ppt for quest

25
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1 INTRODUCTION Overview of Systems Analysis

Upload: ruchiturja

Post on 06-Apr-2015

271 views

Category:

Documents


3 download

TRANSCRIPT

Page 1: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 1

INTRODUCTION

Overview of Systems Analysis

Page 2: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 2

Key Ideas

Many systems failures were because analysts tried to build wonderful systems without understanding the organization and applying a systematic approach.

Page 3: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 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.

Page 4: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 4

Types of Information Systems

Transaction Processing SystemsManagement Information SystemsDecision Support SystemsExpert Systems

Development of these systems require a good understanding of business processes and data

Page 5: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 5

Systems Development Lifecycle Approach

The projectMoves systematically through phases where each phase has a standard set of outputsProduces project deliverablesUses deliverables in implementationUses gradual refinement and an iterative approach

Page 6: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 6

Project Phases

PlanningWhy build the system?

AnalysisWhat will the system be?

DesignHow will the system work?

ImplementationSystem delivery

Page 7: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 7

Identifying business valueAnalyze feasibilityDevelop work planStaff the projectControl and direct project

Planning

Page 8: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 8

AnalysisInformation gatheringProcess modelingData modeling

Analysis

Page 9: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 9

Physical designArchitectural designInterface designDatabase and file designProgram design

Design

Page 10: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 10

ConstructionInstallation

Implementation

Page 11: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 11

Processes and Deliverables

Process Product

Planning

Analysis

Design

Implementation

Project Plan

System Proposal

System Specification

New System and Maintenance

Plan

Page 12: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 12

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.

Page 13: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 13

Structured Design

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

Page 14: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 14

Waterfall Development Method

Page 15: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 15

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

Page 16: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 16

Alternatives to the SDLC

Rapid Application Development (RAD)Prototyping

Page 17: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 17

Rapid Application Development

Critical elementsCASE toolsJAD sessionsFourth generation/visualization programming languagesCode generators

Page 18: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 18

How Prototyping Works

Page 19: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 19

Object-Oriented Analysis and Design

Attempts to balance emphasis on data and processUses Unified Modeling Language (UML) for diagramming

Use-case DrivenArchitecture Centric

Functional, Static, and Dynamic views

Iterative and Incremental

Page 20: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 20

Key Elements

Classes -- template to define objects

Instances -- specific examples of class members

Objects -- building block of the system

Attributes -- describe data aspects of the object

Methods -- the processes the object can perform

Messages -- instructions sent to or received from other objects

Page 21: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 21

A Class and Its Objects

PATIENT

-Name-Birthdate-Phone Number+Insert ()()+Delete ()()

PATIENT 1: TOP PACKAGE: PATIENT

-Name = Teresa Marks-Birthdate = March 16, 1975-Phone number = 314-997-3456

PATIENT 2: TOP PACKAGE: PATIENT

-Name = Mel Bourne-Birthdate = May 11, 1965-Phone number = 314-997-3219

Attributes

Methods

Class

Instantiated Objects of the Class

Page 22: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 22

The Key to Reusability

Information hiding is the principle that only information required to use the object is available outside the objectEncapsulation is the mechanism that combines data and processes in a single object

Page 23: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 23

UML

Unified Modeling LanguageThe full UML provides 9 separate diagramming techniques

Page 24: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 24

Summary

The Systems Development Lifecycle consists of four stages: Planning, Analysis, Design, and Implementation

There are two major development methodologies: the waterfall method, RAD/Prototyping

Page 25: Ppt for Quest

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design

Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.Slide 25

Summary

There are six major elements in Object-Oriented design: classes, objects, instances, attributes, methods, and messages.Encapsulation, Inheritance, and Polymorphism are also important object-oriented conceptsThere are five major team roles: business analyst, systems analyst, infrastructure analyst, change management analyst and project manager.