Flowchart

A flowchart is a schematic representation of an algorithm or a stepwise process, showing the steps as boxes of various kinds, and their order by connecting these with arrows. Flowcharts are used in designing or documenting a process or program. [http://pascal.computer.org/sev_display/index.action SEVOCAB: Software and Systems Engineering Vocabulary] . Term: "Flow chart". retrieved 31 July 2008.]

Overview

The two most common types of boxes in a flowchart:
* a processing step (usually called "activity", and denoted as a rectangular box)
* a decision (usually denoted as a diamond)

There are hundreds if not thousands of different types of flowcharts, each with their own repertoire of boxes and notational conventions.

A flowchart is described as "cross-functional" when the page is divided into different swimlanes describing the control of different organizational units. A symbol appearing in a particular "lane" is within the control of that organizational unit. This technique allows the analyst to locate the responsibility for performing an action or making a decision correctly, allowing the relationship between different organizational units with responsibility over a single process.

Flowcharts are used in designing and documenting complex processes. Like other types of diagrams, they help visualize what is going on and thereby help to find flaws, bottlenecks, or other non-obvious properties of a process.

Flowcharts depict just one aspect of processes and they are usually complemented with other types of diagrams. 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, cause-and-effect diagram, and scatter diagram [ [http://www.onesixsigma.com/node/7445 The seven basic tools of quality, by Matthew Moore, at www.onesixsigma.com] ] . Similarly, in the UML, a standard used in software development, the activity diagram, which a type of flowchart, is just one of many different diagram types.

An alternative for flowcharts are Nassi-Shneiderman diagrams

History

The first structured method for documenting process flow, the "flow process chart", was introduced by Frank Gilbreth to members of ASME in 1921 as the presentation “Process Charts—First Steps in Finding the One Best Way”. Gilbreth's tools quickly found their way into industrial engineering curricula. In the early 1930s, an industrial engineer, Allan H. Mogensen began training business people in the use of some of the tools of industrial engineering at his Work Simplification Conferences in Lake Placid, New York.

A 1944 graduate of Mogensen's class, Art Spinanger, took the tools back to Procter and Gamble where he developed their Deliberate Methods Change Program. Another 1944 graduate, Ben S. Graham, Director of Formcraft Engineering at Standard Register Corporation, adapted the flow process chart to information processing with his development of the multi-flow process chart to displays multiple documents and their relationships. In 1947, ASME adopted a symbol set derived from Gilbreth's original work as the ASME Standard for Process Charts.

According to Herman Goldstine, he developed flowcharts with John von Neumann at Princeton University in late 1946 and early 1947. [cite book | last = Goldstine | first = Herman | authorlink = Herman H. Goldstine | title = The Computer from Pascal to Von Neumann | publisher = Princeton University Press | date = 1972 | pages = 266-267 | isbn = 0-691-08104-2 ]

Flowcharts used to be a popular means for describing computer algorithms.They are still used for this purpose; modern techniques such as UML activity diagrams can be considered to be extensions of the flowchart.However, their popularity decreased when, in the 1970s, interactive computer terminals and third-generation programming languages became the common tools of the trade, since algorithms can be expressed much more concisely and readably as source code in such a language.Often, pseudo-code is used, which uses the common idioms of such languages without strictly adhering to the details of a particular one.

Flow chart building blocks

Symbols

A typical flowchart from older Computer Science textbooks may have the following kinds of symbols: ;Start and end symbols: Represented as lozenges, ovals or rounded rectangles, usually containing the word "Start" or "End", or another phrase signaling the start or end of a process, such as "submit enquiry" or "receive product".

;Arrows: Showing what's called "flow of control" in computer science. An arrow coming from one symbol and ending at another symbol represents that control passes to the symbol the arrow points to.

;Processing steps: Represented as rectangles. Examples: "Add 1 to X"; "replace identified part"; "save changes" or similar.

;Input/Output:Represented as a parallelogram. Examples: Get X from the user; display X.

;Conditional or decision: Represented as a diamond (rhombus). These typically contain a Yes/No question or True/False test. This symbol is unique in that it has two arrows coming out of it, usually from the bottom point and right point, one corresponding to Yes or True, and one corresponding to No or False. The arrows should always be labeled. More than two arrows can be used, but this is normally a clear indicator that a complex decision is being taken, in which case it may need to be broken-down further, or replaced with the "pre-defined process" symbol.

A number of other symbols that have less universal currency, such as:
* A "Document" represented as a rectangle with a wavy base;
* A "Manual input" represented by parallelogram, with the top irregularly sloping up from left to right. An example would be to signify data-entry from a form;
* A "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.
* A "Data File" represented by a cylinder

Flowcharts may contain other symbols, such as connectors, usually represented as circles, to represent converging paths in the flow chart. Circles will have more than one arrow coming into them but only one going out. Some flow charts may just have an arrow point to another arrow instead. These are useful to represent an iterative process (what in Computer Science is called a loop). A loop may, for example, consist of a connector where control first enters, processing steps, a conditional with one arrow exiting the loop, and one going back to the connector. Off-page connectors are often used to signify a connection to a (part of another) process held on another sheet or screen. It is important to remember to keep these connections logical in order. All processes should flow from top to bottom and left to right.

Examples

A flowchart for computing factorial N (N!)Where N! = 1 * 2 * 3 *...* N. This flowchart represents a "loop and a half" — a situation discussed in introductory programming textbooks that requires either a duplication of a component (to be both inside and outside the loop) or the component to be put inside a branch in the loop.

Software

Manual

Any vector-based 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 spreadsheets. Some tools offer special support for flowchart drawing, e.g., ConceptDraw, SmartDraw, "EDraw Flowchart", Visio, and OmniGraffle.

Automatic

Many software packages exist that can create flowcharts automatically, either directly from source code, or from a flowchart description language:

For example, Graph::Easy, a Perl package, takes a textual description of the graph, and uses the description to generate various output formats including HTML, ASCII or SVG. The example graph listed below was generated from the text shown below. The automatically generated SVG output is shown on the right:

graph { flow: south; }node.start { shape: rounded; fill: #0000FFff; }node.question { shape: diamond; fill: #ffff8a; }node.action { shape: rounded; fill: #8bef91; }

[ Lamp doesn't work ] { class: start } --> [ Lamp plugged in? ] { class: question; } -- No --> [ Plug in lamp ] { class: action; }

[ Lamp plugged in? ] --> [ Bulb burned out? ] { class: question; } -- Yes --> [ Replace bulb ] { class: action; }

[ Bulb burned out? ] -- No --> [ Buy new lamp ] { class: action; }

See also

* Activity diagram
* Augmented transition network
* Business process illustration
* Business Process Mapping
* Control flow graph
* Data flow diagram
* Functional flow block diagram
* N2 Chart
* Petri nets
* Process architecture
* Pseudocode
* Recursive transition network
* Sankey diagram
* State diagram
* Warnier-Orr
* Unified Modeling Language (UML)

References

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

External links

* [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.allclearonline.com/applications/DocumentLibraryManager/upload/program_intro.pdf Introduction to Programming in C++ flowchart and pseudocode] (PDF)
* [http://www.tipskey.com/manufacturing/advanced_flowchart.htm Advanced Flowchart] - Why and how to create advanced flowchart