Prelim Lecture 3a System Engineering Intro To System 2

INTRODUCTION
Lecture 3-a
Introduction to System Analysis
and Design
Slide 1 PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design
Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.
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.
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.
THE SYSTEMS
DEVELOPMENT LIFE
CYCLE
Major Attributes of the
Lifecycle
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
Project Phases
Planning
Why build the system?
Analysis
Who, what, when, where will the system be?
Design
How will the system work?
Implementation
System delivery
A “Simple” Process for Making Lunch
Planning
Identifying business value
Analyze feasibility
Develop work plan
Staff the project
Control and direct project
Analysis
Analysis
Information gathering
Process modeling
Data modeling
Design
Physical design
Architectural design
Interface design
Database and file design
Program design
Implementation
Construction
Installation
Processes and
Deliverables
Process Product
Planning Project Plan
Analysis System Proposal
Design System
Specification
Implementation New System and

Maintenance Plan
THE EVOLUTION OF
SYSTEM DEVELOPMENT
What Is a Methodology?
A formalized approach or series

of steps
Writing code without a well-
thought-out system request
may work for small programs,
but rarely works for large ones.
Structured Design
Projects move methodically
from one to the next step
Generally, a step is finished
before the next one begins
Waterfall Development
Method
Pros and Cons of the
Waterfall Method
Pros Cons
Identifies systems Design must be

requirements long specified on paper
before programming before programming
begins begins
Long time between

system proposal and
delivery of new
system
Alternatives to the SDLC
Rapid Application Development

(RAD)
Phased Development
Prototyping
Throw-Away Prototyping
Rapid Application
Development
Critical elements
CASE tools
JAD sessions
Fourth generation/visualization
programming languages
Code generators
Rapid Application
Development Categories
Phased development
A series of versions
Prototyping
System prototyping
Throw-away prototyping
Design prototyping
How Prototyping Works
Throwaway Prototyping
Object-Oriented Analysis
and Design
Attempts to balance emphasis
on data and process
Uses Unified Modeling Language
(UML) for diagramming
Use-case Driven
Architecture Centric
Iterative and Incremental
BASIC
CHARACTERISTICS OF
OBJECT-ORIENTED
SYSTEMS
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
A Class and Its Objects
Instantiated Objects of the Class
Class PATIENT 1: TOP PACKAGE: PATIENT
-Name = Teresa Marks

PATIENT -Birthdate = March 16, 1975
-Phone number = 314-997-3456
-Name
-Birthdate Attributes
-Phone Number
+Insert ()()
+Delete ()() PATIENT 2: TOP PACKAGE: PATIENT
-Name = Mel Bourne

Methods -Birthdate = May 11, 1965
-Phone number = 314-997-3219
The Key to Reusability
Information hiding is the
principle that only information
required to use the object is
available outside the object
Encapsulation is the mechanism
that combines data and
processes in a single object
Class Hierarchy
Inheritance
Polymorphism
OBJECT-ORIENTED
ANALYSIS AND DESIGN
USING UML
UML
The full UML provides 9
separate diagramming
techniques
PROJECT TEAM ROLES
AND SKILLS
Information Systems
Roles
Business analyst
System analyst
Infrastructure analyst
Change management analyst
Project manager
Summary -- Part 1
The Systems Development Lifecycle

consists of four stages: Planning, Analysis,
Design, and Implementation
There are three major development

methodologies: the waterfall method, RAD,
and the Object-Oriented approach.
Summary -- Part 2
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 concepts
There are five major team roles: business
analyst, systems analyst, infrastructure
analyst, change management analyst and
project manager.
Expanding the Domain
For complete description of UML
see:
www.rational.com/uml

Prelim Lecture 3a System Engineering Intro To System 2

Uploaded by

Copyright:

Available Formats

You might also like

Prelim Lecture 3a System Engineering Intro To System 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Prelim Lecture 3a System Engineering Intro To System 2

Uploaded by

Copyright:

Available Formats

INTRODUCTION

Planning Project Plan

Analysis System Proposal

Implementation New System and

A formalized approach or series

Identifies systems Design must be

Long time between

Rapid Application Development

Class PATIENT 1: TOP PACKAGE: PATIENT

-Name = Teresa Marks

-Name = Mel Bourne

The Systems Development Lifecycle

There are three major development

You might also like