[go: up one dir, main page]

0% found this document useful (0 votes)
13 views5 pages

Experiment 1

The document discusses flowcharts, their uses and basic symbols. It provides examples of flowcharts for simple programs like printing 'Hello World' and calculating the average of two numbers. Guidelines for creating flowcharts are also outlined.

Uploaded by

sayyedzuber5anas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views5 pages

Experiment 1

The document discusses flowcharts, their uses and basic symbols. It provides examples of flowcharts for simple programs like printing 'Hello World' and calculating the average of two numbers. Guidelines for creating flowcharts are also outlined.

Uploaded by

sayyedzuber5anas
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Experiment 1

Aim: Assignments on Flowchart

Theory:
What Is A Flowchart?

Flow charts are diagrams showing the exact sequence of logical steps. They use geometrical
shapes and arrows to show processes, relationships, and data/process flow. In other words,
flowcharts depict decisions and results of them.

In different fields, flowcharts are often used to analyze and manage processes. To put it simply,
it helps you visualize what the processes look like. That way, you can see all the bottlenecks
and flaws in them. The act of creating a chart is called flowcharting.

Flowchart In C Programming

Flowcharts are useful tools in software development. In C programming, flowcharts are often
used to represent algorithms or programs. They show the connections, flow of information, and
processes within an algorithm or a program. For example, here's an if else flowchart that's often
used in C programming.

Programmers use flowcharts in the program-planning, or the debugging process, often to solve
problems, even in complex programs.

A program might contain many flows of logic and processes, so flowcharts, using natural
language and symbols, can also help normal, non-technical people understand how the program
works. Here are some conventional symbols for a basic flowchart:
Example 1: Print “Hello World.” On-screen

When we first learn a programming language, our first program is often a simple “Hello World”
program. So, a chart of a simple program of printing a “Hello World” message onto the screen
should be like this:

Print "Hello World" on screen Flowchart


Example 2: Calculate The Average Of Two Numbers.

To calculate the average of two numbers, we can sum up those two numbers and divide the
result by 2. In other words, the formula for calculating the average of two numbers is: (number
1 + number 2)/2.

So the basic shapes of the chart should be like this:


Example 3

Another program is checking odd/even numbers. It is a basic conditional operation that


involves: inputting a number, determining whether it is odd or even, printing the result on-
screen. The chart should be something like this:

Input Number and Check If They Are Odd or Even Algorithm Flowchart
Flowchart Guidelines

To create a flowchart, you must follow the following current standard guideline:

• Step 1: Start the program.


• Step 2: Begin Process 1 of the program.
• Step 3: Check some conditions and take a Decision (“yes” or “no”).
• Step 4: If the decision is “yes”, proceed to Process 3. If the decision is “no”, proceed to
Process 2 and return to Step 2.
• Step 5: End of the program.

Additionally, the following can be helpful tips in creating flowcharts as well:

• You can only have one start and one end in your chart, no more, no less.
• On-page connectors are referred to by numbers, while off-page connectors are referred
to by alphabetical letters.
• The flow of processes is generally from top to bottom or left to right, not the other way
around.
• It would be best not to make the arrows cross each other.

Conclusion: Hence We have studied basics of Flowcharts .

You might also like