Scribd
Upload
40 views

Software Requirement Engineering

The document discusses drawing data flow diagrams (DFDs) for software engineering projects. It defines DFDs and their elements, and provides a 5-step process for creating DFDs, including identifying inputs/outputs, building context and level 1 diagrams, and expanding to more detailed level 2+ diagrams. An example of drawing DFD levels for a hotel reservation system is also given.

Uploaded by

alihassankhan2277
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
40 views

Software Requirement Engineering

The document discusses drawing data flow diagrams (DFDs) for software engineering projects. It defines DFDs and their elements, and provides a 5-step process for creating DFDs, including identifying inputs/outputs, building context and level 1 diagrams, and expanding to more detailed level 2+ diagrams. An example of drawing DFD levels for a hotel reservation system is also given.

Uploaded by

alihassankhan2277
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

SOFTWARE REQUIREMENT

ENGINEERING

Experiment 10
Drawing Data flow diagrams

CLO 1 : Construct the experiments/projects of varying complexities.

CLO 2: Use modern tools and languages.

CLO 3: Demonstrate an original solution of problem under discussion.

CLO 4: Work individually as well as in teams.


1- What is Data Flow Diagram?
A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and
outputs. As its name indicates its focus is on the flow of information, where data comes from,
where it goes and how it gets stored.

2- Data flow diagram symbols and notation

There are essentially two different types of notations for data flow diagrams that defines different
visual representations for processes, data stores, data flow and external entities.

1. Yourdon & Coad (used for system analysis and design)


2. Gane & Sarson (visualizing information systems)

There are four basic elements of a data flow diagram:

1. processes
2. data stores
3. external entities
4. data flows
The picture below shows the standard shapes for both methodologies.
3- How to create a data flow diagram

The process can be broken down into 5 steps:

a. Identify major inputs and outputs in your system

Nearly every process or system begins with input from an external entity and ends with the output of data
to another entity or database. Identifying such inputs and outputs gives a macro view of your system—it
shows the broadest tasks the system should achieve. The rest of your DFD will be built on these elements,
so it is crucial to know them early on.

b. Build a context diagram

Once you’ve identified the major inputs and outputs, building a context diagram is simple. Draw a single
process node and connect it to related external entities. This node represents the most general process
information undergoes to go from input to output.

c. Expand the context diagram into a level 1 DFD

The single process node of your context diagram doesn’t provide much information—you need to break it
down into subprocesses. In your level 1 data flow diagram, you should include several process nodes,
major databases, and all external entities. Walk through the flow of information: where does the
information start and what needs to happen to it before each data store?

d. Expand to a level 2+ DFD

To enhance the detail of your data flow diagram, follow the same process as in step 3. The processes in
your level 1 DFD can be broken down into more specific subprocesses. Once again, ensure you add any
necessary data stores and flows.To progress beyond a level 2 data flow diagram, simply repeat this
process. Stop once you’ve reached a satisfactory level of detail.

e. Confirm the accuracy of your final diagram

When your diagram is completely drawn, walk through it. Pay close attention to the flow of information:
does it make sense? Are all necessary data stores included? By looking at your final diagram, other
parties should be able to understand the way your system functions. Before presenting your final diagram,
check with co-workers to ensure your diagram is comprehensible.
Example 1: Draw levels of data flow diagram for Hotel Reservation System.

Levels of Data flow diagram

Data flow diagrams are also categorized by level. Starting with the most basic, level 0, DFDs get

increasingly complex as the level increases. As you build your own data flow diagram, you will need to

decide which level your diagram will be.

Level 0 DFDs, also known as context diagrams, are the most basic data flow diagrams. They provide a

broad view that is easily digestible but offers little detail. Level 0 data flow diagrams show a single

process node and its connections to external entities.

Data Flow Diagram Level 0

Level 1 DFDs are still a general overview, but they go into more detail than a context diagram. In a level

1 data flow diagram, the single process node from the context diagram is broken down into subprocesses.
As these processes are added, the diagram will need additional data flows and data stores to link them

together.

Data Flow Diagram Level 1

Level 2+ DFDs simply break processes down into more detailed sub processes. In theory, DFDs could go

beyond level 3, but they rarely do. Level 3 data flow diagrams are detailed enough that it doesn’t usually

make sense to break them down further.


Americas couch or data stores being Kuchar process again further amari process Joanna 1920 they can't
man up the process without reservation process obviously they came to aki main main just systemData
Flow Diagram Level 2

Lab Task: Draw level 0, level 1 Data flow diagram for hospital management
System.

You might also like