TESTING METHODOLOGY

123456789101112131415161718
Across
  1. 4. The degree to which a component or system can function correctly in the presence of invalid inputs or stressful environmental conditions.(10 letters)
  2. 5. A process or meeting during which a work product or set of work products, is presented to project personnel, managers, users, customers, or other interested parties for comment or approval.(6 letters)
  3. 7. ____ is a testing methodology in which two or more program mutations are executed using the same test cases to evaluate the ability of the test cases to detect differences in the mutations.(8 letters)
  4. 8. ____ is a skeletal or special-purpose implementation of a software component which is used to develop or test a component that calls or is otherwise dependent on it.(4 letters)
  5. 12. The process of confirming that a component or system complies with its specified requirements.(13 letters)
  6. 15. An independent examination of a work product or set of work products to assess compliance with specifications, standards, contractual agreements, or other criteria.(5 letters)
  7. 17. The capability of the software product to provide appropriate performance, relative to the amount of resources used under stated conditions.(10 letters)
  8. 18. The capability of the software product to avoid unexpected effects from modifications in the software.(9 letters)
Down
  1. 1. The degree to which a process, system or component meets specified requirements or needs and expectations of customer.(7 letters)
  2. 2. A framework to describe the software development life cycle activities from requirements specification to maintenance.(6 letters)
  3. 3. The ease with which the software product can be transferred from one h/w or s/w environment to another.(11 letters)
  4. 6. Code _____ is a manual testing technique where the programmer presents the source code to a group who analyze the code to meet with coding standards and also with a checklist of historically common programming errors.(10 letters)
  5. 9. A specification or software product that has been formally reviewed or agreed upon, that thereafter serves as the basis for further development, and that can be changed only through a formal change control process.(8 letters)
  6. 10. A factor, usually expressed as impact and likelihood, that could result in future negative consequences.(4 letters)
  7. 11. A type of review that relies on visual examination of documents to detect defects, e.g. violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a documented procedure.(10 letters)
  8. 13. The ability of the software product to perform its required functions under stated conditions for a specified period of time, or for a specified number of operations.(11 letters)
  9. 14. Data that exists (for example, in a database) before a test is executed, and that affects or is affected by the component or system under test.(8 letters)
  10. 16. ____ is a testing of a module for typographic, syntactic, and logical errors, for correct implementation of its design, and for satisfaction of its requirements.(4 letters)