DFD Rules
Rules:
Avoid “Black Holes”, “Miracles” and “Grey Holes”
Black Holes:
Process has Input but no Output Order Data.
White Hole or Miracle:
Process has Output but no Input.
Gray Hole:
Process has insufficient Input for the Output it generates.
Incorrect Data Flows | Correct Data Flows |
---|---|
Guidelines for Constructing DFDs:
- Choose meaningful names for processes, flows, stores, and entities:
- Label the process to identify the function the system is carrying out
- Choose an active verb and an appropriate object to form a descriptive phrase
- Avoid verbs such as DO, HANDLE, PROCESS
- Avoid specific abbreviations and acronyms familiar to the user or to us
- Number the processes:
- Numbering schemes should be consistent
- Numbering schemes may imply a certain sequence of operation
- Numbers are a convenient way of referencing processes
- Numbers become the basis for a hierarchical numbering scheme
- Avoid overly complex DFDs:
- Should be easy to understand, easy to absorb, easy to read and pleasing to the eye
- Should fit comfortably on an 8.5 by 11-inch sheet of paper
- Generally, not more than 6 - 8 processes per page
- Context diagram shows one process that represents the entire system and highlights the interfaces between the system and the external entities
- Redraw the DFD as many times as necessary for aesthetics:
- Draw, redraw, redraw
- Should be technically correct
- Should be acceptable to the user
- Should be neat
- Make sure your DFD is logically consistent:
- Avoid processes that have no outputs - “black holes”
- Avoid processes that have no inputs - “miracles”
- Beware of unlabeled flows and unlabeled processes
- Beware of read-only or write-only stores
- Make sure that dataflows coming into and going out of an entire level correspond to the dataflows coming into and going out at the next lower level which describes that process
- A store at the highest level serves as an interface between two or more processes; show it at EVERY lower-level that further describes those processes