Flowchart and Algorithm

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. Flowcharts are
used in analyzing, designing, documenting or managing a process or program in various fields.
An algorithm is a step-by-step procedure that defines a set of instructions that must be carried out
in a specific order to produce the desired result. Algorithms are generally developed
independently of underlying languages, which means that an algorithm can be implemented in
more than one programming language.

History of Flowchart
Flowcharts to document business processes came into use in the 1920s and ‘30s. In 1921,
industrial engineers Frank and Lillian Gilbreth introduced the “Flow Process Chart” to the
American Society of Mechanical Engineers (ASME). In the early 1930s, industrial engineer
Allan H. Morgensen used Gilbreth’s tools to present conferences on making work more efficient
to businesspeople at his company. In the 1940s, two Morgensen students, Art Spinanger and
Ben S. Graham, spread the methods more widely. Spinanger introduced the work simplification
methods to Procter and Gamble. Graham, a director at Standard Register Industrial, adapted flow
process charts to information processing. In 1947, ASME adopted a symbol system for Flow
Process Charts, derived from the Gilbreths’ original work.
Also, in the late ‘40s, Herman Goldstine and John Van Neumann used flowcharts to develop
computer programs, and diagramming soon became increasingly popular for computer programs
and algorithms of all kinds. Flowcharts are still used for programming today, although
pseudocode, a combination of words and coding language meant for human reading, is often
used to depict deeper levels of detail and get closer to a final product.
In Japan, Kaoru Ishikawa (1915-1989), a key figure in quality initiatives in manufacturing,
named flowcharts as one of the key tools of quality control, along with complementary tools
such as the Histogram, Check Sheet and Cause-and-Effect Diagram, now often called the
Ishikawa Diagram.

Uses of Flowchart
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.
Flowcharts are used in analyzing, designing, documenting or managing a process or program in
various fields.
Types of Flowcharts
1. The Process Flowchart or Communication Flow Chart

A process flowchart or process flow diagram is probably the most versatile of the four
commonly used flowchart types because it can be applied to virtually anything. Process
flowcharts or process mapping can help quickly explain how something gets done in your
organization. Sometimes, these types use a standard language or notation, like Business Process
Modeling and Notation. Use a process flow diagram to:

 Map out roles and responsibilities within an organization to gain clarity.

 Describe the manufacturing process or inputs that go into creating a finished product.
 Explain how information is communicated throughout an organization or process.
 Draw up a proposal for a new process or project to understand its scope and steps.
 Show the way you wake up in the morning, as shown below.

2. The Workflow Chart or Workflow Diagram

Understand How Data and Documents Flow Within Your Organization

A workflow chart shows the way a business or process functions. The below example
illustrates the steps required for a potential customer to renew a policy through a
company website. This type of workflow diagram can be used to:

 train new employees

 discover potential problem areas
 create or organize your team around a new standard operating procedure
 clarify business operations by showing a high-level overview
3.  The Swimlane Flowchart

Describe How Separate Departments, Processes or Employees Interact

The swim lane flowchart comes in handy when you need to show multiple flows of
information side by side. Swimlane diagrams might sound really like a workflow
diagram, but the key here is that it allows you to create different categories where activity
takes place.
A swim lane flowchart or diagram is great for documenting a whole process that interacts
with different segments of an organization or requires collaboration among different
teams. The below example illustrates the way an internal-facing department runs parallel
with an external-facing one and at what times in the process they interact with each other.
More complicated diagrams could include five, six, or even more swim lanes, like for
each department within an organization or each role on a cross-functional team. The goal
of swim lanes is to clarify and simplify a flowchart, though, so avoid adding too many
lanes and keep things simple!
4. The Data Flowchart

See Where Data Flows in and Out of an Information System with a Data Flow Diagram

A data flowchart or data flow diagram shows the way data is processed. It comes in
handy when you want to design or analyze a system. Although most often used for
software development and design, it can be used to analyze any type of information flow,
like how information moves through a business. The below example shows a typical sales
funnel. In this case the “data” is consumer behavior.

Best Practices in Flowcharting

1. Use Consistent Design Elements

Shapes, lines and texts within a flowchart diagram should be consistent.
2. Keep Everything on One Page
It is good practice to make sure that the flowchart fits on a single page and the
text remains readable. When a diagram becomes too large to fit on a page, it's
advisable to divide it into multiple charts and connect them with hyperlinks.
3. Flow Data from Left to Right
Structuring a flowchart from left to right makes the information easier to read and
comprehend.
4. Use a Split Path Instead of a Traditional Decision Symbol
Traditional flowcharts use a diamond symbol to represent a decision.
5. Place Return Lines Under the Flow Diagram
Since we naturally read text from the top of the page down, it is logical that return
lines should be placed under the flowchart rather than above. 
Create a Flow Chart: Taking a Bath

Start

Don't take a No Yes I should take

Is it
bath right a bath
time
now; instead, because I
for me
play. stink so bad.
to take
a bath?

I'm finished
with my bath.

Do I Yes, I do, and

You don't, No Yes I'm going to
feel
you quickly keep playing
clean
take a bath. online games.
now?

End
Brushing Your Teeth:

Start

Are my
Teeth Brush your Teeth
clean?

No