0% found this document useful (0 votes)
53 views8 pages

Kelompok 4 Flowchart: 2013020170 MAKMUR 2013020171 AHMAD SHOLIHIN 2014020198 MUH. ROBBY MALIK

The document discusses flowcharting and programming. It begins by introducing the topic of how programmers start writing programs and explains that the first step is to logically layout the problem using a flowchart. It then provides context on the origins of flowcharting from John von Neumann and describes some basic flowchart symbols like rectangles, diamonds, and arrows. The document also notes that while flowcharts can vary between programmers, they reveal how one thinks about solving a problem logically. It closes by emphasizing the importance of flowcharting for student programmers.

Uploaded by

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

Kelompok 4 Flowchart: 2013020170 MAKMUR 2013020171 AHMAD SHOLIHIN 2014020198 MUH. ROBBY MALIK

The document discusses flowcharting and programming. It begins by introducing the topic of how programmers start writing programs and explains that the first step is to logically layout the problem using a flowchart. It then provides context on the origins of flowcharting from John von Neumann and describes some basic flowchart symbols like rectangles, diamonds, and arrows. The document also notes that while flowcharts can vary between programmers, they reveal how one thinks about solving a problem logically. It closes by emphasizing the importance of flowcharting for student programmers.

Uploaded by

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

KELOMPOK 4

FLOWCHART
2013020170 MAKMUR
2013020171 AHMAD SHOLIHIN
2014020198 MUH. ROBBY MALIK

So far we have conserned ourselves primaily with computers and computer language.
Now we must ask ourselve how a programmer acrually sits down and begins to write a
program. The first step in programming any problem is to lay out in a logical fashion. A
layout of the kind used by programmers is called a flowchart.
Flowcharting is not restricted to the preparation of programs is ane particular language,
but is rather a broad overview of the specific problem independent of the particular
language taht is to be used in the final program
The intellectual father of flowcharting is John von Neuman. He and his collagues at the
Institute for Advanced Studies at Priceton, New Jersey, were the first to use a graphic aids in
outlining the solutions of prloblems on which they were working. Even though the
conversations of flowcharting are different now from those that von Neuman used, the spirit
and purpose of flowcharying remain the same

START

REMOVE
THE NEXT
TUBE

NO

IF
FINAL
TUBE

STOP

REMOVE
A TUBE

IS THIS
TUBE
DEFECTI
VE ?

REMOVE
THE NEXT
TUBE

YES

REPLACE IT
WITH A
GOOD
TUBE

IF
FINAL
TUBE

STOP

All that flowchart indicate is that each tube should be tasted until detective
tube have been replaced. We can then assume that the machine will be in
proper working order.

SYMBOL OF FLOWCHARTING
This is the terminal symbol, which indicate either the start of the finish of a prgram

Parallelogram symbol, this is used as in input/ output symbol. It indicated that we either bring something to the
program or we take something from the program

The rectangel symbol, stand for processing, in other words a place in the program where action is taken.

The diamond symbol, indicate that a decision has to made. It is usually in the form od question that has to be
answerd.

Arrow, the direction of flow of the program, that show the order in which the different action in the program are
performed

Flowchart are not unique. It is possible for two different programmers to


write programs to solve the same problem, and yet the flowchart and
the programs may be quite different.

A flowchart is almost a picture of the way a person thinks about a


problem, and of course w know that there are many cases in which
people approach the same problem quite differently.

When documentation is not available, it is possible to make a flowchart


from an applications program. This is really working backwards. In the
normal procedure the flowchart would come before the applications
program. However, when the original flowchart has been lost or
destroyed, it may be necessary to create it all over again in order to
understand the program for which it was a preparatory step.

On the first things that a student programmer is taught is flowcharting.


A new programmers ability is frequently revealed by his ability to
flowchart problems that are given to him to solve, since it requires a
logical and analytical mind to break down a problem into small parts and
then write a clear and inclusive flowchart of all those parts

Thank You
For
Attention

You might also like