Control flow diagram

From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article is about flow diagrams in business process modeling[clarification needed]. For directed graphs representing the control flow of imperative computer programs, see control flow graph.
Example of a "performance seeking" control flow diagram.[1]

A control flow diagram (CFD) is a diagram to describe the control flow of a business process, process or program.

Control flow diagrams were developed in the 1950s, and are widely used in multiple engineering disciplines. They are one of the classic business process modeling methodologies, along with flow charts, data flow diagrams, functional flow block diagram, Gantt charts, PERT diagrams, and IDEF.[2]

Overview[edit]

A control flow diagram can consist of a subdivision to show sequential steps, with if-then-else conditions, repetition, and/or case conditions. Suitably annotated geometrical figures are used to represent operations, data, or equipment, and arrows are used to indicate the sequential flow from one to another.[3]

There are several types of control flow diagrams, for example:

In software and systems development control flow diagrams can be used in control flow analysis, data flow analysis, algorithm analysis, and simulation. Control and data are most applicable for real time and data driven systems. These flow analyses transform logic and data requirements text into graphic flows which are easier to analyze than the text. PERT, state transition, and transaction diagrams are examples of control flow diagrams.[4]

Types of Control Flow Diagrams[edit]

Process Control Flow Diagram[edit]

A flow diagram can be developed for the process control system for each critical activity. Process control is normally a closed cycle in which a sensor provides information to a process control software application through a communications system. The application determines if the sensor information is within the predetermined (or calculated) data parameters and constraints. The results of this comparison are fed to an actuator, which controls the critical component. This feedback may control the component electronically or may indicate the need for a manual action.[5]

This closed-cycle process has many checks and balances to ensure that it stays safe. The investigation of how the process control can be subverted is likely to be extensive because all or part of the process control may be oral instructions to an individual monitoring the process. It may be fully computer controlled and automated, or it may be a hybrid in which only the sensor is automated and the action requires manual intervention. Further, some process control systems may use prior generations of hardware and software, while others are state of the art.[5]

Performance seeking control flow diagram[edit]

The figure presents an example of a performance seeking control flow diagram of the algorithm. The control law consists of estimation, modeling, and optimization processes. In the Kalman filter estimator, the inputs, outputs, and residuals were recorded. At the compact propulsion system modeling stage, all the estimated inlet and engine parameters were recorded.[1]

In addition to temperatures, pressures, and control positions, such estimated parameters as stall margins, thrust, and drag components were recorded. In the optimization phase, the operating condition constraints, optimal solution, and linear programming health status condition codes were recorded. Finally, the actual commands that were sent to the engine through the DEEC were recorded.[1]

See also[edit]

References[edit]

 This article incorporates public domain material from websites or documents of the National Institute of Standards and Technology.

  1. ^ a b c Glenn B. Gilyard and John S. Orme (1992) Subsonic Flight Test Evaluationof a Performance Seeking ControlAlgorithm on an F-15 Airplane NASA Technical Memorandum 4400.
  2. ^ Thomas Dufresne & James Martin (2003). "Process Modeling for E-Business". INFS 770 Methods for Information Systems Engineering: Knowledge Management and E-Business. Spring 2003
  3. ^ FDA glossary of terminology applicable to software development and computerized systems. Accessed 14 Jan 2008.
  4. ^ Dolores R. Wallace et al. (1996). Reference Information for the Software Verification and Validation Process, NIST Special Publication 500-234.
  5. ^ a b National Institute of Justice (2002). A Method to Assess the Vulnerability of U.S. Chemical Facilities. Series: Special Report.