Flowcharting is probably the most useful tool available to developers in the design and implementation of Information Systems. Unfortunately, little standardization has occurred in this important area. Unlike engineers and architects who have standardized, the DP/IT professionals use their own unique approaches. Some standardization has occurred in programming flowcharts, but to a large degree they represent personal preferences and it is still somewhat difficult to read a flowchart without explanation. "PRIDE" has developed standards for flowcharting through all phases of design.

"PRIDE" uses flowcharting as a communication, design and planning tool in a manner similar to the way engineers use flow diagrams to describe processes. Flowcharts are graphic representations of a proposed design. As a result, design decisions can be made using flowcharts as a basis, instead of making changes after the designs have been translated into hard form. For example, it is extremely difficult to add a bathroom onto a house after it has been completed if it was not planned for in the initial design. This is certainly true in the design and development of information systems. As a design and planning tool, flowcharting permits system designers to plan each design step and test it by review before implementation.

Since they are graphic, flowcharts are readily understood by both the data processing professional and the non-data processing oriented user. Through flowcharting, the old proverb "a picture is worth a thousand words" can be applied.

By using consistent flowcharting techniques throughout the system and programming functions, communication problems can be minimized. Professionals can be easily transferred from project to project because each one can understand the other's designs. This permits project managers to utilize available manpower efficiently.

When user reviews are conducted at the end of each design phase, the flowchart becomes a basic presentation tool. User personnel quickly become accustomed to presentations that use flowcharts as a visual aid. System problem areas are isolated and the necessary management decisions can be obtained to correct these situations.

Aside from other schematics used in "PRIDE"-ISEM, there are three basic flowcharts used in the methodology, all of which make use of ANSII standard symbols:

• System Flowcharts - showing sub-systems - prepared in ISEM Phase 2.

• Sub-System Flowcharts - showing procedures - prepared in ISEM Phase 3.

• Computer Procedure Flowcharts - showing programs - prepared in ISEM Phase 4-II.

These flowcharts reflect "layered documentation" whereby each flowchart defines the next level of detail in the system structure or hierarchy. More importantly, they show the movement of data through processes.

SYSTEM FLOWCHART SYMBOLS

For a sample System Flowchart, click HERE.

SUB-SYSTEM FLOWCHART SYMBOLS

For sample Sub-System Flowcharts, click for Batch Example or Interactive Example. Sub-System Flowcharts can be drawn either horizontally (as shown in the examples) or vertically.

COMPUTER PROCEDURE FLOWCHART SYMBOLS

The Computer Procedure Flowchart uses the same symbols as the Sub-System Flowchart (as well as the same approach to drawing). For a sample Computer Procedure Flowchart, click for HERE. Like the Sub-System Flowchart, the Computer Procedure Flowchart can be drawn either horizontally (as shown in the example) or vertically.

INFORMATION FLOW DIAGRAM (IFD) SYMBOLS