Systems Analysis and Design,

1-1

Key Ideas
Many failed systems were abandoned because analysts tried to build wonderful systems without understanding the organization. The primarily goal is to create value for the organization.

1-2

Key Ideas
The systems analyst is a key person analyzing the business, identifying opportunities for improvement, and designing information systems to implement these ideas. It is important to understand and develop through practice the skills needed to successfully design and implement new information systems.
1-3

THE SYSTEMS DEVELOPMENT LIFE CYCLE

1-4

Major Attributes of the Life Cycle

The project -Moves systematically through phases where each phase has a standard set of outputs Produces project deliverables Uses deliverables in implementation Results in actual information system Uses gradual refinement
1-5

Project Phases
Planning (Why build the system? How should the team go about building it?) Analysis (Who uses system, what will it do, where and when will the system be used?) Design (How will the system work?) Implementation (System delivery)
1-6

Planning
Identifying business value Analyze feasibility Develop work plan Staff the project Control and direct project

1-7

Analysis
Analysis strategy Gathering business requirements Requirements definition use cases Process modeling Data modeling

1-8

Design
Design selection Architecture design Interface design Data storage design Program design

1-9

Implementation
Construction
Program building Program and system testing

Installation
Conversion strategy Training plan Support plan
1 - 10

Processes and Deliverables

Process
Planning

Product
System Request Feasibility Analysis Workplan System Proposal System Specification New System and Maintenance Plan

Analysis

Design
Implementation
1 - 11

SYSTEM DEVELOPMENT METHODOLOGIES

1 - 12

What Is a Methodology?
A formalized approach to implementing the SDLC
A series of steps and deliverables

Methodology Categories
Process-Centered Data-Centered Object-Oriented Structured Design Rapid Application Development Agile Development

1 - 13

Waterfall Development Methodology

1 - 14

Pros and Cons of the Waterfall Methodology

Pros
Identifies systems requirements long before programming begins Minimizes changes to requirements as project progresses

Cons
Design must be specified on paper before programming begins Long time between system proposal and delivery of new system

1 - 15

Parallel Development Methodology

1 - 16

Pros and Cons of Parallel Development Methodology

Pros
Reduces Schedule Time Less Chance of Rework

Cons
Still Uses Paper Documents Sub-projects May Be Difficult to Integrate

1 - 17

Rapid Application Development

Incorporate special techniques and tools:
CASE tools JAD sessions Fourth generation/visualization programming languages Code generators

1 - 18

Three RAD Categories

Phased development
A series of versions developed sequentially

Prototyping
System prototyping

Throw-away prototyping
Design prototyping

1 - 19

Phased Development Methodology

Insert Figure 1-4 here

1 - 20

Pros and Cons of Phased Development Methodology

Pros
Users Get a System To Use Quickly Users Can Identify Additional Needs For Later Versions

Cons

Users Work with a System that is Intentionally Incomplete

1 - 21

How Prototyping Works

1 - 22

Pros and Cons of Prototyping Methodology

Pros
Users Interact with Prototype Very Quickly Users Can Identify Needed Changes And Refine Real Requirements

Cons
Tendency to do Superficial Analysis Initial Design Decisions May Be Poor

1 - 23

Throwaway Prototyping

1 - 24

Pros and Cons of Throwaway Prototyping Methodology

Pros
Risks are Minimized

Cons
May Take Longer Than Prototyping

Important Issues are Understood Before the Real System is Built

1 - 25

Agile Development: Extreme Programming

1 - 26

Pros and Cons of Agile Methodologies

Pros
Fast Delivery of Results

Cons
Requires Discipline Works Best in Small Projects

Works Well in Projects With Undefined or Changing Requirements

Requires Much User Input

1 - 27

Criteria for Selecting the Appropriate Methodology

Clear user requirements Familiarity with technology Complexity of system Reliability of system Time schedule Schedule visibility
1 - 28

Summary
The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation There are six major development methodologies: the waterfall method, the parallel development method, the phased development method, system prototyping, design prototyping, and agile development. There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.
1 - 29