Description
In this phase, you will design and communicate an appropriate technical solution that aligns
with your context, needs, and information architecture. You must align your logical design
with functional and non-functional requirements at operational and strategic levels. Non-
Functional requirements are requirements or constraints posed by the client or by the
problem that do not relate directly to the functions of the system.
3.1 Data Flow Diagrams
Translate’ the system structure into data flow diagrams (DFDs) by drawing the high-
level and primitive DFDs: (a) Contextual diagram, (b) Level-0 diagram; and (c) Level-
1 diagrams for the major activities in level-0. Level-1 diagram results from
decomposition of the Level-0 diagram. Remember to label ALL processes, datasets,
and data arrows (inflow and outflow of data). Your DFDs should be contextualized
with a project dictionary (Table) that briefly defines each component of DFDs
(processes, data-sets, source, and sinks). Consistency in labeling is crucial here.
NOTE: ‘Verify’ your models with your client/potential users before submission.
NOTE: you can use Visio (PC Only), or Lucidchart (cloud-based, recommended) to
develop DFDs.