Alpha University College
School of Business and Economics
Degree Program
Systems Analysis and Design
Chapter 2
System Analysis and Design Tools & Technique
Prepared by: Seid Y.
Learning Objectives
Understand different methodology of
SAD
Define systems analysis and design
tools
Discuss the technique to systems
analysis and design
1.1
1.1
What is Methodology?
It is a formalized approach or series of steps.
SAD Methodology is a structured process for
developing information systems, involving phases of
understanding user needs (analysis) and then
detailing a solution (design).
It is Comprehensive guidelines to follow for
completing every activity in the systems development
life cycle, including specific models, tools and
techniques.
1.2
1.2
The Main
Components of
Methodology (MCM)
Techniques Tools
METHODOLOGY
Models
1.4
1.4
MCM>Techniques,
Models, Tools (TMT)
Techniques is a collection of guidelines
that help an analyst complete a system
development.
Model is a representation of some
important aspect of the real world.
Tool is software tool that helps create
models or other components required
in the project.
MCM>TMT>Samples
1. Flowchart 1. Strategic Planning 1. CASE
2. Data Flow Diagram 2. User interviewing 2. Drawing/graphic
(DFD) techniques applications
3. Entity-Relationship 3. Data-Modeling 3. Reverse-
Diagram (ERD) techniques engineering
tool
4. Structure Chart 4. Software-testing
techniques 4. Code generator
5. Class diagram
tool
5. Project Mgt
6. Sequence diagram
techniques 5. Database management
application
6. Structured analysis &
design techniques 6. Word processor
1.4
1.4
Two General Approaches to
Development
Object-
Traditional
Oriented
Approach
Approach
Structure
d
Approach
“…All system developers should be familiar with two
very general approaches (structured, OO) to system
development, because they form the basis of virtually all
methodologies…”
1.3
1.3
Structured & O-O
Methodologies
Structured Analysis is a methodology used in
software engineering to understand and
define system requirements through a
systematic approach.
It focuses on breaking down a system into
smaller, manageable components and
understanding the flow of data and
processes.
Key elements include data flow diagrams,
process specifications, and data dictionaries.
1.4
1.4
Cont.….
Object-Oriented Analysis (OOA) is a
methodology in software engineering that
models a system based on real-world entities
and their interactions.
It focuses on identifying objects—entities with
both data (attributes) and behaviors (methods)
—and their relationships to design a system.
The main components include classes, objects,
inheritance, and encapsulation.
1.4
1.4
Cont.….
Structured Analysis Object-Oriented Analysis
The main focus is on the process and procedures The main focus is on data structure and real-world
of the system. objects that are important.
It uses System Development Life Cycle It uses Incremental or Iterative methodology
It is suitable for well-defined projects with stable It is suitable for large projects with changing user
user requirements. requirements.
Risk while using this analysis technique is high Risk while using this analysis technique is low and
and reusability is also low. reusability is also high.
Structuring requirements include DFDs (Data Requirement engineering includes the Use case
Flow Diagram), Structured Analysis, ER (Entity model (find Use cases, Flow of events, Activity
Relationship) diagram, CFD (Control Flow Diagram), the Object model (find Classes and class
Diagram), Data Dictionary, Decision table/tree, relations, Object interaction, Object to ER mapping),
and the State transition diagram. Statechart Diagram, and deployment diagram.
This technique is old and is not preferred usually. This technique is new and is mostly preferred.
1.4
1.4
Structured Methodologies
1. Data Flow Diagram
Data Flow Diagram is a graphical representation of the flow
of data within the system. It help to understand the flow of data
throughout the system, from input to output, and how it gets
transformed along the way.
S y m b o l s a n d No tati o n s U s e d
• External entity: an outside system that sends or
receives data, communicating with the system being
diagrammed.
• P r o c e s s : any process that changes the data,
producing an output.
• Data store: files or repositories that hold
information for later use
• D a t a fl ow: the route that data takes between the
external entities, processes and data stores.
1.4
1.4
Cont.….
1.4
1.4
Cont.….
D F D rules
• Each process should have at least one input
and an output.
• Each data store should have at least one
data flow in and one data flow out.
• Data stored in a system must go through a
process.
• All processes in a DFD go to another process
or a data store.
1.4
1.4
Cont.….
D F D levels and layers
• A data flow diagram can be represented into
progressively more detail by using levels and
layers, zeroing in on a particular piece.
• DF D levels are numbered 0, 1 or 2, and
occasionally go to even Level 3 or beyond.
• The necessary level of detail depends on the
scope of what you are trying to accomplish.
1.4
1.4
Cont.….
D F D Level 0-Context
• b a Diagram.
s i c o v e r v i e w of the w h o l e s y s t e m or
p ro c e s s b e i n g analyzed or modeled.
• It’s d e s i g n e d to be a n at-a -g l a n c e view,
s h o w i n g the system as a single high-level
process, with its relationship to external entities.
• Its u s e d b y a wide a u d i e n c e , i n c l u d i n g
s t a ke h o l d e r s , business analysts, data
a n a l y s t s a n d d e v e l o p e r s to understand
the system.
1.4
1.4
Cont.….
DFD Level 1
• It provides a more detailed breakout of pieces of
the Context Level Diagram.
• It highlights the main functions carried out by the
system, as we break down the high-level process of the
Context Diagram into its subprocesses
1.4
1.4
Cont.….
DFD Level 2
• It goes one step deeper into parts of Level 1.
• It m a y require more text to reach the necessary level of
detail about the system’s functioning.
1.4
1.4
Cont.….
1.4
1.4
Thank You!!!
1.28
1.28