1 - 1 systems analysis and design,. 1 - 2 key ideas many failed systems were abandoned because...

1 - 1

Systems Analysis Systems Analysis and Designand Design, ,

1 - 2

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 - 3

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 - 4

THE SYSTEMS THE SYSTEMS DEVELOPMENT LIFE DEVELOPMENT LIFE CYCLECYCLE

1 - 5

Major Attributes of the Life Cycle

The project --Moves systematically through phases where each phase has a standard set of outputsProduces project deliverablesUses deliverables in implementationResults in actual information systemUses gradual refinement

1 - 6

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 - 7

Identifying business valueAnalyze feasibilityDevelop work planStaff the projectControl and direct project

Planning

1 - 8

Analysis strategyGathering business requirementsRequirements definition use casesProcess modelingData modeling

Analysis

1 - 9

Design selectionArchitecture designInterface designData storage designProgram design

Design

1 - 10

ConstructionProgram buildingProgram and system testing

InstallationConversion strategyTraining planSupport plan

Implementation

1 - 11

Processes and Deliverables

Process Product

Planning

Analysis

Design

Implementation

System RequestFeasibility Analysis

Workplan

System Proposal

System Specification

New System and Maintenance Plan

1 - 12

SYSTEM DEVELOPMENT SYSTEM DEVELOPMENT METHODOLOGIESMETHODOLOGIES

1 - 13

What Is a Methodology?

A formalized approach to implementing the SDLC

A series of steps and deliverables

Methodology CategoriesProcess-

CenteredData-CenteredObject-

Oriented

Structured DesignRapid Application

DevelopmentAgile Development

1 - 14

Waterfall Development Methodology

1 - 15

Pros and Cons of the Waterfall Methodology

Pros Cons

Identifies systems requirements long before programming begins

Minimizes changes to requirements asproject progresses

Design must be specified on paper before programming begins

Long time between system proposal and delivery of new system

1 - 16

Parallel Development Methodology

1 - 17

Pros and Cons of Parallel Development Methodology

Pros Cons

Reduces Schedule Time

Less Chance ofRework

Still Uses PaperDocuments

Sub-projects May BeDifficult to Integrate

1 - 18

Rapid Application Development

Incorporate special techniques and tools:

CASE toolsJAD sessionsFourth generation/visualization programming languagesCode generators

1 - 19

Three RAD Categories

Phased developmentA series of versions developed sequentially

PrototypingSystem prototyping

Throw-away prototypingDesign prototyping

1 - 20

Phased Development Methodology

Insert Figure 1-4 here

1 - 21

Pros and Cons of Phased Development Methodology

Pros Cons

Users Get a SystemTo Use Quickly

Users Can IdentifyAdditional NeedsFor Later Versions

Users Work with aSystem that isIntentionally Incomplete

1 - 22

How Prototyping Works

1 - 23

Pros and Cons of Prototyping Methodology

Pros Cons

Users Interact withPrototype Very Quickly

Users Can IdentifyNeeded ChangesAnd Refine RealRequirements

Tendency to doSuperficial Analysis

Initial Design Decisions May

Be Poor

1 - 24

Throwaway Prototyping

1 - 25

Pros and Cons of Throwaway Prototyping Methodology

Pros Cons

Risks are Minimized

Important Issues areUnderstood Before the

Real System is Built

May Take LongerThan Prototyping

1 - 26

Agile Development: Extreme Programming

1 - 27

Pros and Cons of Agile Methodologies

Pros Cons

Fast Delivery of Results

Works Well in ProjectsWith Undefined or

Changing Requirements

Requires Discipline

Works Best in Small Projects

Requires MuchUser Input

1 - 28

Criteria for Selecting the Appropriate Methodology

Clear user requirementsFamiliarity with technologyComplexity of systemReliability of systemTime scheduleSchedule visibility

1 - 29

SummaryThe Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and ImplementationThere 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.