The example that was put together for the Pseudocode and the Flow diagram are very elaborate and well thought out. It did show the relation between the Pseudocode structure as the written language and the Flow diagram that indicate the application of the Pseudocode. Within the whole process the Pseudocode and Flow diagram does correlate to each other.

The program was built in a straightforward fashion. If you would relate to the Pseudocode herein our discussion board, you would notice that it is a step-by-step procedure that has been put up as a flowing structure. Flow diagram makes that application feasible as it readjust the procedures for proper setup and illustrations that is easily understood by programmers that want to apply the system. The pseudocode and flow diagram created in this example are great useable creation. I would however tweak the setup only when a prior and necessary procedure needed to be added base on the engineering of the program. I would also check the designing restraints of the pseudocode that I will build before I would create a flow diagram as sometimes in real world the pseudocode we create will not fit the case.

The advantage of using a flowchart is that programmers and designers will be able to outline and tweak the structures of a given program to their desired outcome . As programmers use it as a default structure in creating two deviating figures from having Boolean system incorporated as such “If” and “then” structures that will correlate into having a rhetorical questions answerable by “yes” and “no” structure. As the plain yes or no and true or false play into scene the chart and figure moves apart as desired answers have certain consequences built. The yes or no and true or false structure will outline two deviating answers to each other that separates each other apart. This create the uniqueness in the flow diagram. As