System Analysis

and Design
CSE 4004

Ms. Hansamali Paul

Lecturer
Dept. of ICT,
Faculty of Technology
University of Sri Jayewardenepura
Structured Analysis
What is Structured Analysis?

Structured analysis is a technique that uses graphical diagrams to develop and

portray system specifications that are easily understood by users.

Structured analysis is a development method that allows that analyst to

understand that system and its activities in a logical way.

It is systematic approach, which uses graphical tools that analyze and refine
the objectives of an existing system and develop a new system specification
which can be easily understood by user.
What is Structured Analysis?

The basic goal of SA/SD is to improve quality and reduce the risk of system
failure.

The tools and techniques used during Structured Analysis are:

DFD (Data Flow Diagrams)
Data Dictionary
Structured English
Pseudo Code
Decision Tree
Decision Table
What is Structured Design?

Structured design is a concept of decomposing problem into

several well-organized elements of solutions.

It gives better understanding of how the problem is being solved.

Structured design also makes it simpler for designer to

concentrate on the problem more accurately.
What is Structured Design?

Structured design is mostly based on ‘’divide and conquer

strategy, where a problem is broken into several small problems
and each small problem is individually solved until the whole
problem is solved.
What is DFD?

DFD stands for “Data Flow Diagram” and also known as “Bubble Chart”

DFD show the flow of data between various elements of a system in graphical
form.

It also expresses the requirement of the system and shows how the current
system is implemented.
What is DFD?

It gives an overview of what data a system processes, what transformations are

being performed, what data are stored, what results are produced and where
they flow.
Its graphical nature makes it a good communication tool between user and
system designer (System Analyst).
DFD is easy to understand and quite effective tool for communication (between
user and system analyst) when the required design is not clear.
Types of DFD

Logical DFD Physical DFD

It shows how data flows in a system It shows how data flow is actually implemented
in the system

It describes processes without suggesting how It include process implementation information.

they are conducted.

It describes what data is moved from one entity It describes how data is moved from one entity
to another to another.

It focuses on what happens in the data flow It shows how the current system operates and
how a system will be implemented

It shows how the system works but not how the

system can be implemented.
Reading a DFD

This diagram is depicting thee process of receiving a bill from a vendor

and paying it..
Basic Elements/Components of DFD
Symbols used in DFD are:
.
DFD Elements Cont.

Process
Processes are represented with rounded rectangles or sometimes circles.
-Process is an activity or function performed for a
specific business reason
-These can be manual or computerized
- when you depict processes in your diagrams include:
A number
A name (verb phrase)
A description (if necessary)
At least one output dataflow
At least one input data flow
DFD Elements Cont.

Data flow
These are the arrows that connect the different pieces on the data flow
diagrams.
-a data flow represents a single piece of data or a
logical collection of data
- data flow names describe the content of the data flow
but not how it is implemented
-it always starts or ends at a process
-it includes:
a name (noun)
Description (if necessary)
One or more connections to a process
DFD Elements Cont.

Data store
Represented with an open narrow rectangle or even listing the data store
between two parallel lines.
-most information systems capture data for later use
- a data store is a collection of data that is stored in
some way (it could be a database or a particular table
in a database or a physical filing cabinet)
-it includes:
a number
a name (noun)
Description (if necessary)
One or more data flows (inputs or output or both)
DFD Elements Cont.

External Entity
External entity is a person, organization, or system that is external to the
system that we are creating

-It has interactions with the system by adding data to

system or receiving data from the system

-it includes:
a name (noun)
Description (if necessary)
DFD Hierarchy

Data flow diagrams are built in a hierarchy

Business processes are too complex to be shown on a single diagram. So a

hierarchy can be build with multiple levels of DFDs.

To build a hierarchy we use decomposition. So a child diagram shows a potion of

a parent diagram in greater detail.
DFD Hierarchy

A context diagram shows a single process with data flows to and from external
entities as shown in the diagram.

.
Levels of DFD

There are mainly 3 levels in DFD:

0-level DFD (Context Diagram)
1-level DFD
2-level DFD

.
Levels of DFD
0-level DFD
it shows the system as a single process with its relationship to external
entities.
it represents the entire system as a single process with input and output
data indicated by incoming/outgoing arrows.
here the single process of the context diagram is broken out into more
detail with more processes and data stores.
Levels of DFD
0-level DFD

.
Levels of DFD
1-level DFD

.
Levels of DFD
2-level DFD
In level 2 DFD, we decompose the 1-level DFD into more detail and define each
necessary detail about system functioning properly.

In practice it’s common to see level 0 and level 1 diagrams, while it’s possible to
have 2, level 3 or even beyond . But they are rare except in very complex
systems.
Diagram Numbering
Since there are large set of data flow diagrams it’s important to correctly number
each process to help the user understand where the process fits into the overall
hierarchy.
context diagram is always “Process 0”
Level 0 processes are always numbered with integer value (1,2,3 etc.)
Level 1 processes always have one “dot”: (1.1, 1.2, 1.3, etc.)
Level 2 processes have two “dots” (1.1.1, 1.1.2, 1.1.3, etc.)
.
Rules in creating DFD
Process labels should be verb phrases
No process can have only outputs or only inputs.
.

Data store and entity labels should be noun phrases

Rules in creating DFD
All flows to or from a data store must move through a process
.
entity

database

Data flow labels should be noun phrases

Rules in creating DFD

Bidirectional flow between process and data store is represented by two separate
arrows.
.
Example: Context diagram (Basic Calculator)

First we have the process. Inside the process we have the system which is the
basic calculator.
We have a user. So user is the one who uses the calculator. For the calculator to
be function the user must send something to the process.
The user needs to give the 1st number, operator and the 2nd number.
The process will give information to the user (calculated result)
Example: Context diagram (Basic Calculator)

1st number
Operator
2nd number

Basic
user
Calculator

Calculated result
 Questions

You want to create a Chat Application.

Create a context diagram for it.
Chat Application
As the process we have Chat application
There’s a sender who provides the message to the system. Apart from the message the
sender will also give the receiver’s name or the contact details because for a message to
be send the application need receiver’s information.
Now the process gives the message to receiver. Apart from the message the application
will also give the sender’s name or contact details.
Receiver can also input message to the application
Application can send the message to the sender. So the message is being transferred vise
versa.
.
Chat Application
Data Flow Diagram: Student Enrollment System

Before creating the data flow diagram, create the context diagram.

.
Data Flow Diagram: Student Enrollment System

Student
Enrollment
System
Level 1 DFD

.
 Questions

Draw a DFD diagram for a Hospital Management

System
Context Diagram: Hospital Management System
Context Diagram: Hospital Management System
Admin will send patient and staff information to hospital module process.
Hospital module will send modified and updated information to admin.

Patient will send his or her information to hospital module

Hospital module will send bill information and diagnosis information to patient

The diagnosis information will be send by doctor or staff to hospital module

Hospital will send it to patient.
Hospital will send list of patient and reports to doctor.
Context Diagram: Hospital Management System
Level 1 DFD Diagram: Hospital Management System
Here we can add 4 processes:
Patient management
Assigning room/facility
Assigning Medicine
Staff management
Then we can take 3 entities
Patients
Staff/Doctor
Admin
Level 1 DFD Diagram: Hospital Management System

Then there are 3 databases

Patient database to store patient information
Medicine database to store medicine information that is assigned to
particular patient
staff database to store Staff information

.
Level 1 DFD Diagram: Hospital Management System
Level 1 DFD Diagram: Hospital Management System
patient will add patient information in the patient database. This information
will shared to manage patient process.
This process will send the patient information to admin. The admin will add edit
and delete patient entry in the patient database.
Manage patient process will also send patient information to staff and doctors.
This information will be store in staff database.
It will send to manage staff and doctor process and then this information will
send to admin.
Admin has the right to update and delete staff information
Level 1 DFD Diagram: Hospital Management System
Manage staff also assign different departments to different staff and doctor will
send patient diagnosis information to patient management process
This process will store this information in a patient database.
Patient can access patient diagnosis information from patient database.
Patient will send this information to assigned room/ facility process and as well
as to assign medicine process
Staff or doctor will send what kind of facilities patient needs and this
information will send to assigned room/ facility process
After diagnosis doctor will also send medicine information of the patient to
Level 1 DFD Diagram: Hospital Management System
After diagnosis doctor will also send medicine information of the patient to
assigned medicine process and send the facilities and medicine information to
patient
At the end patient management process will send the bill information to patient
.
Level 1 DFD Diagram: Hospital Management System
Level 2 DFD Diagram for the billing process
Thank You