The systems life cycle: evaluation Cambridge IGCSE Information & Communication Technology revision

Not started

Learn it

In plain words

Some time after the new system goes live, someone has to ask the awkward question: is it any good? Evaluation measures the finished system against what was asked for at the start.

6 things to know

  1. A solution is evaluated for its efficiency (does it do the job quickly, with the least time and resources?), its ease of use, and its appropriateness (does it suit the task and the users?).
  2. The solution is compared with the original task requirements, to see whether each one has been met.
  3. Any limitations of the system are identified, along with the improvements needed.
  4. The users' responses to the system are collected, through interviews, questionnaires and observation.
  5. The results of testing are looked at again.
  6. Evaluation may lead to changes, and so back to an earlier stage of the life cycle.

Worked example

A shop has used a new stock control system for three months. How should it be evaluated?

  1. Compare what the system does with the list of requirements written during analysis.
  2. Ask the staff who use it, by questionnaire or interview, whether it is easy to use and whether it saves them time.
  3. List any limitations found, and the improvements needed to remove them.

Tips and tricks

  • Three words to remember: efficiency, ease of use and appropriateness.
  • Evaluation always looks back to the original requirements. Mention them in any answer.
5 questions, about 2 minutes.

It lands in your notebook with its questions as flashcards.

The systems life cycle: evaluation: 5 questions and answers

These are the quiz’s questions. Do the quiz first, then come back here for the ones that got you.

  1. What is the new system compared with during evaluation?
    • a competitor's system
    • the original task requirements (the answer)
    • the cost of the hardware
    • the programmer's wages

    Each requirement is checked.

  2. Which is considered when evaluating a solution?
    • the colour of the computers
    • the ease of use of the solution (the answer)
    • the age of the analyst
    • the name of the software company

    Along with efficiency and appropriateness.

  3. What may evaluation lead to?
    • deleting all the data
    • improvements to the system (the answer)
    • removal of the documentation
    • the end of testing for ever

    Limitations are identified and put right.

  4. Who provides feedback on how easy the system is to use?
    • the hardware supplier
    • the users (the answer)
    • the bank
    • the competitors

    They work with it every day.

  5. When does evaluation take place?
    • before analysis
    • during design
    • after the system has been implemented (the answer)
    • before testing

    The system has to be in use first.

Still stuck on this one?Ask in the Papermunch Discord, or help someone else who is. Discord is for ages 13 and up.Join the server

Things you can type

Or go straight to

Or browse a shelf