Slide 1

Systems Analysis and Design With UML Systems Analysis and Design With UML 2.02.0

An Object-Oriented Approach, Second EditionAn Object-Oriented Approach, Second Edition

Chapter 1: Introduction to Systems Analysis and Design

Alan Dennis, Barbara Wixom, and David Tegarden© 2005John Wiley & Sons, Inc.

Slide 2

Copyright © 2005John Wiley & Sons, Inc.

All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for redistribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.

Slide 3

INTRODUCTION

Chapter 1

Slide 4

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.

Slide 5

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.

Slide 6

THE SYSTEMS DEVELOPMENT LIFE CYCLE

Slide 7

Major Attributes of the Lifecycle

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

Slide 8

Project Phases

PlanningWhy build the system?

AnalysisWho, what, when, where will the system be?

DesignHow will the system work?

ImplementationSystem delivery

Slide 9

A “Simple” Process for Making Lunch

Slide 10

Identifying business valueAnalyze feasibilityDevelop work planStaff the projectControl and direct project

Planning

Slide 11

AnalysisInformation gatheringProcess modelingData modeling

Analysis

Slide 12

Physical designArchitectural designInterface designDatabase and file designProgram design

Design

Slide 13

ConstructionInstallation

Implementation

Slide 14

Processes and Deliverables

Process Product

Planning

Analysis

Design

Implementation

Project Plan

System Proposal

System Specification

New System and Maintenance

Plan

Slide 15

SYSTEM DEVELOPMENT Methodologies

Slide 16

What Is a Methodology?

A formalized approach or series of stepsWriting code without a well-thought-out system request may work for small programs, but rarely works for large ones.

Slide 17

Structured Design

Projects move methodically from one to the next stepGenerally, a step is finished before the next one begins

Slide 18

Waterfall Development Method

Slide 19

Pros and Cons of the Waterfall Method

Pros Cons

Identifies systems requirements long before programming begins

Design must be specified on paper before programming begins

Long time between system proposal and delivery of new system

Slide 20

Parallel Development

Slide 21

Alternatives to the SDLC

Rapid Application Development (RAD)Phased DevelopmentPrototypingThrow-Away Prototyping

Slide 22

Rapid Application Development

Critical elementsCASE toolsJAD sessionsFourth generation/visualization programming languagesCode generators

Slide 23

Rapid Application Development Categories

Phased developmentA series of versions

PrototypingSystem prototyping

Throw-away prototypingDesign prototyping

Agile DevelopmentExtreme Development

Slide 24

How Prototyping Works

Slide 25

Throwaway Prototyping

Slide 26

Selecting the Appropriate Methodology

Clarity of User RequirementsFamiliarity with TechnologySystem ComplexitySystem ReliabilityShort Time SchedulesSchedule Visibility

Slide 27

Criteria for Selecting a Methodology

Slide 28

Project Team Roles and Skills

Slide 29

Information Systems Roles

Business analystSystem analystInfrastructure analystChange management analystProject manager

Slide 30

Project Team Roles

Slide 31

Summary -- Part 1

The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and ImplementationThe major development methodologies:

Structured design the waterfall method Parallel development

RAD development Prototyping (regular and throwaway)

Agile development XP streamline SDLC

Slide 32

Summary -- Part 2

There are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.