Scribd
Upload
34 views6 pages

22BT04025 Se Practical 8

SE Practical

Uploaded by

SImPL E
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
34 views6 pages

22BT04025 Se Practical 8

SE Practical

Uploaded by

SImPL E
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Practical- 8

Modeling of Data Flow Diagram


I. Give a brief introduction with graphical notations for data flow diagram, explanation
of symbols used in DFD, Context diagram and levelling DFD.
II. Create a level-0 & level-1 DFD for the selected application.

What is a Data Flow Diagram?


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.

The following observations about DFDs are essential:


i. All names should be unique. This makes it easier to refer to elements in the DFD.
ii. Remember that DFD is not a flow chart. Arrows is a flow chart that represents the
order of events; arrows in DFD represents flowing data. A DFD does not involve any
order of events.
iii. Suppress logical decisions. If we ever have the urge to draw a diamond-shaped box
in a DFD, suppress that urge! A diamond-shaped box is used in flow charts to
represents decision points with multiple exists paths of which the only one is taken.
This implies an ordering of events, which makes no sense in a DFD.
iv. Do not become bogged down with details. Defer error conditions and error
handling until the end of the analysis.

Software Engineering (BTCS502) PageNo:28


Devani Ayush (22BT04025)
Standard Symbols for Data Flow Diagram:

Circle: A circle (bubble) shows a process that transforms data inputs into data outputs.

Data Flow: A curved line shows the flow of data into or out of a process or data store.

Data Store: A set of parallel lines shows a place for the collection of data items. A data
store indicates that the data is stored which can be used at a later stage or by the other
processes in a different order. The data store can have an element or group of elements.

Source or Sink: Source or Sink is an external entity and acts as a source of system inputs
or sink of system outputs.

Software Engineering (BTCS502) PageNo:29


Devani Ayush (22BT04025)
Context Diagrams:

The context diagram is used to establish the context and boundaries of the system to be
modelled: which things are inside and outside of the system being modelled, and what is
the relationship of the system with these external entities.

A context diagram, sometimes called a level 0 data-flow diagram, is drawn in order to


define and clarify the boundaries of the software system. It identifies the flows of
information between the system and external entities. The entire software system is shown
as a single process.

To construct Context diagram:

1. Identify data-flows by listing the major documents and information flows associated
with the system, including forms, documents, reference material, and other structured and
unstructured information (emails, telephone conversations, information from external
systems, etc.).

2. Identify external entities by identifying sources and recipients of the data-flows, which
lie outside of the system under investigation. The actors an any use case models you have
created may often be external entities.

3. Draw and label a process box representing the entire system.

4. Draw and label the external entities around the outside of the process box.

5. Add the data-flows between the external entities and the system box. Where documents
and other packets of information flow entirely within the system, these should be ignored
from the point of view of the context diagram – at this stage they are hidden within the
process box.

What is Leveling?
Leveling in a Data Flow Diagram (DFD) is the process of breaking down a complex
system into more manageable sub-systems or levels of detail. It helps to organize and
represent the information flow within a system by gradually expanding or refining the DFD
to show more detail.

Here’s how it works:

1. Level 0 (Context Diagram): This is the highest-level DFD and provides an overview of
the entire system. It shows the system as a single process (usually labeled as Process 0)
along with external entities that interact with the system. The arrows indicate data flow
between the system and these external entities.

Software Engineering (BTCS502) PageNo:30


Devani Ayush (22BT04025)
2. Level 1 DFD: This is a more detailed breakdown of the Level 0 diagram. The single
process in the Level 0 DFD is decomposed into multiple sub-processes, showing internal
data flows and the interaction between these sub-processes. It provides a more detailed
view of the system's main functions.

3. Level 2, Level 3, etc.: Further decomposition can be done if needed, where each process
in Level 1 can be broken down into more detailed sub-processes. This hierarchical structure
continues until no further decomposition is required or meaningful.

The goal of leveling is to provide a clear, structured, and easy-to-understand representation


of a system’s data flows, starting from a high-level overview and moving towards more
detailed diagrams. It allows for better system analysis and helps stakeholders understand
the processes involved in the system.

Level 0 Diagram for trading system:

Software Engineering (BTCS502) PageNo:31


Devani Ayush (22BT04025)
Level 1 diagram for trading system:

Software Engineering (BTCS502) PageNo:32


Devani Ayush (22BT04025)
Conclusion: A Data Flow Diagram (DFD) is a visual tool used to represent the flow of
data within a system, showcasing how information moves between processes, data stores,
and external entities. The context diagram, or Level 0 DFD, provides a high-level view of
the entire system, depicting it as a single process with its external interactions. Leveling
involves breaking down this high-level diagram into more detailed sub-levels (Level 1,
Level 2, etc.), refining the system into smaller components to illustrate the internal
processes and data flows. This approach helps to simplify complex systems and enhances
understanding for better analysis and design.

Software Engineering (BTCS502) PageNo:33


Devani Ayush (22BT04025)

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy