You are on page 1of 5

SOFTWARE ENGINEERING

CO-301
EXPERIMENT - 06
RISHIT TOTEJA
(2K20/EE/217)

AIM - Draw different levels of DFD for different domains, like the library system,
banking systems, hospital management systems and hotel management system.

THEORY -

Data flow diagram is a graphical representation of the flow of data in an information


system. It is capable of depicting incoming data flow, outgoing data flow and stored
data.

Certainly, let's expand on the theory of Data Flow Diagrams (DFD) and provide some
additional information:

1. Process Modeling: DFDs are used as a tool for process modeling in system analysis and
design. They help in understanding the flow of data and processes within a system. This
modeling technique is crucial for identifying system components and their interactions.

2. Levels of Detail: DFDs can be structured into multiple levels of detail, ranging from a
high-level overview of the entire system down to detailed processes within a module. This
hierarchical approach allows for a clear representation of the system's architecture and
functionality.

3. External Entities: In a DFD, external entities are represented as sources or destinations of


data. These can include individuals, other systems, or organizations that interact with the
system being analyzed. External entities interact with the system through data flows.
4. Processes: Processes in a DFD represent actions or transformations that occur within the
system. They are labeled with a unique process number and a clear description of the function
they perform. DFDs can have various levels of processes, with higher-level diagrams showing
more abstract, top-level processes, and lower-level diagrams providing finer details.

5. Data Stores: Data stores represent repositories where data is stored within the system.
These can be databases, files, or any other storage mechanisms. Data stores are depicted as a
rectangle with a double line.

6. Data Flows: Data flows are arrows that represent the movement of data between processes,
external entities, and data stores. They indicate the direction of data transfer and are labeled
with the data's name and sometimes its characteristics.

7. Data Flow: Attributes: Each data flow can be associated with attributes, which describe the
properties of the data being transferred. Attributes may include data types, formats, and any
constraints or rules that apply to the data.

8. Context Diagram: The highest level of a DFD is often referred to as the context diagram,
which provides an overview of the entire system. It shows external entities and their
interactions with the system without delving into detailed processes.

9. Balancing: DFDs are typically balanced, meaning that the total flow of data into and out of
a system or process must be accounted for. This ensures data consistency and completeness
within the system.

10. Modularity and Decomposition: DFDs support modularity by allowing the system to
be decomposed into smaller, manageable modules. This decomposition aids in system design
and development.

11. System Boundaries: DFDs define clear boundaries for the system being analyzed. This
helps in identifying what is part of the system and what is external to it.
12. Iterative Development: DFDs can be used iteratively during system analysis and design.
As more details become available, DFDs can be refined and expanded to provide a deeper
understanding of the system.

DFDs are a powerful tool in system analysis and design, providing a visual representation that
aids in communication, documentation, and understanding of complex systems across various
domains, including library systems, banking systems, hospital management systems, and hotel
management systems.

LEVEL 0 DFD:
LEVEL 1 DFD:

LEVEL 2 DFD:
PRECAUTIONS:

1. Always back up your data and diagrams before making any changes to prevent data loss
or corruption.
2. Clearly define the experiment's objectives and scope to maintain focus and avoid
unnecessary complexity.
3. Create a controlled testing environment to avoid impacting the actual system and
ensure data integrity.
4. Keep detailed records of your experiment, including decisions and modifications made
during the process.

You might also like