System Analysis and Process

Integration

BAem 414
Lecture # 3
 Table of Contents

• System Development Life Cycle Phases

• Information Systems Attributes

• UML introduction
System Analysis and Design

Attributes of System
Development
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 4
SYSTEMS DEVELOPMENT
LIFE CYCLE
Major Attributes of the Lifecycle

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

Slide 6
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 Slide 7
A “Simple” Process for Making Lunch

Slide 8
Processes and Deliverables

Process Product
Project Plan
Planning

System Proposal
Analysis

System
Design
Specification

New System and

Implementation
Maintenance
Plan
Slide 9
THE EVOLUTION OF SYSTEM
DEVELOPMENT

Slide
10
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.

Slide
11
Structured Design

• In this type of design, Projects move from one to the next step.

• Generally, a step is finished before the next one begins.

Slide
12
Waterfall Development Method

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

Slide
14
Alternatives

• Rapid Application Development (RAD)

• Phased Development
• Prototyping
• Throw-Away Prototyping

Slide
15
Rapid Application Development

• Critical elements
• CASE tools
• JAD sessions
• Fourth generation/visualization programming languages
• Code generators

Slide
16
Rapid Application Development
Categories

• Phased development
• A series of versions

• Prototyping
• System prototyping

• Throw-away prototyping
• Design prototyping

Slide
17
How Prototyping Works

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

Slide
19
BASIC CHARACTERISTICS OF
OBJECT-ORIENTED SYSTEMS

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

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

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

Slide
23
Class Hierarchy

Slide
24
Inheritance

Slide
25
Polymorphism

Slide
26
OBJECT-ORIENTED ANALYSIS AND
DESIGN USING UML

Slide
27
 Example : Stakeholders

• During the development of a banking information system, the

following are the stakeholders who have influence on the proposed
system.
• Development team
• Customers
• Operational staff
• Bank managers
• Executive management

• Question:

• Who all are the stakeholders of SIS?

28
• Discuss the role of each stakeholder.
 What is UML?

“A picture is worth a thousand words”

• UML stands for Unified Modelling Language

• It is a standardized modelling language

• A way for interaction between different stakeholder in the system.

• Supports a broad range of application

• Independent of programming language and development process

• Developed for specifying, visualizing, constructing, and documenting the

artifacts of a system
 What is UML? – cont.
UML is not limited to a particular phase of the SDLC, it is used on all
phases of SDLC

UML simplifies the complexity of the system and used as a

communication tool among stakeholders of the system
 Vast Usability of UML

• A system can viewed from two different aspects:

• Structural
• Behavioral Represent the static
aspect of the system
(Class diagram)

Represent the dynamic

aspect of the system
(Activity diagram)
 UML Digrams

Structural Behavioral
Class diagram Use case diagram
Object diagram Sequence diagram
Component diagram Collaboration diagram
Deployment diagram State chart diagram
Activity diagram
Disgn Process Using UML
 UML Software

• StarUML is one of the commercially available UML tool

• It has a free version

• StarUML supports most of the diagram types specified in UML 2.0

• You can download and use this version from its web site
https://starUML.io/download
PROJECT TEAM ROLES AND SKILLS

Slide
35
 Information Systems Roles

• Business analyst

• System analyst

• Infrastructure analyst

• Change management analyst

• Project manager

Slide
36
 Summary - Describe the components of
Systems Analysis

Systems analysis is a process of examining a business or organizational problem in order to develop a solution in
the form of a software system. The components of systems analysis are as follows:

• Requirements gathering

• Feasibility study:

• Current system analysis

• Data and process modeling:

• Requirements specification

• Prototype & Design Solution

• Testing and validation & Maintenance

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.

Slide
38
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.

Slide
39
In-Class Activity
 Q/A

Thanks
Reference for extra knowledge:

PowerPoint Presentation for Dennis, Wixom &

Tegardem, Systems Analysis and Design, Copyright
2021 © John Wiley & Sons, Inc. All rights reserved.

Slide
42