Learn to Write Pseudocode: What It Is and Why You Need It

PDF download Download Article
Step-by-step guide to using pseudocode in software development
PDF download Download Article

Want to learn how to write pseudocode? Pseudocode is a step-by-step written outline of your code that you can transcribe into the programming language you’re working with. In other words, you’re writing the flow of your code in plain language rather than official coding syntax. Many programmers use pseudocode to plan out the logic of an algorithm before writing it in code. This wikiHow shows you how to write a pseudocode document for your computer program.

Things You Should Know

  • Pseudocode is useful for planning your program and troubleshooting the logic.
  • Use a simple plain-text editor or even pen and paper to write your pseudocode.
  • Write a statement for each line of logic in your program.
Part 1
Part 1 of 3:

Pseudocode Basics

PDF download Download Article
  1. Pseudocode is used to show how a computing algorithm should work. Coders often use pseudocode as an intermediate step in programming in between the initial planning stage and the stage of writing actual executable code. Some other uses of pseudocode include the following: [1]
    • Describing how an algorithm should work. Pseudocode can illustrate where a particular construct, mechanism, or technique could or must appear in a program.
    • Explaining a computing process to less-technical users. Computers need a very strict input syntax to run a program, but humans (especially non-programmers) may find it easier to understand a more fluid, subjective language that clearly states the purpose of each line of code.
    • Designing code in a group setting. High-level software architects will often include pseudocode in their design process to help solve a complex problem they see their programmers running into. If you are developing a program with other coders, you may find that pseudocode helps make your intentions clear.

    Pseudocode serves as a guide for thinking through programming problems, and a communication option that can help you explain your ideas to other people.

  2. There is no set syntax or rules that you absolutely must use for pseudocode, but it is a common professional courtesy to use standard pseudocode structures that other programmers can easily understand. [2] If you are coding a project by yourself, then the most important thing is that the pseudocode helps you structure your thoughts and enact your plan.
    • If you are working with others on a project—whether they are your peers, junior programmers, or non-technical collaborators—it is important to use at least some standard structures so that everyone else can easily understand your intent.
    • If you are enrolled in a programming course at a university, a coding camp, or a company, you will likely be tested against a taught pseudocode "standard". This standard often varies between institutions and teachers.

    Clarity is a primary goal of pseudocode, and it may help if you work within accepted programming conventions. As you develop your pseudocode into actual code, you will need to transcribe it into a programming language – so it can help to structure your outline with this in mind.

    Advertisement
  3. It can be easy to revert to writing in code once you hit your stride. Remembering the purpose of your pseudocode—explaining what each line of the program should do—will keep you grounded while creating the pseudocode document.
    4. Advertisement
Part 2
Part 2 of 3:

Writing Good Pseudocode

PDF download Download Article
  1. It can be tempting to use a word processor (e.g., Microsoft Word) or a similar program to create a rich-text document, but pseudocode needs as little formatting as possible to keep it simple.
    • You can use pen and paper to write your pseudocode! Try different formats to find what works best for your creative programming process.

    Plain-text editors include Notepad (Windows) and TextEdit (Mac).

  2. Dedicating a line or two to explaining the purpose of your code will help set up the rest of the document, and it will also save you the task of explaining the program's function to each person to whom you show the pseudocode. [3]
  3. Each statement in your pseudocode should express just one action for the computer. In most cases, if the task list is properly drawn, then each task will correspond to one line of pseudocode. Consider writing out your task list, then translating that list into pseudocode, then gradually developing that pseudocode into actual, computer-readable code. [4]
  4. Using white spaces between "blocks" of text will help keep different components of your pseudocode isolated, and indenting different pieces of each block will indicate that those pieces of pseudocode go under a less-indented section.
    • For example, a section of pseudocode that discusses entering a number should all be in the same "block", while the next section (e.g., the section that discusses the output) should be in a different block.
  5. Depending on your pseudocode requirements or the environment in which you're sharing the pseudocode, you may need to capitalize commands that will remain in the actual code.
    • For example, if you use "if" and "then" commands in your pseudocode, you might want to change them to read "IF" and "THEN" (e.g., "IF <condition> THEN <output result>").
  6. Remember, you're writing about what the project will do , not summarizing the code itself. This is especially important if you're writing pseudocode to serve as a demonstration for an individual who doesn't know coding, or as a project for a beginner programmer .

    You might even want to get rid of any coding commands altogether and just define each line's process in plain language. For example, "if input is odd, output 'Y'" might become "if user enters an odd number, display 'Y'".

  7. While the language you use to modify your pseudocode should be simple, you still need to keep each piece of your pseudocode in the order in which it needs to be executed.
    • This will make writing the actual code easier, since your code will run top-down.
  8. Everything that is happening in the process must be described completely. Pseudocode statements are close to simple English statements. Pseudocode does not typically use variables, but instead describes what the program should do with variables and data like account numbers, names, or transaction amounts. [5]
  9. Even if there is no standard for pseudocode, it will be easier for other programmers to understand your steps if you use structures from existing (sequential) programming languages. Use terms like "if", "then", "while", "else", and "loop" the same way that you would in your preferred programming language. Consider the following structures: [6]
    • if CONDITION then INSTRUCTION — This means that a given instruction will only be conducted if a given condition is true. "Instruction", in this case, means a step that the program will perform, while "condition" means that the data must meet a certain set of criteria before the program takes action. [7]
    • while CONDITION do INSTRUCTION — This means that the instruction should be repeated again and again until the condition is no longer true. [8]
    • do INSTRUCTION while CONDITION — This is very similar to "while CONDITION do INSTRUCTION". In the first case, the condition is checked before the instruction is conducted, but in the second case the instruction will be conducted first; thus, in the second case, INSTRUCTION will be conducted at least one time.
    • function NAME (ARGUMENTS): INSTRUCTION — This means that every time a certain name is used in the code, it is an abbreviation for a certain instruction. "Arguments" are lists of variables that you can use to clarify the instruction.
  10. If you have large sections of pseudocode that define other pieces of pseudocode within the same block, you may want to use brackets or other identifiers to keep everything contained.
    • Brackets—both square [code] and curly {code}—can help contain long segments of pseudocode.
    • When coding, you can add comments by typing "//" on the left side of the comment (e.g., //This is a temporary step. ). You can use this same method when writing pseudocode to leave notes that don't fit into the coding text.
  11. You should be able to answer the following questions by the end of the document:
    • Would this pseudocode be understood by someone who isn't familiar with the process?
    • Is the pseudocode written in such a way that it will be easy to translate it into a computing language?
    • Does the pseudocode describe the complete process without leaving anything out?
    • Is every object name used in the pseudocode clearly understood by the target audience?
    • If you find that a section of pseudocode needs elaboration or it doesn't explicitly outline a step that someone else might forget, go back and add the necessary information.
    12. Advertisement
Part 3
Part 3 of 3:

Creating an Example Pseudocode Document

PDF download Download Article
  1. You can use Notepad (Windows) or TextEdit (Mac) by default if you don't want to install a new program. [9]
  2. While not strictly necessary, writing a one- or two-sentence line at the top of the document will make clear from the beginning the intent of the program: 
    This program will request a greeting from the user. If the greeting matches a specific response, the response will be delivered ; 
 if 
not, a rejection will be delivered.
  3. Your first command—that is, the first thing your program should do upon running—should be the first line: 
    print greeting "Hello stranger!"
  4. Place a space between the last line and the next one by pressing ↵ Enter , then create the next line of code. In this example, the user should prompt the next line of dialogue: 
    print prompt
	press "Enter" 
to continue 
<user presses "Enter" 
>
  5. In this example, the user will be prompted for a greeting: 
    print call-to-action "How are you?"
  6. Again, after pressing ↵ Enter in this example, the user should see a list of possible responses: 
    display possible responses "1. Fine." 
 "2. Great!" 
 "3. Not good."
  7. This is where the program will ask the user to enter a response: 
    print request for 
input "Enter the number that best describes you:"
  8. Since there are multiple responses the user can select, you'll want to add multiple results based on their selected response: 
     if 
 "1" 
print response "Dandy!" 
 if 
 "2" 
print response "Fantastic!" 
 if 
 "3" 
print response "Lighten up, buttercup!"
  9. In the event that the user incorrectly chooses a response, you can have an error message ready: 
     if 
input isn 't recognized 
 print response 
 "You don' 
t follow instructions very well, do 
you? "
  10. Go through your document and add or flesh out any details to ensure that both you and anyone reading the document will understand its meaning. As per this method's example, your final pseudocode document should look something like this: 
    This program will request a greeting from the user. If the greeting matches a specific response, the response will be delivered ; 
 if 
not, a rejection will be delivered.

print greeting "Hello stranger!" 
print prompt
	press "Enter" 
to continue 
<user presses "Enter" 
>

print call-to-action "How are you today?" 
display possible responses "1. Fine." 
 "2. Great!" 
 "3. Not good." 
print request for 
input "Enter the number that best describes you:" 
 if 
 "1" 
print response "Dandy!" 
 if 
 "2" 
print response "Fantastic!" 
 if 
 "3" 
print response "Lighten up, buttercup!" 
 if 
input isn 't recognized 
 print response 
 "You don' 
t follow instructions very well, do 
you? "
  11. Press Ctrl + S (Windows) or ⌘ Command + S (Mac), enter a name, and click Save to do so. [10]
    12. Advertisement

Community Q&A

Search
Add New Question
  • Question
    Is programming always required?
    Community Answer
    Pseudocode isn't real code, but details what a program should do step by step. Knowing how to write code is necessary to writing meaningful and useful pseudocode.
    Thanks! We're glad this was helpful.
    Thank you for your feedback.
    If wikiHow has helped you, please consider a small contribution to support us in helping more readers like you. We’re committed to providing the world with free how-to resources, and even $1 helps us in our mission. Support wikiHow
    Yes No
    Not Helpful 42 Helpful 82
  • Question
    How can I tell the difference between an odd and even number using pseudocode?
    Community Answer
    Divide it by two to see if you get a remainder. If not, then it's even; if yes, then it's odd.
    Thanks! We're glad this was helpful.
    Thank you for your feedback.
    If wikiHow has helped you, please consider a small contribution to support us in helping more readers like you. We’re committed to providing the world with free how-to resources, and even $1 helps us in our mission. Support wikiHow
    Yes No
    Not Helpful 41 Helpful 79
  • Question
    How do I spot errors in pseudocode?
    Scratchless
    Community Answer
    Since pseudocode isn't real code, there can't be any errors. You decide what you want to write as pseudocode and then translate it to any coding language you'd like.
    Thanks! We're glad this was helpful.
    Thank you for your feedback.
    If wikiHow has helped you, please consider a small contribution to support us in helping more readers like you. We’re committed to providing the world with free how-to resources, and even $1 helps us in our mission. Support wikiHow
    Yes No
    Not Helpful 41 Helpful 42
See more answers
Ask a Question
200 characters left
Include your email address to get a message when this question is answered.
Submit
      Advertisement

      Video

      Tips

      • Pseudocode is optimal for complex programs that are hundreds to thousands of lines in length.
        Thanks
        Helpful 4 Not Helpful 0
      Submit a Tip
      All tip submissions are carefully reviewed before being published
      Name
      Please provide your name and last initial
      Submit
      Thanks for submitting a tip for review!
      Advertisement

      Warnings

      • Pseudocode cannot be substituted for actual code when creating a program. Pseudocode can only be used to create a reference for what the code should do.
        Thanks
        Helpful 3 Not Helpful 0
      Advertisement

      You Might Also Like

      How to
      Code
      How to
      Learn HTML
      2 Simple Ways to Format Text Into Code on Discord
      How to
      Change 4-Digit User Codes on Schlage Locks
      How to
      Run a Program from the Command Line on Linux
      How to
      Delay a Batch File: Timeout, Pause, Ping, Choice & Sleep
      How to
      Factory Reset a Schlage Lock & Restore the Default Programming Code
      Converting Binary to Decimal: Positional Notation & Doubling
      3 Ways to Download GitHub Directories and Repositories
      How to
      Make an Exe File
      Convert from Decimal to Hexadecimal: A Quick Guide + Examples
      How to
      View Source Code
      How to
      Make a Program Using Notepad
      How to
      Develop a Mobile App: Planning, Designing, & Publishing
      Advertisement

      References

      1. ↑ https://www.geeksforgeeks.org/what-is-pseudocode-a-complete-tutorial/
      2. ↑ https://www.techopedia.com/definition/3946/pseudocode
      3. ↑ https://www.geeksforgeeks.org/how-to-write-a-pseudo-code/
      4. ↑ https://www.geeksforgeeks.org/how-to-write-a-pseudo-code/
      5. ↑ https://www.youtube.com/watch?v=D0qfR606tVo
      6. ↑ https://www.geeksforgeeks.org/how-to-write-a-pseudo-code/
      7. ↑ https://www.ibm.com/docs/en/zos/2.3.0?topic=instructions-ifthenelse
      8. ↑ https://users.csc.calpoly.edu/~jdalbey/SWE/pdl_std.html
      9. ↑ https://support.microsoft.com/en-us/windows/help-in-notepad-4d68c388-2ff2-0e7f-b706-35fb2ab88a8c
      1. ↑ https://support.apple.com/guide/textedit/save-documents-txte71fa0102/mac

      About This Article

      Article Summary X

      1. Write the purpose of the process.
      2. Write the initial steps that set the stage for functions.
      3. Write only one statement per line.
      4. Capitalize the initial keyword of each main direction.
      5. Write what you mean, not how to program it.
      6. Use standard programming structures.
      7. Use blocks to structure steps.
      8. Add comments if necessary.

      Did this summary help you?
      In other languages
      Thanks to all authors for creating a page that has been read 1,092,936 times.

      Is this article up to date?

      Advertisement