- Learning to Program—The stages of programming
- Learning to Program – Some Terms You Should Understand
- Learning to Program – IPO Charts (Stage 1)
- Learn to Program- Flowcharting (Stage 2)
- Learning to Program – Flowcharting (Stage 2). — Decisions and Loops
- Learning to Program—Flowcharting (Stage 2) – Case Statements
- Learning to Program (Stage 2)—Flowcharting – Methods and Classes
- Learning to Program – Structure and Spaghetti Code
- Learning to Program – Pseudocode (Stage 3) an overview
- Learning to Program – Stage 3 Pseudocode commands and reserved words
- Learning to Program—Stage 3 Pseudocode examples Part 1
- Learning to Program – Stage 3 Psuedocode (Arrays)
- Learning to Program – Stage 3: Pseudocode—Methods
- Learning To Program—Stage 3.5 (UML Diagrams)
- Learning to Program – (Stage 4) Coding
- Learning To Program—Stage 5 Testing
- Learning to Program—Stage 6 (Documentation)
- Learning to Program – Stage 7 (Maintenance)
- Learning to Program—Random Thoughts with a Theme
- Learning to Program- Two Main Types of Errors
- Learning to Program – Integrated Development Environments (IDE’s)
- Learning to Program
This is an overview of flowcharting. There are a lot of things that won’t be covered in this post, however I will touch on them in future posts. My intention is to cover flowcharting as fully as possible, and then move on to pseudocode.
A flowchart is a graphical (Visual) example of the sequence in a program and the flow of the data through the program. You may have seen flowcharts in other applications (such as troubleshooting a problem, process controls, or other aspects). These are similar to how flowcharts in programs work, and in some cases even use the same symbols.
Symbols used in Flowcharting:
In order to accurately show the symbols, I will create an image with them all listed. Also, I will include the text from each symbol in the image.
An example of flowcharting:
This example builds upon the example that I used for the IPO charts in the previous post.
In the above example, I did not include a symbol for assigning the variables. The assignment is optional in flowcharts—as long as you know that it MUST happen in the program. In pseudocode, you will see the assignment at the top (where it belongs). This is because in pseudocode, you’re as close to the actual language as you can be. So, you have to follow the order and requirements of the language that you’re coding for.
In fact, in a flowchart, you are not required to use variables at all. The flowchart is meant as an intermediate step between the IPO chart and the pseudocode. However, if you don’t intend to do pseudocode prior to code, then you should include the assignment and variables in your flowchart.
Next, I will dig a little deeper into the various flows that you may encounter. I will explain the Decision symbol a little more, and follow up with loops. Finally, I will start to describe methods and classes.
Have a great day:)