In pseudocode you use similar terms to flowcharts however you have to lay it out in a different way with all of the outputs and inputs being shown. All instructions must be written in capital letters. The instructions include:

OUTPUT = The device outputs a piece of data (question e.t.c)

INPUT = The user puts something into the program

STORE = Allows the device to remember a variable

IF = A question checking a condition, like a decision in flowcharts

THEN = Showing what to do if the answer to IF is true (yes)

ELSE = Showing what to do if the answer to IF is false (no)

REPEAT UNTIL = Repeating the algorithm until a condition is met

The most common way to start an algorithm is with a question written like this:

OUTPUT
INPUT
STORE

This allows the question to be asked, an answer to be revived, and the answer to be stored for later use as a variable. It would look like this in a practical situation.

OUTPUT: "What is your name?"
INPUT: user inputs name
STORE: user answer in name variable

After this it would be common to add an IF, THEN, ELSE sequence afterwards to determine what happens next. For example:

IF name (this is the variable) = "Oliver" THEN

OUTPUT: "That's mine too!"
ELSE
OUTPUT: "Nice name, mine's Oliver"

With pseudocode you would never write in the start and stop like you do with flowcharts.

Useful BBC Bitsize: http://www.bbc.co.uk/education/guides/z3bq7ty/revision/2