1. Maintenance testing can be best described as:
2. The capability of an organization with respect to the effectiveness and efficiency of its processes and work practice can be best named as:
3. Inspection leader can be best described as:
4. A type of performance testing conducted to evaluate the behavior of a component or system under varying loads, usually between anticipated conditions of low, typical, and peak usage can be best named as:
5. The number or category assigned to an attribute of an entity by making a measurement can be best named as:
6. Maintainability can be best described as:
7. The degree to which a component or system meets needs for reliability under normal operation can be best named as:
8. A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing the program and/or other concurrent processes to fail due to lack of memory can be best named as:
9. Master test plan can be best described as:
10. The process of assigning a number or category to an entity to describe an attribute of that entity can be best named as:
11. A software tool or hardware device that runs concurrently with the component or system under test and supervises, records and/or analyzes the behavior of the component or system can be best named as:
12. Moderator (inspection leader) can be best described as:
13. Maintenance can be best described as:
14. A point in time in a project at which defined (intermediate) deliverables and results should be ready can be best named as:
15. Low-level test case (concrete test case) can be best described as:
16. Non-functional requirement can be best described as:
17. A measurement scale and the method used for measurement can be best named as:
18. Non-functional testing can be best described as:
19. Model-based testing (MBT) can be best described as:
20. Lifecycle model can be best described as: