Guidelines for using pseudocode1. Use English-like statements that precisely describe specific operations.2. Avoid syntactic elements from the target programming language.3. Write pseudocode at the level of intent, rather than how the approach will be implemnet in the target language. 4. Write pseudocode at a low enough level that generating code from it will nearly automatica.Once the pseudocode is written, you build the code around it and the pseudoccode turns into programming-language comments.
Benefits you can expect from using this style of pseudocode1. Pseudocode makes reviews easier.2. Pseudocode supports the idea of iterative refinement.You start with a high level design, refine the design to pseudocode, and then refine the pseudocode to source code.3 . Pseudocode makes changes easier.A few lines of pseudocode are easier to change than a page of code.4. Pseudocode minimizes commenting effort.5. Pseudocode is easier to maintain than other forms of design documentation.With other approaches, design is separated from The Code, And When One Changes, The Two Fall Out of Agreement.
