Across
- 2. A specific instantiation of a test process.
- 4. A test level that focuses on interactions between systems.
- 7. Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
- 8. A type of acceptance testing performed to verify whether a system satisfies its contractual requirements.
- 9. Testing performed to evaluate that a component or system complies with non-functional requirements.
- 18. Testing in which the test items are interfaces and interactions between integrated components.
- 22. A type of change-related testing performed after fixing a defect to confirm that a failure caused by that defect does not reoccur.
- 24. A type of change-related testing to detect whether defects have been introduced or uncovered in unchanged areas of the software.
- 25. A group of test activities based on specific test objectives aimed at specific characteristics of a component or system.
- 26. Testing based on an analysis of the internal structure of the component or system.
- 29. The identification of all work products affected by a change, including an estimate of the resources needed to accomplish the change.
- 30. The reason or purpose of testing.
- 31. A test level that focuses on verifying that a system as a whole meets specified requirements.
- 32. A type of acceptance testing performed in the developer's test environment by roles outside the development organization.
Down
- 1. Testing to evaluate the degree to which the system can be used by specified users with effectiveness, efficiency and satisfaction in a specified context of use.
- 3. A type of acceptance testing performed to verify whether a system conforms to relevant laws, policies and regulations.
- 5. A type of acceptance testing performed to determine if operations and/or systems administration staff can accept a system.
- 6. A type of acceptance testing performed to determine if intended users accept the system.
- 10. An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test.
- 11. A test level that focuses on determining whether to accept the system.
- 12. Testing the changes to an operational system or the impact of a changed environment to an operational system.
- 13. A type of software development lifecycle model in which a complete system is developed in a linear way of several discrete and successive phases with no overlap between them.
- 14. A test level that focuses on interactions between components or systems.
- 15. Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled.
- 16. A type of testing initiated by modification to a component or system.
- 17. A sequential software development lifecycle model describing a one-for-one relationship between major phases of software development from business requirements specification to delivery, and corresponding test levels from acceptance testing to component testing.
- 19. Testing performed to evaluate if a component or system satisfies functional requirements.
- 20. A test level that focuses on individual hardware or software components.
- 21. A set of preconditions, inputs, actions (where applicable), expected results and postconditions, developed based on test conditions.
- 23. The work product to be tested.
- 27. A type of acceptance testing performed at an external site to the developer's test environment by roles outside the development organization.
- 28. The body of knowledge used as the basis for test analysis and design.