How to Use Data on a Flowchart

Programmers and business analysts use flowcharts to streamline operations.

Flowcharts are visual representations of what happens to data during any given process. The charts are made up of symbols that describe input and output, data processing, actions and calculation information. These symbols include circles, parallelograms, rectangles and ovals. Computer programmers, department heads, business analysts and more will use the data found on a flowchart to examine, edit and streamline processes. While doing so, those working with the flowcharts may convert that data to pseudocode for a software application or into reports. The end result of the data will determine how you use the flowchart to accomplish that goal.

Things You'll Need

• Pen
• Paper
• Word processing program (optional)

Instructions

Programming

1. Look over the flowchart and see if you can break it up into different sections. For example, "Customer Identification," "Customer Database" and "Customer History" may be appropriate.

2. Read the flowchart from the start and write down each step as it happens in pseudocode format. For example, "Customer enters account number. Verify account number. If correct account number, let customer in to see customer history" may be appropriate.

3. Continue doing this for each section until you finish. Go through the pseudocode when you finish it and double-check the processes for logical accuracy and flow. For example, if the customer is required to enter a password that is only to include capital letters, be sure you included pseudocode that would instruct the program to check the password did not include numbers.

4. Have a colleague or teammate double-check your pseudocode for accuracy and begin to translate the pseudocode into the programming language of your choice.

Business Processes

1. Review the flowchart from beginning to end and note any sections that raise questions. Read through it a second time, spending more time at the confusing sections and write down any findings or conclusions you come to, especially if you feel the steps are not ordered logically.

2. Examine each section of the process for efficiency by asking yourself if any of the processes could be done more efficiently. Write down your findings.

3. Write down a more efficient process, if you find one, and read through the flowchart again using your more efficient method. Double-check to make sure your more efficient process does not hinder or sacrifice security processes that may exist in the rest of the flowchart. Present your findings to the necessary department heads.

Tips & Warnings

• If you need to, make extra copies of the flowchart so you can write on a copy to help you in your thought processes as you analyze and work with the data.

• Flowcharts should be written in laymen terms. If you find the flowchart you're working with has several technical descriptions you do not understand, you'll need to seek clarification from the author of the flowchart or from your information technology department.

References

• "Programming Logic and Design, Fifth Edition"; Joyce Farrell; 2008
• Robot C: Pseudocode & Flow Charts