One of the main advantages in using pseudocode lies in the fact that it is in essence a programming language. It is written in a highly simple, unstructured programming language that can be easily transitioned to the main programming language. Pseudocode requires the least amount of modification when transitioning from model to program. Flowcharts probably represent ideal solutions, but may not be easy to implement into the program. With the use of pseudocoding, the probability is high that the design specifications and implemented program will be very close.
Programmers generally require time to learn new programming languages. The advantage in using pseudocode is its inherent simplicity. Pseudocode is familiar and very similar to reading instructions; each step is detailed in an English-like language. For this reason, the learning curve is not very steep and programmers who can read and write can create pseudocode with relative ease. The pseudocode instructions are easily understood.
Pseudocode tends to place greater emphasis on details, limiting its perspective on the bigger picture. In the case of flowcharts, for example, the graphics make it possible to present a really big picture. Pseudocode cannot show logic flows like a flowchart or other modeling tools can. Pseudocode models are very detail-oriented, requiring extreme concentration and practice. This is not the case with flowcharts, which provide an overview of the logic being presented, making them understood at higher levels.
One of the disadvantages in using pseudocode is the lack of standards. The analyst's logic in writing the instructions may not be viewed as logical by the programmer. Pseudocode has an unstructured nature with few rules, making it hard to standardize. This causes problems in terms of rejection on the part of a programmer of what may be a good design, on the basis of inappropriate criteria. Simply put, a programmer may fail to see the logic behind what someone else has written and reject it.