Syllabus requires you to:
- Describe methods of ensuring that software is reliable:
- Understand the reasons why fully-tested software may fail to operate
successfully when implemented as part of an information technology
- Understand the need for maintenance release(s).
- Software is released to a restricted number of testers,
- often within the organisation.
- The software may not be finished and may still contain faults.
- Released after the alpha testing and any changes have been made.
- Software is released to privileged customers in exchange for their constructive comments.
- Beta versions are usually near-complete packages.
- Testers are often informed users
- e.g. computer magazine reviewers,
- authors of relevant books,
- developers of associated software or hardware.
- The advantage is that the comments can be used to:
- improve the software and
- advertise the final product.
- Made when the system development is complete.
- A series of tests are made to show the customer that the system works correctly.
- Usually carried out just before the system is handed over to the customer.
- Acceptance testing will test all parts of the system and compare it with the specification agreed with the customer.
- It is designed to ensure that the software delivers what the customer ordered.
- The developer should correct any fault found during acceptance testing before the system is delivered.
- A mathematical technique.
- Used to attempt to prove that the software works without having to test every aspect of the program.
British Computer Society: The BCS Glossary of ICT and Computing Terms.
11th ed. Harlow: Pearson Education, 2005.
Past Exam Questions
- Do the exercise and questions at the end of Chapter 62 of the textbook.