TheDragonFire (talk | contribs) m Reverted edit by 2409:4052:698:950C:0:0:2549:68AD (talk) to last version by Ira Leviton Tag: Rollback |
|||
| (6 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
{{Short description| |
{{Short description|Business process modeling tool}} |
||
{{This|flow diagrams in business process modeling{{clarify|reason=From the lead, I'm unable to give a more informative characterization of 'Control flow diagram'.|date=January 2014}}|directed graphs representing the control flow of imperative computer programs|control-flow graph}} |
{{This|flow diagrams in business process modeling{{clarify|reason=From the lead, I'm unable to give a more informative characterization of 'Control flow diagram'.|date=January 2014}}|directed graphs representing the control flow of imperative computer programs|control-flow graph}} |
||
[[File:Performance seeking control flow diagram.jpg|thumb|240px|Example of a "performance seeking" control-flow diagram.<ref name="GO92"> Glenn B. Gilyard and John S. Orme (1992) [http://www.nasa.gov/centers/dryden/pdf/88262main_H-1808.pdf ''Subsonic Flight Test Evaluationof a Performance Seeking ControlAlgorithm on an F-15 Airplane''] NASA Technical Memorandum 4400.</ref>]] |
[[File:Performance seeking control flow diagram.jpg|thumb|240px|Example of a "performance seeking" control-flow diagram.<ref name="GO92"> Glenn B. Gilyard and John S. Orme (1992) [http://www.nasa.gov/centers/dryden/pdf/88262main_H-1808.pdf ''Subsonic Flight Test Evaluationof a Performance Seeking ControlAlgorithm on an F-15 Airplane''] NASA Technical Memorandum 4400.</ref>]] |
||
| Line 17: | Line 17: | ||
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.<ref>Dolores R. Wallace et al. (1996). [http://hissa.nist.gov/HHRFdata/Artifacts/ITLdoc/234/val-proc.html ''Reference Information for the Software Verification and Validation Process''] {{webarchive|url=https://web.archive.org/web/20081011193257/http://hissa.nist.gov/HHRFdata/Artifacts/ITLdoc/234/val-proc.html |date=2008-10-11 }}, NIST Special Publication 500-234.</ref> |
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.<ref>Dolores R. Wallace et al. (1996). [http://hissa.nist.gov/HHRFdata/Artifacts/ITLdoc/234/val-proc.html ''Reference Information for the Software Verification and Validation Process''] {{webarchive|url=https://web.archive.org/web/20081011193257/http://hissa.nist.gov/HHRFdata/Artifacts/ITLdoc/234/val-proc.html |date=2008-10-11 }}, NIST Special Publication 500-234.</ref> |
||
== Types of |
== Types of control-flow diagrams == |
||
=== Process- |
=== Process-control-flow diagram === |
||
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 . The application determines if the sensor information is within the predetermined (or calculated) data parameters and constraints. The results of this comparison, which controls the critical component. This [feedback] may control the component electronically or may indicate the need for a manual action |
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 . The application determines if the sensor information is within the predetermined (or calculated) data parameters and constraints. The results of this comparison, which controls the critical component. This [feedback] may control the component electronically or may indicate the need for a manual action. This closed-cycle process has many checks and balances to ensure that it stays safe. |
||
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. |
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. |
Further, some process control systems may use prior generations of hardware and software, while others are state of the art. |
||
| Line 30: | Line 30: | ||
== See also == |
== See also == |
||
* [[Data-flow diagram]] |
* [[Data-flow diagram]] |
||
* [[Data and information visualization]] |
|||
* [[Control-flow graph]] |
* [[Control-flow graph]] |
||
* [[DRAKON]] |
* [[DRAKON]] |
||
Latest revision as of 14:15, 22 February 2024
A control-flow diagram (CFD) is a diagram to describe the control flow of a business process, process or review.
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, drakon-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:
- Change-control-flow diagram, used in project management
- Configuration-decision control-flow diagram, used in configuration management
- Process-control-flow diagram, used in process management
- Quality-control-flow diagram, used in quality control.
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 . The application determines if the sensor information is within the predetermined (or calculated) data parameters and constraints. The results of this comparison, which controls the critical component. This [feedback] may control the component electronically or may indicate the need for a manual action. This closed-cycle process has many checks and balances to ensure that it stays safe. 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.
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 the National Institute of Standards and Technology
- ^ 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.
- ^ Thomas Dufresne & James Martin (2003). "Process Modeling for E-Business" Archived 2006-12-20 at the Wayback Machine. INFS 770 Methods for Information Systems Engineering: Knowledge Management and E-Business. Spring 2003
- ^ FDA glossary of terminology applicable to software development and computerized systems. Accessed 14 Jan 2008.
- ^ Dolores R. Wallace et al. (1996). Reference Information for the Software Verification and Validation Process Archived 2008-10-11 at the Wayback Machine, NIST Special Publication 500-234.