Introduction to Software Engineering
4340702
PRACTICAL - 6
AIM - Develop data designs using DFDs (data flow diagram) and E-R (entity -
relationship) diagram.
TASK
1. Prepare DFD diagram for above selected system.
2. Prepare ER Diagram for above selected system.
DFD - Data Flow Diagrams
A Data Flow Diagram (DFD) is a traditional visual representation of the information
flows within a system. A neat and clear DFD can depict the right amount of the system
requirement graphically. It can be manual, automated, or a combination of both.
It shows how data enters and leaves the system, what changes the information, and
where data is stored.
The objective of a DFD is to show the scope and boundaries of a system as a whole.
It may be used as a communication tool between a system analyst and any person who
plays a part in the order that acts as a starting point for redesigning a system. The DFD
is also called as a data flow graph or bubble chart.
Introduction to Software Engineering
4340702
Levels in Data Flow Diagrams (DFD)
The DFD may be used to perform a system or software at any level of abstraction. In
fact, DFDs may be partitioned into levels that represent increasing information flow
and functional detail. Levels in DFD are numbered 0, 1, 2 or beyond. Here, we will
see primarily three levels in the data flow diagram, which are: 0-level DFD, 1-level
DFD, and 2-level DFD.
0- level DFD
1- level DFD
Introduction to Software Engineering
4340702
2- level DFD
Introduction to Software Engineering
4340702
ER (Entity Relationship) Diagram
ER model stands for an Entity-Relationship model. It is a high-level data model.
This model is used to define the data elements and relationship for a specified
system.
It develops a conceptual design for the database. It also develops a very simple and
easy to design view of data.
In ER modeling, the database structure is portrayed as a diagram called an entity-
relationship diagram.
For example,
suppose we design a school database.
In this database, the student will be an entity with attributes like address, name, id,
age, etc.
The address can be another entity with attributes like city, street name, pin code, etc.
and there will be a relationship between them.
Introduction to Software Engineering
4340702