- This document should describe how to use the software.
- Ideally there should also be tutorial files which can take the user through examples of a piece of work, and allow them to become familiar with the commands, and the various sections of the software.
- This document should provide information on
- how to install the software
- hardware requirements
- software requirements
Evaluation - Does the solution meet the user requirements?
- Judge this against a set of criteria
- screen layout
- help required
- user prompts
- fitness for purpose
- maintainability
- robustness
- reliability
- portability
Some Definitions (1) - Correctness
- A program is correct if it matches the users requirements
- Maintainability
- A program will be easily maintained if it has been written in a way which will make it easy to change. This will include
- internal commentary
- meaningful variable and procedure names
- parameter passing
Some Definitions (2) - Reliability
- Readability
- A program is readable if it is easily understandable by people other than the original programmer, ie good internal documentation, use of white space, etc.
Some Definitions (3) - Portability
- A program is said to be portable if it can be transferred from one system to another with minimal adaptation
- Efficiency
- A program is efficient if it uses the most appropriate structures for the job. It should run as fast as possible and not use up more system resources than are necessary.
Some Definitions (4) - Robustness
- A program is said to be robust if it does not crash when invalid data is input or unexpected results are generated.
- Fitness for Purpose
- Does the program meet the requirements?
Maintenance - Activities identified as part of maintenance:
- corrective (17%)
- adaptive (18%)
- Perfective (65%)
Maintenance Costs - Maintenance is very costly. It is vital that errors are detected at as early a stage as possible.
Do'stlaringiz bilan baham: |
