Across
- 6. User requirements that relate to the quality of the solution, and may be subjectively assessed, i.e. not everyone will assess them equally
- 7. Used to test that the system can cope with very large or very small data values
- 8. The process of finding and fixing errors or bugs in software or hardware
- 11. A systematic approach to building something, whether it's a product, a software application, or even an individual's skills or growth
- 13. Model represents a sequential approach to application development. A series of stages need to be completed in a fixed order.
- 15. A method of testing which examines the underlying structure of the application or code which has been developed
- 17. A model of a system being developed; may not be fully functional
- 18. Another word for an error or fault, which leads to errors in the execution of a program or application
Down
- 1. Used to test that the system can process invalid data and does not crash when invalid data is entered
- 2. Where lines of code are designed to run one after another from the beginning to the end
- 3. A sequence of stages or changes that something goes through, from its beginning to its end
- 4. Used to test that the system operates as expected with normal data
- 5. User requirements which can be easily measured, for example in terms of time
- 9. The use of loops and conditions to repeat sections of code
- 10. The process of evaluating how something works
- 12. Used to test that the system can cope when no data is entered
- 14. Software programs designed to perform specific tasks on a computer or device
- 16. Where the tester is unaware of the internal structure of the application they are testing