SYSTEMS DEVELOPMENT METHODOLOGIES. WHAT IS A METHODOLOGY? Procedures + Techniques + Tools + Phases = Method Method + Philosophy = Methodology.

Slides:



Advertisements
Similar presentations
Lecture 3 Planning and Development Methodologies.
Advertisements

Software Quality Assurance Plan
Software Project Management
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Information Systems Analysis and Design
Soft Systems Methodology
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Introduction to Soft Systems Methodology. The Vision SSM Models Use Cases Activity Models Dynamic Models Object Models Programs Databases Business Computing.
© Farhan Mir 2008 IMS MIS Development BBA (IT) 6 th (Lectures ) (Information System Development Methodologies) Course Lecturer: Farhan Mir.
2.1 The traditional SDLC and structured approaches: Structured Analysis IMS Information Systems Development Practices.
System Design and Analysis
Lecture 13 Revision IMS Systems Analysis and Design.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Physical design. Stage 6 - Physical Design Retrieve the target physical environment Create physical data design Create function component implementation.
Computers: Tools for an Information Age
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
IMS Information Systems Development Practices
IMS5024 Week 81 IMS 5024 Human Activity modelling.
Introduction to Computer Technology
Chapter 6: The Traditional Approach to Requirements
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
SYSTEM ANALYSIS AND DESIGN
Introduction to Information System Development.
Introduction to Systems Analysis and Design Trisha Cummings.
Overview of the Database Development Process
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Section 02Systems Documentation1 02 Systems Documentation And Franchise Colleges By MANSHA NAWAZ.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
Week 5: Business Processes and Process Modeling MIS 2101: Management Information Systems.
Information Systems Analysis and Design
ITEC224 Database Programming
CB1004 Modelling Business Systems 71 Modelling Business Systems 7 Systems Methods.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
Project Life Cycles.
Modeling and simulation of systems Model building Slovak University of Technology Faculty of Material Science and Technology in Trnava.
1 Introduction to Software Engineering Lecture 1.
Systems Analysis and Design
Systems Life Cycle A2 Module Heathcote Ch.38.
Structured Systems Analysis and Design Methodology Contains 5 modules: Feasibility Study (Stage 0) Requirements Analysis (Stages 1 and 2) Requirements.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
The Systems Life Cycle AS Computing F451 AS Computing F451.
Systems Development Life Cycle
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Lecture 2 System Development Lifecycles. Building a house Definition phase Analysis phase Design phase Programming phase System Test phase Acceptance.
Lecture 3 : Hard Systems Modelling UFCE8V-20-3 Information Systems Development SHAPE Hong Kong 2010/11.
1 The System life cycle 16 The system life cycle is a series of stages that are worked through during the development of a new information system. A lot.
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
Methodologies and SSADM Models, Tools and Techniques.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Unit F451 Computer Fundamentals Components of a Computer System Software Data: Its representation, structure and management in information.
Chapter 1 Assuming the Role of the Systems Analyst.
MANAGEMENT INFORMATION SYSTEM
Information Systems Development
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
Concepts used for Analysis and Design
Introduction to Systems Analysis and Design
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Information Systems Development (ISD) Systems Development Life Cycle
Presentation transcript:

SYSTEMS DEVELOPMENT METHODOLOGIES

WHAT IS A METHODOLOGY? Procedures + Techniques + Tools + Phases = Method Method + Philosophy = Methodology

WHAT IS A PHILOSOPHY? e.g. building a system that: - makes most use of computers or - is the cheapest to run or - is implemented earliest or - is the most adaptable or - is best liked by its users or etc.

WHY USE A METHODOLOGY? To introduce structure into design To increase the likelihood of success Previously: Problem - User - Programmer - Change - Create Problem - User - Programmer etc With Methodologies: Problem - Analysis - Design - Implementation - Success

EXAMPLES OF SYSTEMS DEVELOPMENT METHODOLOGIES 'Hard' Methodologies SSADM (Structured Systems Analysis and Design Methodology) STRADIS (Structured Analysis and Design) JSD (Jackson Structured Design) 'Soft' Methodologies ETHICS SSM (Soft Systems Methodology) Mix of 'hard' and 'soft' MULTIVIEW

SSADM (Structured Systems Analysis and Design Methodology) Features: Data Driven Detailed rules Comprehensive manuals For Covers all elements of life cycle Used by Civil Service It works! Against Overkill for small projects

Stages Analysis 1. Analysis of Current System 2. Specification of Required System 3. Technical Options Design 4. Detailed Data Design 5. Detailed Procedure Design 6. Physical Design Control

1.Analysis of Current System Identify bottlenecks/dissatisfaction Use interviews/questionnaires etc. Produce DFDs, LDSs Agree current system model with users

2. Specification of Required System Expand current system to include new requirements Include data and process aspects Include audit, security and controls Produce a consolidation of people's views

3. Technical Options Centralised vs. Distributed OnLine vs. Batch Response times Staffing level implications Other resource implications

4. Detailed Data Design Define data and data relationships Ensure data structure meets: Screen/Report requirements Processing requirements

5. Detailed Procedure Design Catalog all functions Check against data structure Perhaps prototype Check logical design meets requirements

6. Physical Design Control Produce plan for building/testing system Include program specs, operating procedures Consolidate documentation

STRADIS (Structured Analysis and Design) Features: Solution found from a number of possible modules and interfaces Uses a selection of tools and techniques For Suited to any size system Against More about defining the solution than the problem

Stages 1. Initial Study 2. Detailed Study 3. Define and Design Alternative Solutions 4. Physical Design

1.Initial Study Aim to select systems which will: Reduce costs Increase revenue Improve services Speak to users and managers Produce overview DFD Decide whether to progress to next stage

2. Detailed Study Identify users of new system Draw level 1 DFD Produce lower levels of DFD Produce process descriptions Produce detailed cost/benefit analysis

3. Define and Design Alternative Solutions Convert organisational objectives into system objectives (i.e. make them specific, not general) Produce level 1 DFD for new system Produce three alternative solutions: quick and cheap (some objectives met) longer and more costly (most met) longest and most expensive (all met)

4. Physical Design Produce all logic and error handling Produce data dictionary Produce report and screen formats Produce files/database Identify clerical tasks All down to a level where costs can be detailed

JSD (Jackson System Development) Features: Extension to JSP (Jackson Structured Programming) Transformation from program specification to implementation For Models a dynamic world Against Orientated towards software rather than organisational needs Several elements of life cycle missing e.g.requirements analysis user interface database design

Stages Entity Action step Entity Structure step Initial Model step Function step System Timing step Implementation step

Entity Action step Define entities that perform or suffer actions e.g. customer, supplier but by behaviour rather than relationship Traditional entity modelling = static JSD = dynamic

Entity Structure step Draw diagrams to show life history (Boxes) Initial Model step Create model to simulate entity activity (Pseudo-code) Function step Add necessary functions to produce output (e.g. account balance) System Timing step Add delays to reflect real world (e.g. user requirements, technical restrictions) Implementation step Allocate processors to processes

ETHICS (Effective Technical and Human Implementation of Computer-Based systems) Features: Adopts an ethical philosophy Technology + Social + Organisational Improved job satisfaction and working life Involves users in design decisions For Well accepted by users Against Treated with suspicion by management Users may not have necessary skills

STAGES Why Change System Boundaries Description on Existing System Definition of Key Objectives and Tasks Diagnosis of Efficiency Needs Diagnosis of Job Satisfaction Needs Future Analysis Specifying and Weighing Efficiency and Job Satisfaction Needs and Objectives Organisational Design of the New System Technical Options Preparation of A Detailed Work Design Implementation Evaluation

Why Change As the name implies, If not conclusive, then don't System Boundaries Consider effect upon the following areas: Business Activities Existing Technology Parts of the Organisation Parts of the Organisation's environment Description of Existing System In terms of inputs, outputs and processes Definition of Key Objectives and Tasks Roles, Purposes, Responsibilities and Functions

Diagnosis of Efficiency Needs Identify weak links Diagnosis of Job Satisfaction Needs Standard Questionnaire Future Analysis Allow flexibility for enhancements etc

Specifying and Weighing Efficiency and Job Satisfaction Needs and Objectives Key step Produce objectives based on previous steps Rank these into primary and secondary All primary objectives must be met As many as possible secondary should be met

Organisational Design of the New System Identify operating activities Identify coordination activities Identify development activities Identify control activities Identify special skills required Identify key roles or relationships

Technical Options Evaluate options for software, hardware, HCI in terms of efficiency, job satisfaction and future change. The Preparation of a Detailed Work Design Design the system in detail Identify data flows, tasks, groups etc Ensure objectives are still being met

Implementation Plan implementation in detail Strategy Education and Training Co-ordination Evaluation Check Objectives met

SSM (Soft Systems Methodology) Philosophy: A System is more than the sum of its parts Models of data and processes are simple, Involve people and they become ill-defined or 'fuzzy‘ For Deals with the real world Against Too much analysis, not enough design

Stages Produce rich picture Include clients, participants and tasks Identify CATWOE: C lient - beneficiary or victim A ctor - agent of change T ransformation - the change taking place W orld view (Weltanschauung) - assumptions O wner - the sponsor E nvironment - the wider system

MULTIVIEW Features Mix of hard and soft For Best of both worlds Against Hotch-Potch of techniques

Stages Analysis of human activity systems Look at organisation, its purpose and problems Information modelling Analyse entities and functions Analysis and design of the socio-technical system Consider people, needs, working environment Design of the Human-Computer Interface Command, Form, Menu, Icon/Mouse, Natural Language? Design of the technical sub-systems Combine Entity model and Technical requirements

Outputs are: Applications - processes Information - produced Database - used Control - error checking Recovery - repairing mistakes Monitoring - keeping track for management