Guidelines for designing a good pseudocode

1. The statements must be short, clear and readable.
2. The statements must not have more than one meaning (i.e., should not be ambiguous).
3. The pseudocode lines should be clearly outlined and indented.
4. A pseudocode must have a Begin and an end.
i.e., a pseudocode should show clearly the start and stop of executable statements and the control structures.

5. The input, output and processing statements should be clearly stated using keywords such as PRINT, READ, INPUT, etc.