Flow chart: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 9: | Line 9: | ||
See also: [[UML activity diagram]], [[Taverna | See also: [[UML activity diagram]], [[Taverna workbench]] | ||
== The traditional flow chart explained == | == The traditional flow chart explained == | ||
Line 24: | Line 24: | ||
* Alan B. Sterneckert (2003) Critical Incident Management, Auerbach Publications, ISBN 978-0849300103 ([http://books.google.co.uk/books?id=8z93xStbEpAC&lpg=PP126&pg=PA126#v=onepage&q&f=false p. 126 Google books]) | * Alan B. Sterneckert (2003) Critical Incident Management, Auerbach Publications, ISBN 978-0849300103 ([http://books.google.co.uk/books?id=8z93xStbEpAC&lpg=PP126&pg=PA126#v=onepage&q&f=false p. 126 Google books]) | ||
[[Category:Design methodologies]] |
Revision as of 14:26, 18 June 2010
“A flowchart is a common type of diagram, that represents an algorithm or process, showing the steps as boxes of various kinds, and their order by connecting these with arrows. This diagrammatic representation can give a step-by-step solution to a given problem. Data is represented in these boxes, and arrows connecting them represent flow / direction of flow of data. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields” ([http://en.wikipedia.org/wiki/Flow_chart Wikipedia, retrieved June 18 2010).
Types of flow charts according to use:
Traditional vs. extended flow charts:
See also: UML activity diagram, Taverna workbench
The traditional flow chart explained
Links and bibliography
Links
- Flow Chart (Wikipedia)
Bibliography
- Alan B. Sterneckert (2003) Critical Incident Management, Auerbach Publications, ISBN 978-0849300103 (p. 126 Google books)