FLOW CHART PRESENTATION (AMA CAV GC)

Slide 1: 

3 1 2 SHOW TIME!!

Slide 8: 

F L O W C H A R T

Slide 9: 

HISTORY

Slide 10: 

The first structured method for documenting process flow, the "flow process chart", was introduced by Frank Gilbreth to members of ASME in 1921 as the presentation “Process Charts—First Steps in Finding the One Best Way”. Gilbreth's tools quickly found their way into industrial engineering curricula. In the early 1930s, an industrial engineer, Allan H. Mogensen began training business people in the use of some of the tools of industrial engineering at his Work Simplification Conferences in Lake Placid, New York.  A 1944 graduate of Mogensen's class, Art Spinanger, took the tools back to Procter and Gamble where he developed their Deliberate Methods Change Program. Another 1944 graduate, Ben S. Graham, Director of Formcraft Engineering at Standard Register Corporation, adapted the flow process chart to information processing with his development of the multi-flow process chart to displays multiple documents and their relationships. In 1947, ASME adopted a symbol set derived from Gilbreth's original work as the ASME Standard for Process Charts by Mishad,Ramsan,Raiaan.

Slide 11: 

Douglas Hartree explains that Herman Goldstine and John von Neumann developed the flow chart (originally, diagram) to plan computer programs.[2] His contemporary account is endorsed by IBM engineers [3] and by Goldstine's personal recollections.[4] The original programming flow charts of Goldstine and von Neumann can be seen in their unpublished report, "Planning and coding of problems for an electronic computing instrument, Part II, Volume 1," 1947, which is reproduced in von Neumann's collected works.[5] Flowcharts used to be a popular means for describing computer algorithms and are still used for this purpose.[6] Modern techniques such as UML activity diagrams can be considered to be extensions of the flowchart. However, their popularity decreased when, in the 1970s, interactive computer terminals and third-generation programming languages became the common tools of the trade, since algorithms can be expressed much more concisely and readably as source code in such a language. Often, pseudo-code is used, which uses the common idioms of such languages without strictly adhering to the details of a particular one.

Slide 12: 

BASIC FLOWCHART SYMBOLS

Slide 15: 

Here is a sample diagram:

Slide 16: 

TERMINATING SYMBOL Used to determine the beginning and the end of the program or point of interruption.

Slide 18: 

PROCESSING SYMBOL Used to present a group of program instruction that perform processing function of the program such as to perform arithmetic operations.

Slide 20: 

DECISSION SYMBOL Denotes a point in the program where more than one path can be taken.

Slide 22: 

ON-PAGE CONNECTOR - Non processing symbol which is used to connect one part of a flowchart to another without drawing flow lines.

Slide 24: 

PRE DEFINED PROCESS SYMBOL A specialized process symbol that represent a named operation

Slide 26: 

FLOWCHART DIRECTION INDICATORS OR FLOWLINES Used to show the direction of processing or data flow.

Slide 27: 

INPUT / OUTPUT SYMBOL Represent an instruction to an input or output device.

Slide 28: 

PREPARATION SYMBOL Used to represent an instruction or a group of instruction that will alter or modify a program’s course of execution.

Slide 29: 

Used instead of the on page connector to designate entry to or exit from a page when a flowchart requires more than one page. OFF PAGE CONNECTOR

On a flowchart does it always need a yes and no bit after each question or process? : 

THE “YES” / “NO” CONDITION On a flowchart does it always need a yes and no bit after each question or process? ?

Flow charts are based on binary code. Every input (question) has to have a response of 0 or 1 which is yes or no. After the response there is either an output or a "go to" command or an arrow that leads to the nest input of yes or no. You follow these on the flow chart by following arrows and answering questions. A flowchart is the visual replication or example of a computer's logic. It visually shows how they work on binary code. So yes every question has to have a distinct YES or NO response followed by an output or a Go To arrow. In binary code there are no maybes. Everything is 0 or 1, Yes or No. : 

Flow charts are based on binary code. Every input (question) has to have a response of 0 or 1 which is yes or no. After the response there is either an output or a "go to" command or an arrow that leads to the nest input of yes or no. You follow these on the flow chart by following arrows and answering questions. A flowchart is the visual replication or example of a computer's logic. It visually shows how they work on binary code. So yes every question has to have a distinct YES or NO response followed by an output or a Go To arrow. In binary code there are no maybes. Everything is 0 or 1, Yes or No. THE “YES” / “NO” CONDITION

Slide 32: 

HERE IS AN EXAMPLE OF A FLOWCHART

Slide 33: 

IS THE BOSS LOOKING? IS IT TIME TO GO HOME? START GO TO WORK TAKE A COFFEE BREAK DO SOME WORK GO HOME STOP Y N Y N

Slide 36: 

CLARITO BEJARASCO Sound effects: RYAN MERCADO ANTON GILBRETT PALMERO DOOPER RAYKYN NABUYA Sound editor: DOOPER RAYKYN NABUYA

Slide 37: 

Slides: DOOPER RAYKYN NABUYA ANTON GILBRETT PALMERO CLARITO BEJARASCO RYAN MERCADO ANGELO VALDEZ RAGIA GRACE CARRERA

Slide 38: 

Coffee maker: RYAN MERCADO RAGIA GRACE CARRERA Moral support: CLARITO BEJARASCO ANGELO JAMES VALDEZ Cook of all time: RYAN MERCADO Financial support RAGIA GRACE CARRERA CLARITO BEJARASCO Animation : DOOPER RAYKYN NABUYA

Slide 39: 

Cast: DOOPER RAYKYN NABUYA RYAN MERCADO CLARITO BEJARASCO ANTON GILBRETT PALMERO RAGIA GRACE CARRERA ANGELA JAMES VALDEZ

Slide 40: 

THANK YOU FOR WATCHING This project is for class presentation of AMA students section GC. Images, graphics, style and concepts are all originally made by the group members. No animals were harmed on this project Peace!