Evaluating Solutions

Once written, an algorithm should be checked to make sure it:

• is fully decomposed

• is complete

• is efficient

• meets design criteria of a problem

Failure to evaluate can make it difficult to write a program

• true

• false

What is evaluation?

• Evaluation is the process that allows us to find a solution to a problem

• Evaluation is the process that allows us to break down a problem

• Evaluation is the process that allows us to make sure our solution is correct

Why is it important to evaluate?

• To ensure that a solution is as good as it can be

• To prove that the solution has been tested

• That it is inefficient

How may a solution be faulty?

• It may be incomplete

• It may not be decomposed

• It may be incomplete and/or not decomposed

What is said when a problem isn't understood?

• That it isn't fully decomposed

• That it is incomplete

• That it is inefficient

What is said when a solution doesn't fully solve the problem?

• It isn't fully decomposed

• It is incomplete

• It is inefficient

Which of the following is an example of an efficient solution?

• Heating some soup, waiting until it is boiled then buttering some bread

• Heating some soup and buttering bread whilst the soup is heating

• Buttering bread then heating soup afterwards

Which of the following is also an example of an efficient solution?

• Carrying a pile of books and placing them on a shelf all in one go

• Carrying the books one at a time and placing them on a shelf

• Moving a pile of books three at a time and placing them on a shelf

Working through an algorithm with pen and paper is known as what?

• Testing

• A dry run

• Evaluation