Evaluation

The evaluation stage of the software development process requires the client and developer to review the software.

Broadly speaking, they evaluate against the following questions:

1.Does this software meet the user requirements?

2.Is it fit for purpose?

Evaluation

To answer these questions, the original aims of the software must be evaluated against the following criteria.

1.Correct2.Robust3.Reliable4.Efficient5.Readable6.Maintainable7.Portable

Evaluation - criteria

CorrectDoes the program meet the software specification?

RobustThe program responds to unexpected input and does not crash

Which is robust…?

ReliableThe program does not have any logic errors and produces output which can be relied upon to be correct

This program is correct and robust. But is it reliable?

EfficientThe program makes efficient use of resources

eg processor, memory, external devices

Size and speed should be proportionate to the problem being solved

ReadableA program should be readable to another programmer. This means using:meaningful variable namesmeaningful subprogram nameswhitespaceinternal commentary

MaintainableIt should be possible to easily carry out future changes to the program:Readable codeFull documentationVersion controlDesign process with maintenance in mind

PortableThe program can be adapted to run on a different Operating System

The software should be evaluated by client and developer at all stages in the process, not just when the software is complete.

e.g. How well the client’s problem has been understood

should be evaluated at the analysis stageThe HCI should be evaluated at the design stage

Evaluation - when