INTRODUCTION TO SYSTEM ANALYSIS

AND DESIGN
BY
DR MOURAD RAAFAT
 5 Marks for
all participants
 Introduction to System
SDLC methodologies
analysis and design

Course Identifying and

contents
Analysis
selecting of system

Process modeling
Logical Modeling
System Requirements
Conceptual data
modeling
 Main Idea

1. Many failed systems were

abandoned because analysts
tried to build wonderful systems
without understanding the
organization.
2. The primarily goal is to create
value for the organization.
(Cont’d)

• The systems analyst is a key

person analyzing the business,
identifying opportunities for
improvement, and designing
systems to implement these
ideas.
• It is important to understand
and develop through practice
the skills needed to
successfully design and
implement new systems.
(Cont’d)

• The systems analyst works

closely with all project team
members so that the team
develops the right system in
an effective way.
• Systems analysts must
understand how to apply
technology in order to solve
problems.
 (CONT’D)

• Systems analysts may serve

as change agents who
identify organizational
improvement needed, design
systems to implement those
changes, and train and
motivate others to use the
systems.
 Technical – Must understand the
technical environment, technical
foundation, and technical
solution.

Business – Must understand how

IT can be applied to business
situations.

Systems Analyst Skills Analytical – Must be problem

solvers.
 Interpersonal – Need to communicate
effectively.

Management – Need to manage

people and to manage pressure and
risks.

Ethical - Must deal fairly, honestly, and

ethically with other project members,
(cont’d) managers, and systems users.
 Business analyst - Focuses on
the business issues surrounding
the system.

Systems analyst - Focuses on

the IS issues surrounding the
system.

Systems Analyst Roles Infrastructure analyst - Focuses

on technical issues
 Change management analyst - Focuses
on the people and management issues
surrounding the system installation.

Project manager - Ensures that the

project is completed on time and within
(cont’d) budget, and that the system delivers
the expected vale to the organization.
System Development
Life cycle
 ▪The project
▪ Moves systematically through
Major phases where each phase has a
standard set of outputs
Attributes of ▪ Produces project deliverables
▪ Uses deliverables in implementation
the Lifecycle ▪ Results in actual information
system
▪ Uses gradual refinement
Project Phases

▪Planning
▪ Why build the system?
Planning

▪Analysis
▪ Who, what, when, where will the system be?
Project
▪Design Implementation
phase
Analysis

▪ How will the system work?

▪Implementation
▪ System delivery Design
A “Simple” Process for Making Lunch
 (cont’d)

▪ The SDLC is composed of four fundamental phases:

• Planning
• Analysis
• Design
• Implementation
▪ Each of the phases is composed of steps, which rely on techniques that produce
deliverables (specific documents that explain various elements of the system).

© Copyright 2011 John Wiley & Sons, Inc. 1-16

 Planning
▪ This phase is the
fundamental process of
understanding why an
information system should be
built, and determining how
the project team will go about
building it.

1-17
The planning phase has two steps:

1. During project initiation, the system’s business

value to the organization is identified (How will it
lower costs or increase revenues?)
2. ie. Technical, economic and organizational?.
2. During project management, the project manager
creates a work plan, staffs the project, and puts
techniques in place to help the project team
control and direct the project through the entire
SDLC.

© Copyright 2011 John Wiley & Sons, Inc. 1-18

Analysis

▪ The analysis phase answers the questions of who will use

the system, what the system will do, and where and when it
will be used.
▪ During this phase the project team investigates any current
system(s), identifies improvement opportunities, and
develops a concept for the new system.

© Copyright 2011 John Wiley & Sons, Inc. 1-19

The analysis phase has three steps:

1. Analysis strategy: This is developed to guide the projects team’s

efforts. This includes a study of the current system and its
problems, and envisioning ways to design a new system.
2. Requirements gathering: The analysis of this information leads
to the development of a concept for a new system. This
concept is used to build a set of analysis models(5
requirements).
3. System proposal: The proposal is presented to the project
sponsor and other key individuals who decide whether the
project should continue to move forward.

© Copyright 2011 John Wiley & Sons, Inc. 1-20

Design

▪ The design phase decides how the

system will operate, in terms of the
hardware, software, and network
infrastructure; the user interface,
forms, and reports that will be used;
and the specific programs, databases,
and files that will be needed.

© Copyright 2011 John Wiley & Sons, Inc. 1-21

The design phase has four steps:

1. Design Strategy: This clarifies whether the system will be

developed by the company or outside the company.
2. Architecture Design: This describes the hardware, software,
and network infrastructure that will be used.
3. Database and File Specifications: These documents define
what and where the data will be stored.
4. Program Design: Defines what programs need to be written
and what they will do.

© Copyright 2011 John Wiley & Sons, Inc. 1-22

▪ This collection of deliverables (architecture design, interface design,
database and file specifications, and program design) is the system
specification that is handed to the programming team for
implementation. At the end of the design phase, the feasibility
analysis and project plan are reexamined and revised, and another
decision is made by the project sponsor and approval committee
about whether to terminate the project or continue.
Implementation

▪ During the implementation phase, the

system is either developed or purchased
(in the case of packaged software) and
installed.
▪ This phase is usually the longest and most
expensive part of the process.

© Copyright 2011 John Wiley & Sons, Inc. 1-24

The implementation phase has three steps:

1. System Construction: The system is built

and tested to make sure it performs as
designed.
2. Installation: The old system is turned off
and the new one is turned on.
3. Support Plan: Includes a post-
implementation review as well as a systematic
way for identifying changes needed for the
system.

© Copyright 2011 John Wiley & Sons, Inc. 1-25

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

Slide 27
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 28
Structured Design

▪ Projects move methodically from one to the next step

▪ Generally, a step is finished before the next one begins

Slide 29
Waterfall Development Method

Slide 30
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 31
Parallel Development Method

Slide 32
Parallel Development Method

▪ Instead of doing design and implementation in sequence, it performs a general

design for the whole system and then divides the project into a series of distinct
subprojects that can be designed and implemented in parallel.

Slide 33
Pros Cons

Reduce the schedule time to Huge paper documents.

deliver a system Sometimes the subprojects are not
completely independent.
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

PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Slide 36
Copyright 2001 © John Wiley & Sons, Inc. All rights reserved.
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

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