Design Step part-1

Step 3. Conclude whether the Data Flow Diagram has transform or transaction flow characteristics.   In commonly, information flow with a system can always be represented as a transform.  Moreover, when an obvious transaction characteristic is encountered a various design mapping is recommended.  In this step the designer selects a worldwide software-broad flow characteristic based on the prevailing nature of the DFD. Additionally, local regions of transform or transaction flow are remote.  These sub flows can be used to refine program structure derived from a global characteristic define above.  For now we focus our attention only on the monitor sensors subsystem data flow depicted in Figure

Evaluating the Data Flow Diagram we see data entering the software along one incoming way and exiting along 3 outgoing paths. No different transaction center  is implied while the transform acquire alarm conditions could be perceived as like. Thus, an overall transform characteristic will be supposed for information flow.