Information About

Flowchart
  CATEGORIES ABOUT FLOWCHART
   
algorithms
   
software engineering
   
quality control tools
   
diagrams
   
technical communication
   
computer programming
   
articles with example code
   
APPAREL
BABY
BEAUTY
BOOKS
CAR TOYS
CELL PHONES
DVD'S
ELECTRONICS
GOURMET FOOD
GROCERIES
HEALTH & PERSONAL
HOME & GARDEN
JEWELRY
MUSIC
MUSIC INSTRUMENTS
OFFICE PRODUCTS
SOFTWARE
SPORTING GOODS
TOOLS & HARDWARE
TOYS
VIDEO GAMES
SHOPPING HOME
MORE SHOPPING...



A flowchart (also spelled '''flow-chart''' and '''flow chart''') is a Schematic representation of an Algorithm or a Process . A flowchart is one of the seven basic tools of quality control, which also includes the Histogram , Pareto Chart , Check Sheet , Control Chart , Cause-and-effect Diagram , and Scatter Diagram (see Quality Management Glossary ). They are commonly used in business/economic presentations to help the audience visualize the content better, or to find flaws in the process. Alternatively, one can use Nassi-Shneiderman Diagram s.


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 rectangle, 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

  • ''Note: All process symbols within a flowchart should be numbered. Normally a number is inserted inside the top of the shape to indicate which step the process is within the flowchart.''

    • 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.


A flowchart is described as "cross-functional" when the page is divided into different "lanes" 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.


HISTORY