Jump to content

Flowchart: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
[accepted revision][pending revision]
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Reverted edits by 164.58.21.70 (talk) (HG) (3.4.4)
←Replaced content with 'this is just some junk about symbols. omega lul'
Tags: Replaced possible vandalism
Line 1: Line 1:
this is just some junk about symbols. omega lul
{{pp-pc1|small=yes}}

{{Redirect|Flow chart|the poem|Flow Chart (poem)|the music group|Flowchart (band)}}
[[File:LampFlowchart.svg|thumb|right| A simple flowchart representing a process for dealing with a non-functioning lamp.]]
A '''flowchart''' is a type of [[diagram]] that represents an [[algorithm]], [[workflow]] or process. The flowchart shows the steps as boxes of various kinds, and their order by connecting the boxes with arrows. This diagrammatic representation illustrates a solution model to a given [[Problem solving|problem]]. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields.<ref name ="SSEV">[http://pascal.computer.org/sev_display/index.action SEVOCAB: Software Systems Engineering Vocabulary]. Term: ''Flow chart''. Retrieved 31 July 2008.</ref>

== Overview ==
[[File:For-loop-diagram.png|thumb|right|Flowchart of a [[C (programming language)|C-style]] ''[[for loop|for&nbsp;loop]]'']]
Flowcharts are used in designing and documenting simple processes or programs. Like other types of diagrams, they help visualize what is going on and thereby help understand a process, and perhaps also find less-obvious features within the process, like flaws and [[Bottleneck (production)|bottleneck]]s. There are different types of flowcharts: each type has its own set of boxes and notations. The two most common types of boxes in a flowchart are:

* a processing step, usually called ''activity'', and denoted as a rectangular box.
* a decision, usually denoted as a diamond.
A flowchart is described as "cross-functional" when the chart is divided into different vertical or horizontal parts, to describe the control of different organizational units. A symbol appearing in a particular part is within the control of that organizational unit. A cross-functional flowchart allows the author to correctly locate the responsibility for performing an action or making a decision, and to show the responsibility of each organizational unit for different parts of a single process.

Flowcharts depict certain aspects of processes and are usually complemented by other types of diagram. For instance, [[Kaoru Ishikawa]] defined the flowchart as one of the seven basic tools of quality control, next to the [[histogram]], [[Pareto chart]], [[check sheet]], [[control chart]], [[Ishikawa diagram|cause-and-effect diagram]], and the [[scatter diagram]]. Similarly, in [[Unified Modeling Language|UML]], a standard concept-modeling notation used in software development, the [[activity diagram]], which is a type of flowchart, is just one of many different diagram types.

[[Nassi-Shneiderman diagram]]s and [[DRAKON|Drakon-charts]] are an alternative notation for process flow.

Common alternative names include: flow chart, process flowchart, functional flowchart, process map, process chart, functional process chart, business process model, process model, process [[flow diagram]], [[workflow|work flow]] diagram, business flow diagram. The terms "flowchart" and "flow chart" are used interchangeably.

The underlying [[Graph (discrete mathematics)|graph]] structure of a flowchart is a flow graph, which abstracts away node types, their contents and other ancillary information.

== History ==
The first structured method for documenting process flow, the "[[flow process chart]]", was introduced by [[Frank Bunker Gilbreth|Frank]] and [[Lillian Moller Gilbreth|Lillian Gilbreth]] in the presentation "Process Charts: First Steps in Finding the One Best Way to do Work", to members of the [[American Society of Mechanical Engineers|American Society of Mechanical Engineers (ASME)]] in 1921.<ref>Frank Bunker Gilbreth, Lillian Moller Gilbreth (1921) ''[https://engineering.purdue.edu/IE/GilbrethLibrary/gilbrethproject/processcharts.pdf Process Charts]''. American Society of Mechanical Engineers.</ref> The Gilbreths' tools quickly found their way into [[industrial engineering]] curricula. In the early 1930s, an industrial engineer, [[Allan H. Mogensen]] began to train business people in the use of some of the tools of industrial engineering at his Work Simplification Conferences in [[Lake Placid, New York|Lake Placid]], [[New York (state)|New York]].

Art Spinanger, a 1944 graduate of [[Allan H. Mogensen|Mogensen]]'s class, took the tools back to [[Procter and Gamble]] where he developed their Deliberate Methods Change Program. [[Benjamin S. Graham|Ben S. Graham]], another 1944 graduate, Director of Formcraft Engineering at [[Standard Register Industrial]], applied the flow process chart to information processing with his development of the multi-flow process chart, to present multiple documents and their relationships.<ref>{{cite web |last = Graham, Jr. |first = Ben S. |title = People come first |work = Keynote Address at ''Workflow Canada'' |url = http://www.worksimp.com/articles/keynoteworkflowcanada.htm |date = 10 June 1996}}</ref> In 1947, [[ASME]] adopted a symbol set derived from Gilbreth's original work as the "ASME Standard: Operation and Flow Process Charts."<ref>American Society of Mechanical Engineers (1947) ''ASME standard; operation and flow process charts''. New York, 1947. ([http://catalog.hathitrust.org/Record/005735891 online version])</ref>

[[Douglas Hartree]] in 1949 explained that [[Herman Goldstine]] and [[John von Neumann]] had developed a flowchart (originally, diagram) to plan computer programs.<ref>{{cite book | last = Hartree | first = Douglas | authorlink = Douglas Rayner Hartree |url=https://archive.org/stream/calculatinginstr00doug#page/112/mode/2up| title =Calculating Instruments and Machines | publisher = The University of Illinois Press | year = 1949 | page = 112}}</ref> His contemporary account was endorsed by IBM engineers<ref>{{cite book | last = Bashe | first = Charles | title = IBM's Early Computers | publisher = The MIT Press | year = 1986 | page = 327}}</ref> and by Goldstine's personal recollections.<ref>{{cite book | last = Goldstine | first = Herman | authorlink = Herman H. Goldstine | title = The Computer from Pascal to Von Neumann | publisher = Princeton University Press | year = 1972 | pages = 266–267 | isbn = 0-691-08104-2 }}</ref> The original programming flowcharts of Goldstine and von Neumann can be found in their unpublished report, "Planning and coding of problems for an electronic computing instrument, Part II, Volume 1" (1947), which is reproduced in von Neumann's collected works.<ref>{{cite book | last = Taub | first = Abraham | authorlink = Abraham Haskel Taub | title = John von Neumann Collected Works | publisher = Macmillan | year = 1963 | volume = 5 | pages = 80–151}}</ref>

The flowchart became a popular tool for describing [[computer algorithm]]s, but its popularity decreased in the 1970s, when interactive [[computer terminal]]s and [[third-generation programming language]]s became common tools for [[computer programming]], since algorithms can be expressed more concisely as [[source code]] in such [[programming language|languages]]. Often [[pseudo-code]] is used, which uses the common idioms of such languages without strictly adhering to the details of a particular one.

Nowadays flowcharts are still used for describing [[computer algorithm]]s.<ref>Bohl, Rynn: "Tools for Structured and Object-Oriented Design", Prentice Hall, 2007.</ref> Modern techniques such as [[Unified Modeling Language|UML]] [[activity diagram]]s and [[DRAKON|Drakon-charts]] can be considered to be extensions of the flowchart.

== Types ==
Sterneckert (2003) suggested that flowcharts can be modeled from the perspective of different user groups (such as managers, system analysts and clerks), and that there are four general types:<ref name="Ster03">Alan B. Sterneckert (2003) ''Critical Incident Management''. [https://books.google.com/books?id=8z93xStbEpAC&lpg=PP126&pg=PA126#v=onepage&q=&f=false p. 126]</ref>
* ''Document flowcharts'', showing controls over a document-flow through a system
* ''Data flowcharts'', showing controls over a data-flow in a system
* ''System flowcharts'', showing controls at a physical or resource level
* ''Program flowchart'', showing the controls in a program within a system
Notice that every type of flowchart focuses on some kind of control, rather than on the particular flow itself.<ref name="Ster03"/>

However, there are some different classifications. For example, Andrew Veronis (1978) named three basic types of flowcharts: the ''system flowchart'', the ''general flowchart'', and the ''detailed flowchart''.<ref>Andrew Veronis (1978) ''Microprocessors: Design and Applications''. [https://books.google.com/books?id=GZ9QAAAAMAAJ&q=%22three+basic+types+of+flowcharts+%28ie,+the+system+flowchart,+the+general+flowchart,+and+the+detailed+flowchart%29.%22&dq=%22three+basic+types+of+flowcharts+%28ie,+the+system+flowchart,+the+general+flowchart,+and+the+detailed+flowchart%29.%22&as_brr=0 p. 111]</ref> That same year Marilyn Bohl (1978) stated "in practice, two kinds of flowcharts are used in solution planning: ''system flowcharts'' and ''program flowcharts''...".<ref>Marilyn Bohl (1978) ''A Guide for Programmers''. p. 65.</ref> More recently, Mark A. Fryman (2001) identified more differences: "Decision flowcharts, logic flowcharts, systems flowcharts, product flowcharts, and process flowcharts are just a few of the different types of flowcharts that are used in business and government".<ref>Mark A. Fryman (2001) ''Quality and Process Improvement''. [https://books.google.com/books?id=M-_B7czAy0kC&pg=PA169#v=onepage&q=&f=false p. 169].</ref>

In addition, many diagram techniques are similar to flowcharts but carry a different name, such as [[Unified Modeling Language|UML]] [[activity diagram]]s.

== Building blocks ==

=== Common symbols ===
The [[American National Standards Institute]] (ANSI) set standards for flowcharts and their symbols in the 1960s.<ref name="ShellyVermaat2011">{{cite book|author1=Gary B. Shelly |author2=Misty E. Vermaat |title=Discovering Computers, Complete: Your Interactive Guide to the Digital World |date=2011 |publisher=Cengage Learning |isbn=1-111-53032-7 |pages=691–693}}</ref> The [[International Organization for Standardization]] (ISO) adopted the ANSI symbols in 1970.<ref name="Myler1998">{{cite book|author=Harley R. Myler |title=Fundamentals of Engineering Programming with C and Fortran |chapterurl=https://books.google.com/books?id=IisfMsdBe2IC&pg=PA32 |date=1998 |publisher=Cambridge University Press |isbn=978-0-521-62950-8 |pages=32–36|chapter=2.3 Flowcharts}}</ref> The current standard was revised in 1985.<ref>{{cite web |title=ISO 5807:1985 |url=https://www.iso.org/standard/11955.html |publisher=International Organization for Standardization |date=February 1985 |accessdate=23 July 2017}}</ref> Generally, flowcharts flow from top to bottom and left to right.<ref name=IBM1970>{{cite book |title=Flowcharting Techniques GC20-8152-1 |publisher=IBM |date=March 1970 |page=10}}</ref>
{| class="wikitable"
|-
! ANSI/ISO Shape
! Name
! Description
|-
| [[File:Flowchart Line.svg|100px]]
| Flowline (Arrowhead)<ref name="Myler1998" />
| Shows the process's order of operation. A line coming from one symbol and pointing at another.<ref name="ShellyVermaat2011" /> Arrowheads are added if the flow is not the standard top-to-bottom, left-to right.<ref name="Myler1998" />
|-
| [[File:Flowchart Terminal.svg|100px]]
| Terminal<ref name="ShellyVermaat2011" />
| Indicates the beginning and ending of a program or sub-process. Represented as a [[Stadium (geometry)|stadium]],<ref name="ShellyVermaat2011" /> oval or rounded (fillet) rectangle. They usually contain the word "Start" or "End", or another phrase signaling the start or end of a process, such as "submit inquiry" or "receive product".
|-
| [[File:Flowchart Process.svg|100px]]
| Process<ref name="Myler1998" />
| Represents a set of operations that changes value, form, or location of data. Represented as a [[rectangle]].<ref name="Myler1998" />
|-
| [[File:Flowchart Decision.svg|100px]]
| Decision<ref name="Myler1998" />
| Shows a conditional operation that determines which one of the two paths the program will take.<ref name="ShellyVermaat2011" /> The operation is commonly a yes/no question or true/false test. Represented as a diamond ([[rhombus]]).<ref name="Myler1998" />
|-
| [[File:Flowchart IO.svg|100px]]
| Input/Output<ref name="Myler1998" />
| Indicates the process of inputting and outputting data,<ref name="Myler1998" /> as in entering data or displaying results. Represented as a [[parallelogram]].<ref name="ShellyVermaat2011" />
|-
| [[File:Flowchart Annotation.svg|100px]]
| Annotation<ref name="ShellyVermaat2011" /> (Comment)<ref name="Myler1998" />
| Indicating additional information about a step the program. Represented as an open rectangle with a dashed or solid line connecting it to the corresponding symbol in the flowchart.<ref name="Myler1998" />
|-
| [[File:Flowchart Predefined Process.svg|100px]]
| Predefined Process<ref name="ShellyVermaat2011" />
| Shows named process which is defined elsewhere. Represented as a rectangle with double-struck vertical edges.<ref name="ShellyVermaat2011" />
|-
| [[File:Flowchart Connector.svg|50px]]
| On-page Connector<ref name="ShellyVermaat2011" />
| Pairs of labeled connectors replace long or confusing lines on a flowchart page. Represented by a small circle with a letter inside.<ref name="ShellyVermaat2011" /><ref name=RFF>{{cite web |title=What do the different flowchart shapes mean? |url=https://www.rff.com/flowchart_shapes.php |publisher=RFF Electronics |accessdate=23 July 2017}}</ref>
|-
| [[File:Off page connector.png|50px]]
| Off-page Connector<ref name="ShellyVermaat2011" />
| A labeled connector for use when the target is on another page. Represented as a [[Baseball field#Home plate|home plate]]-shaped [[pentagon]].<ref name="ShellyVermaat2011" /><ref name=RFF />
|}

=== Other symbols ===
The ANSI/ISO standards include symbols beyond the basic shapes. Some are:<ref name=IBM1970 /><ref name=RFF />

* ''Data File'' or ''Database'' represented by a cylinder (disk drive).
* ''Document'' represented as a [[rectangle]] with a wavy base.
* ''Manual input'' represented by [[quadrilateral]], with the top irregularly sloping up from left to right, like the side view of a keyboard.
* ''Manual operation'' represented by a [[trapezoid]] with the longest parallel side at the top, to represent an operation or adjustment to process that can only be made manually.
* ''Parallel Mode'' represented by two horizontal lines at the beginning or ending of simultaneous operations<ref name=IBM1970 />
* ''Preparation'' or ''Initialization'' represented by an elongated [[hexagon]], originally used for steps like setting a switch or initializing a routine.

For [[Parallel computing|parallel]] and [[Concurrent computing|concurrent]] processing the ''Parallel Mode'' horizontal lines<ref name="Valvano2011">{{cite book |author=Jonathan W. Valvano |title=Embedded Microcomputer Systems: Real Time Interfacing |date=2011 |publisher=Cengage Learning |isbn=1-111-42625-2 |pages=131–132 }}</ref> or a horizontal bar<ref name="Nakatsu2009">{{cite book |author=Robbie T. Nakatsu |title=Reasoning with Diagrams: Decision-Making and Problem-Solving with Diagrams |date=2009 |publisher=John Wiley & Sons |isbn=978-0-470-40072-2 |pages=68–69}}</ref> indicate the start or end of a section of processes that can be done independently:
* At a ''[[Fork–join model|fork]]'', the process creates one or more additional processes, indicated by a bar with one incoming path and two or more outgoing paths.
* At a ''join'', two or more processes continue as a single process, indicated by a bar with several incoming paths and one outgoing path. All processes must complete before the single process continues.<ref name="Nakatsu2009" />

== Software ==

=== Diagramming ===
[[File:Flowgorithm Editor.png|thumb|right|Flowgorithm]]
Any drawing program can be used to create flowchart diagrams, but these will have no underlying data model to share data with databases or other programs such as [[project management]] systems or [[spreadsheet]]. Some tools such as [[yEd]], [[Inkscape]] and [[Microsoft Visio]] offer special support for flowchart drawing. Many software packages exist that can create flowcharts automatically, either directly from a programming language source code, or from a flowchart description language.

There are several applications and [[visual programming languages]]<ref>Myers, Brad A. "[http://www.cs.cmu.edu/~bam/papers/chi86vltax.pdf Visual programming, programming by example, and program visualization: a taxonomy.]" ACM SIGCHI Bulletin. Vol. 17. No. 4. ACM, 1986.</ref> that use flowcharts to represent and execute programs. Generally these are used as teaching tools for beginner students. Examples include [[Flowgorithm]], [[Raptor (programming language)|Raptor]]. LARP, [[Visual Logic]], and VisiRule.

== See also ==
{{Col-begin}}
{{Col-break}}

===Related diagrams===
* [[Activity diagram]]
* [[Control flow diagram]]
* [[Control flow graph]]
* [[Data flow diagram]]
* [[Deployment flowchart]]
* [[DRAKON|Drakon-chart]]
* [[Flow map]]
* [[Functional flow block diagram]]
* [[Nassi–Shneiderman diagram]]
* [[State diagram]]
* [[Warnier/Orr diagram]]
{{Col-break}}

===Related subjects===
* [[Augmented transition network]]
* [[Business process mapping]]
* [[Interactive EasyFlow]]
* [[Process architecture]]
* [[Pseudocode]]
* [[Recursive transition network]]
* [[Unified Modeling Language]] (UML)
* [[Workflow]]
{{col-end}}

== References ==
{{Reflist|2}}

== Further reading ==
*{{cite book | last = ISO | year = 1985 | url = http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=11955 | title = Information processing – Documentation symbols and conventions for data, program and system flowcharts, program network charts and system resources charts | publisher = International Organization for Standardization| id = ISO 5807:1985}}
*ISO 10628: Flow Diagrams For Process Plants – General Rules
*[http://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/ECMA-4,%202nd%20Edition,%20September%201966.pdf ECMA 4: Flowcharts] (withdrawn – [http://www.ecma-international.org/publications/standards/Standardwithdrawn.htm list] of withdrawn standards)
* [[Schultheiss, Louis A.]], and Edward M. Heiliger. "[https://www.ideals.illinois.edu/bitstream/handle/2142/743/1963Schultheiss.pdf?sequence=2 Techniques of flow-charting]." (1963); with introduction by Edward Heiliger.

== External links ==
{{Commons|Flow chart}}
*[http://www.fh-jena.de/~kleine/history/software/IBM-FlowchartingTechniques-GC20-8152-1.pdf Flowcharting Techniques] An IBM manual from 1969 (5MB PDF format)
* [http://www.breezetree.com/images/flow-chart-symbols.png FlowChart Symbols List]
*[http://www.retroflow.ca/ Interactive RetroFlow] A free/open-source program specifically for creating flowcharts.

{{Authority control}}

[[Category:Quality control tools]]
[[Category:Diagrams]]
[[Category:Technical communication]]
[[Category:Computer programming]]
[[Category:Articles with example code]]
[[Category:American inventions]]
[[Category:Algorithm description languages]]

Revision as of 18:45, 5 September 2018

this is just some junk about symbols. omega lul

Retrieved from "https://en.wikipedia.org/w/index.php?title=Flowchart&oldid=858202917"