1 - 1

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

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

1 - 4

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

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

1 - 7

A simple process for making lunch

1 - 8

Process Product

Planning

Analysis

Design

Implementation

System RequestFeasibility Analysis

Workplan

System Proposal

System Specification

New System and Maintenance Plan

1 - 9

A formalized approach to implementing the SDLCA series of steps and deliverables

Methodology Categories

1 - 10

Process-Centered

Data-CenteredObject-

Oriented

Structured DesignRapid Application

DevelopmentAgile Development

1 - 11

1 - 12

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

1 - 14

Pros Cons

Reduces Schedule Time

Less Chance ofRework

Still Uses PaperDocuments

Sub-projects May BeDifficult to Integrate

1 - 15

Spiral Model

1 - 16

1 - 17

Incorporate special techniques and tools:CASE tools JAD sessionsFourth generation/visualization programming

languagesCode generators

1 - 18

Phased developmentA series of versions developed sequentially

PrototypingSystem prototyping

Throw-away prototypingDesign prototyping

1 - 19

Insert Figure 1-4 here

1 - 20

Pros Cons

Users Get a SystemTo Use Quickly

Users Can IdentifyAdditional NeedsFor Later Versions

Users Work with aSystem that isIntentionally Incomplete

1 - 21

1 - 22

Pros Cons

Users Interact withPrototype Very Quickly

Users Can IdentifyNeeded ChangesAnd Refine RealRequirements

Tendency to doSuperficial Analysis

Initial Design Decisions May

Be Poor

1 - 23

1 - 24

Pros Cons

Risks are Minimized

Important Issues areUnderstood Before the

Real System is Built

May Take LongerThan Prototyping

1 - 25

1 - 26

Pros Cons

Fast Delivery of Results

Works Well in ProjectsWith Undefined or

Changing Requirements

Requires Discipline

Works Best in Small Projects

Requires MuchUser Input

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

1 - 27

1 - 28

Business analyst Systems analyst Infrastructure analyst Change management analyst Project manager

1 - 29

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