0% found this document useful (0 votes)
230 views9 pages

Flow Chart:: Flowchart Symbols

A flow chart uses symbols to represent steps in a process and arrows to show the direction of flow. Common symbols include rectangles for processes, ovals for start/stop, diamonds for decisions, and arrows for connections. An IPO chart shows the input, processing, and output of an algorithm or process. A Gantt chart uses horizontal bars to illustrate the timing and dependencies of tasks in a project schedule. A PERT chart represents tasks as nodes and dependencies as arrows to analyze the critical path of a project.

Uploaded by

neha
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
0% found this document useful (0 votes)
230 views9 pages

Flow Chart:: Flowchart Symbols

A flow chart uses symbols to represent steps in a process and arrows to show the direction of flow. Common symbols include rectangles for processes, ovals for start/stop, diamonds for decisions, and arrows for connections. An IPO chart shows the input, processing, and output of an algorithm or process. A Gantt chart uses horizontal bars to illustrate the timing and dependencies of tasks in a project schedule. A PERT chart represents tasks as nodes and dependencies as arrows to analyze the critical path of a project.

Uploaded by

neha
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1/ 9

FLOW CHART:

A flow chart is a graphical or symbolic representation of a process. Each step


in the process is represented by a different symbol and contains a short
description of the process step. The flow chart symbols are linked together
with arrows showing the process flow direction.

Flowchart Symbols
Here is a chart for some of the common symbols used in drawing
flowcharts.

Symbol Symbol Name Purpose

Used at the beginning and end of the


Start/Stop algorithm to show start and end of
the program.

Indicates processes like


Process mathematical operations.

Used for denoting program inputs


Input/ Output
and outputs.

Stands for decision statements in a


program, where answer is usually
Decision Yes or No.

Shows relationships between


Arrow different shapes.
Connects two or more parts of a
flowchart, which are on the same
On-page Connector page.

Connects two parts of a flowchart


which are spread over different
Off-page Connector pages.

Guidelines for Developing Flowcharts


These are some points to keep in mind while developing a flowchart −

 Flowchart can have only one start and one stop symbol

 On-page connectors are referenced using numbers

 Off-page connectors are referenced using alphabets

 General flow of processes is top to bottom or left to right

 Arrows should not cross each other


Here is a flowchart to calculate the average of two numbers.

Pseudo-code: Pseudocode is an informal high-level


description of a computer program or algorithm. It is written in
symbolic code which must be translated into a programming
language before it can be executed. It uses short terms or simple
English language syntaxes to write code for programs before it is
actually converted into a specific programming language. This is
done to identify top level flow errors, and understand the
programming data flows that the final program is going to use.
A pseudocode does not conform to any programming language and
expresses logic in plain English.
 It may specify the physical programming logic without actual
coding during and after the physical design.
 It is used in conjunction with structured programming.
 It replaces the flowcharts of a program.
Advantages of pseudocode –
• Pseudocode is understood by the programmers of all types.

• it enables the programmer to concentrate only on the algorithm


part of the code development.

• It cannot be compiled into an executable program. Example, Java


code : if (i < 10) { i++; } pseudocode :if i is less than 10, increment i
by 1.

IPO charts

An IPO chart records the input, process, and output of a process, or program
module. It is commonly used when designing spreadsheet formulas,
calculated fields in databases, and algorithms in programming.

A simple example is to calculate someone's age. Work backwards, starting


with deciding what the output should be (Age)

INPUT PROCESSING OUTPUT


Age

Now ask what data is needed to generate this output (date of birth, current
date)

INPUT PROCESSING OUTPUT


Date of birth
Age
Current date
Finally, work out the algorithm (calculation strategy) to get the output from
the input: in this case, find the number of days between the date of birth
and the current date, divide by 365.25 to convert it to years.

INPUT PROCESSING OUTPUT


Date of
birth (Current Date - Date of Birth) /
Age
Current 365.25
date

Another more complex example...

HIPO Diagram
HIPO (Hierarchical Input Process Output) diagram is a combination of two
organized method to analyze the system and provide the means of
documentation. HIPO model was developed by IBM in year 1970.

HIPO diagram represents the hierarchy of modules in the software system.


Analyst uses HIPO diagram in order to obtain high-level view of system
functions. It decomposes functions into sub-functions in a hierarchical
manner. It depicts the functions performed by system.

HIPO diagrams are good for documentation purpose. Their graphical


representation makes it easier for designers and managers to get the
pictorial idea of the system structure.

In contrast to IPO (Input Process Output) diagram, which depicts the flow
of control and data in a module, HIPO does not provide any information
about data flow or control flow.

Example
Both parts of HIPO diagram, Hierarchical presentation and IPO Chart are
used for structure design of software program as well as documentation of
the same.
Gantt chart
Gantt chart is a horizontal bar chart developed as a production control tool in
1917 by Henry L. Gantt, an American engineer and social scientist. Frequently
used in project management, a Gantt chart provides a graphical illustration of
a schedule that helps to plan, coordinate, and track specific tasks in a
project.
Gantt charts may be simple versions created on graph paper or more complex
automated versions created using project management applications such as
Microsoft Project or Excel.

A Gantt chart is constructed with a horizontal axis representing the total time
span of the project, broken down into increments (for example, days, weeks,
or months) and a vertical axis representing the tasks that make up the project
(for example, if the project is outfitting your computer with new software, the
major tasks involved might be: conduct research, choose software, install
software). Horizontal bars of varying lengths represent the sequences, timing,
and time span for each task. Using the same example, you would put
"conduct research" at the top of the verticle axis and draw a bar on the graph
that represents the amount of time you expect to spend on the research, and
then enter the other tasks below the first one and representative bars at the
points in time when you expect to undertake them. The bar spans may
overlap, as, for example, you may conduct research and choose software
during the same time span. As the project progresses, secondary bars,
arrowheads, or darkened bars may be added to indicate completed tasks, or
the portions of tasks that have been completed. A vertical line is used to
represent the report date.

What Is a PERT Chart?


A PERT chart is a project management tool that provides a graphical
representation of a project's timeline. The Program Evaluation Review Technique
(PERT) breaks down the individual tasks of a project for analysis. PERT charts
are considered preferable to Gantt charts because they identify task
dependencies, but they're often more difficult to interpret.
A PERT chart presents a graphic illustration of a project as a network diagram
consisting of numbered nodes (either circles or rectangles) representing
events, or milestones in the project linked by labelled vectors (directional
lines) representing tasks in the project. The direction of the arrows on the lines
indicates the sequence of tasks. In the diagram, for example, the tasks
between nodes 1, 2, 4, 8, and 10 must be completed in sequence. These are
called dependent or serial tasks. The tasks between nodes 1 and 2, and
nodes 1 and 3 are not dependent on the completion of one to start the other
and can be undertaken simultaneously. These tasks are
called parallel or concurrent tasks. Tasks that must be completed in
sequence but that don't require resources or completion time are considered
to have event dependency. These are represented by dotted lines with arrows
and are called dummy activities. For example, the dashed arrow linking nodes
6 and 9 indicates that the system files must be converted before the user test
can take place, but that the resources and time required to prepare for the
user test (writing the user manual and user training) are on another path.
Numbers on the opposite sides of the vectors indicate the time allotted for the
task.

The PERT chart is sometimes preferred over the Gantt chart, another popular
project management charting method, because it clearly illustrates task
dependencies. On the other hand, the PERT chart can be much more difficult
to interpret, especially on complex projects. Frequently, project managers use
both techniques.

----------------

You might also like