Data Flow Diagram - Guidelines for Process Naming in DFD

Guidelines for Process Naming

·   Select names that indicate the action taking place. Selecting an action verb and an object to receive the action is most appropriate.

           

·   Be sure the name fully describes the process. (If a process both edits and validates invoice data, it should not be labelled EDIT INVOICES).

           

·   Select process names that explain the linkage between inflows and outflows of data.

           

·   Avoid vague process names, such as PROCESS, REVIEW, ASSEMBLE, HANDLE or ORGANISE.

           

·   Use lower-level process names that are much more specific and descriptive than those associated with high-level processes.

           

·   Assign process names that are unique to the activity they describe.

The process numbering system introduced earlier further identifies processes especially between levels of detail. The highest level diagram (Context) need not be numbered. All lower level diagrams should be identified by number.

So if a Level 1 diagram identifies five processes (numbered 1 to 5) then lower-level explosions of these processes are assigned a decimal to indicate that they are further explanations of a higher-level process. For example, if high-level process 3 contains four processes then they are numbered 3.1, 3.2, 3.3, 3.4. Successive explosions add additional decimal digits: 3.1.1,  3.1.2., 3.1.3., etc.