10
Data Flow Diagram: Developed By Larry Constantine as a way of expressing system requirements in graphical Form: Data Flow Models (DFMs) are easy to understand and, with a little practice, reasonably quick and straightforward to develop They consist of two parts: a set of Data Flow Diagrams (DFDs) and a set of associated textual descriptions … that provide us with the truly effective tool for understanding the information processes of a system

Data Flow Diagram(2)

  • Upload
    manav

  • View
    234

  • Download
    3

Embed Size (px)

DESCRIPTION

To bring your customers closer to you, Booklogic's unique approach towards Flight Booking System is Immense! Online flight management system is one of the ...

Citation preview

Page 1: Data Flow Diagram(2)

Data Flow Diagram: Developed By Larry Constantine as a

way of expressing system requirements in graphical Form:

Data Flow Models (DFMs) are easy to understand and, with a

little practice, reasonably quick and straightforward to develop

They consist of two parts: a set of Data Flow Diagrams

(DFDs) and a set of associated textual descriptions

… that provide us with the truly effective tool for

understanding the information processes of a system

Page 2: Data Flow Diagram(2)

Objectives of Data Flow Diagram:

To define what is meant by structured

analysis.

To define the symbols used in a Data

Flow Diagram (DFD).

To draw a context diagram (Level 0 DFD)

for a given scenario.

To refine a DFD to a more detailed (lower-

level) view.

Page 3: Data Flow Diagram(2)

Using Data Flow Diagrams:

structured approach - take a top-down approach to

system development.

system is defined first at a general level – overview.

successive refinement occurs until the bottom (primitive)

levels are defined.

primitive level - point where specifications can be

translated into lines of code.

So...system is decomposed into small modules that

perform simple tasks.

Page 4: Data Flow Diagram(2)

Structured Development:

definition is from top to bottom in increasing levels

of detail.

major flows and processes identified .

These are exploded into subprocesses.

Subprocesses are exploded into more detail.

This process can continue to the primitive level,

where programming begins directly from the exploded

diagram.

Page 5: Data Flow Diagram(2)

Structured Terms:

data elements - lowest level of information on which a process

can act i.e. DB attributes/record fields - e.g. unit price.

data stores - places where data are stored; e.g. files; microfiche,

filing cabinets.

data flows - represent movement of data in a system; consist of

data input and data output e.g. forms, reports, invoices, letters.

show movement of data about a physical “thing”.

Page 6: Data Flow Diagram(2)

Logical DFDs:

shows sources and sinks (destinations) of data

identifies and names the logical functions (processes) of the

system.

identifies and names the groups of data elements that connect

one process to another.

identifies the data stores.

each function broken down into more detailed DFD (levels).

descriptions of processes, flows, stores, elements recorded in

data dictionary.

Page 7: Data Flow Diagram(2)

Logical DFDs:

All of the above documentation comprises a logical

functional specification for an existing or new system.

A detailed statement of what the system does/is to

do.

Free from physical considerations of how it will be

implemented.

Page 8: Data Flow Diagram(2)

Data Flow Diagrams Symbol:

The following four symbols are used in data flow diagrams:  External entity   

Process   

Data store 

Data flow

Page 9: Data Flow Diagram(2)

CustomerOrder

Invoice

Available stock stock

Process order

Out-of-stock notice

Unfilled order backorders

Warehouse

Despatch note

Data flow diagram of part of an order processing system:

Page 10: Data Flow Diagram(2)

Booking confirmation

Booking

CustomerTravel-query Available flights

flightsBook flight

Data flow diagram of a travel agent booking system: