Scribd Logo
Hochladen

Willkommen bei Scribd!

  • DFD Notations

    Hochgeladen von

    Varsha Malviya
    665 Ansichten13 Seiten
    A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modeling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated.[2] DFDs can also be used for the visualization of data processing (structured design). A DFD shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel (which is shown on a flowchart). It is common practice to draw the context-level data flow diagram first, which shows the interaction between the system and external agents which act as data sources and data sinks. On the context diagram the system's interactions with the outside world are modelled purely in terms of data flows across the system boundary. The context diagram shows the entire system as a single process, and gives no clues as to its internal organization. This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the detail of the system being modeled. The Level 1 DFD shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the system as a whole. It also identifies internal data stores that must be present in order for the system to do its job, and shows the flow of data between the various parts of the system. Data flow diagrams were proposed by Larry Constantine, the original developer of structured design,[3] based on Martin and Estrin's "data flow graph" model of computation. Data flow diagrams are one of the three essential perspectives of the structured-systems analysis and design method SSADM. The sponsor of a project and the end users will need to be briefed and consulted throughout all stages of a system's evolution. With a data flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The old system's dataflow diagrams can be drawn up and compared with the new system's data flow diagrams to draw comparisons to implement a more efficient system. Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to report. How any system is developed can be determined through a data flow diagram model. In the course of developing a set of levelled data flow diagrams the analyst/designers is forced to address how the system may be decomposed into component sub-systems, and to identify the transaction data in the data model. Data flow diagrams can be used in both Analysis and Design phase of SDLC. There are different notations to draw data flow diagrams (Yourdon & Coad and Gane & Sarson[, defining different visual representations for processes, data stores, data flow, and external entities.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Verfügbare Formate

    PPT, PDF, TXT oder online auf Scribd lesen

    Stufen Sie dieses Dokument als nützlich ein?

    Sind diese Inhalte unangemessen?

    Dieses Dokument melden
    A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modeling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated.[2] DFDs can also be used for the visualization of data processing (structured design). A DFD shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel (which is shown on a flowchart). It is common practice to draw the context-level data flow diagram first, which shows the interaction between the system and external agents which act as data sources and data sinks. On the context diagram the system's interactions with the outside world are modelled purely in terms of data flows across the system boundary. The context diagram shows the entire system as a single process, and gives no clues as to its internal organization. This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the detail of the system being modeled. The Level 1 DFD shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the system as a whole. It also identifies internal data stores that must be present in order for the system to do its job, and shows the flow of data between the various parts of the system. Data flow diagrams were proposed by Larry Constantine, the original developer of structured design,[3] based on Martin and Estrin's "data flow graph" model of computation. Data flow diagrams are one of the three essential perspectives of the structured-systems analysis and design method SSADM. The sponsor of a project and the end users will need to be briefed and consulted throughout all stages of a system's evolution. With a data flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The old system's dataflow diagrams can be drawn up and compared with the new system's data flow diagrams to draw comparisons to implement a more efficient system. Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to report. How any system is developed can be determined through a data flow diagram model. In the course of developing a set of levelled data flow diagrams the analyst/designers is forced to address how the system may be decomposed into component sub-systems, and to identify the transaction data in the data model. Data flow diagrams can be used in both Analysis and Design phase of SDLC. There are different notations to draw data flow diagrams (Yourdon & Coad and Gane & Sarson[, defining different visual representations for processes, data stores, data flow, and external entities.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Als PPT, PDF, TXT herunterladen oder online auf Scribd lesen
    Markieren Sie unangemessene Inhalte
    665 Ansichten13 Seiten

    DFD Notations

    Hochgeladen von

    Varsha Malviya
    A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modeling its process aspects. Often they are a preliminary step used to create an overview of the system which can later be elaborated.[2] DFDs can also be used for the visualization of data processing (structured design). A DFD shows what kinds of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It does not show information about the timing of processes, or information about whether processes will operate in sequence or in parallel (which is shown on a flowchart). It is common practice to draw the context-level data flow diagram first, which shows the interaction between the system and external agents which act as data sources and data sinks. On the context diagram the system's interactions with the outside world are modelled purely in terms of data flows across the system boundary. The context diagram shows the entire system as a single process, and gives no clues as to its internal organization. This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the detail of the system being modeled. The Level 1 DFD shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which together provide all of the functionality of the system as a whole. It also identifies internal data stores that must be present in order for the system to do its job, and shows the flow of data between the various parts of the system. Data flow diagrams were proposed by Larry Constantine, the original developer of structured design,[3] based on Martin and Estrin's "data flow graph" model of computation. Data flow diagrams are one of the three essential perspectives of the structured-systems analysis and design method SSADM. The sponsor of a project and the end users will need to be briefed and consulted throughout all stages of a system's evolution. With a data flow diagram, users are able to visualize how the system will operate, what the system will accomplish, and how the system will be implemented. The old system's dataflow diagrams can be drawn up and compared with the new system's data flow diagrams to draw comparisons to implement a more efficient system. Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to report. How any system is developed can be determined through a data flow diagram model. In the course of developing a set of levelled data flow diagrams the analyst/designers is forced to address how the system may be decomposed into component sub-systems, and to identify the transaction data in the data model. Data flow diagrams can be used in both Analysis and Design phase of SDLC. There are different notations to draw data flow diagrams (Yourdon & Coad and Gane & Sarson[, defining different visual representations for processes, data stores, data flow, and external entities.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Als PPT, PDF, TXT herunterladen oder online auf Scribd lesen
    Markieren Sie unangemessene Inhalte
    von 13

    Data Flow Diagram Notations

    Data Store Process A process transforms incoming data flow into outgoing data flow. Yourdon and Coad Process Notations
    Data stores are repositories of data in the system. They are sometimes also referred to as files. Dataflow Dataflows are pipelines through which packets of information flow. Label the arrows with the name of the data that moves through it.

    Yourdon and Coad Datastore Notation


    Gane and Sarson Process Notation Gane and Sarson Datastore Notations
    External Entity External entities are objects outside the system, with which the system communicates. External entities are sources and destinations of the system's inputs and outputs.

    DataFlow Diagrams

    Data Flow Diagram LayersDraw


    Data flow diagrams are drawn in several nested layers A single process node on a high level diagram can be expanded to show a more detailed data flow diagram. Draw the context diagram first, followed by various layers of data flow diagrams.

    DFD Layers

    Context Diagrams
    A context diagram is a top level (also known as Level 0) data flow diagram. It only contains one process node (process 0) that generalizes the function of the entire system in relationship to external entities.

    DFD levels
    The first level DFD shows the main processes within the system. Each of these processes can be broken into further processes until you reach pseudocode.

    Context Diagram- Registration

    Level 0 Data Flow Diagram

    Explosion of Process 4

    Level 0 DFD ATM


    request Transaction requests

    User

    member banks
    Balance Information
    ATM

    display

    receipt

    Printer
    Account data Information request

    account database

    A level 1 DFD
    Customers Card details
    Rejection message
    1. Validate Customer access 2. Reject transaction \and end session

    Printer/display

    PIN Access authorization

    Access map

    Network directory
    Access permissions Rejection message

    customer
    select options

    3. Obtain Details of transaction

    Transaction request

    4. Validate transaction

    A level 2 DFD
    Customers Card details
    1.1 Read Details From card

    Cannot Read card

    Card data

    Printer/display

    Encoded pin
    1.2 Check Expiry date And bank group

    PIN

    customer

    1.3 Request Pin And match Max 3 attempts

    Card Validation data Access map

    Invalid pin Access authorization

    Network directory

    member banks

    Another Approach to the ATM Level 1

    Get deposit

    User

    Get inquiry

    bank name error account # account # & deposit error

    account display

    Validate deposit

    Validate inquiry

    account #

    Display account
    account # & deposit

    Make inquiry Printer

    account data

    balance query

    Do deposit transaction

    deposit transaction

    account data

    Create account summary

    account database

    Das könnte Ihnen auch gefallen