A. Test execution activities run until exit criteria have been met.

B. Reporting of all test results occurs when testing is complete for the whole project.

C. System test planning starts when project planning activities commence.

D. Test analysis activities run concurrently with specification of requirements and design.

A. Mandatory reviews of all important design work products

B. Formal inspections of the code modules affected by the last release

C. Increased static analysis during the implementation phase

D. Increased white-box coverage during system testing

A. FMEA is an analytical process upstream, that attempts to identify the hazards for each risk.

B. FMEA is where quality risks, their potential causes and their likely effects are identified and then severity, priority and detection ratings are assigned.

C. FMEA is a quality risk management technique concerned with quality risks that arise from an incorrect understanding of the customer requirements.

D. FMEA is a risk mitigation process that involves determining every possible type of failure, and designing tests to cover each one.

A. Comparing actual progress against the test plan and implementing the necessary corrective actions

B. Identifying and analyzing new product risks that should be mitigated through test design and execution

C. Establishing a testing schedule and monitoring framework to enable tracking of the status of testing

D. Comparing actual results against the expected results as the test cases are executed

A. Time - Cost - Quality

B. Time - Cost - Effort

C. Quality - Cost - Effort

D. Time - Effort - Quality

A. Decide whether to take a model based or an analytical based process improvement approach

B. Trial a low-priority improvement in order to assess the difficulty of changing the organisation's processes

C. Re-prioritise the possible improvements according to their expected return on Investment

D. Check to see which benefits have, or have not, been achieved from the improvement made

E. Trial one or more of the highest-priority improvements in a pilot project

A. The Test Manager uses this information to control the test execution effort.

B. The development manager uses this information to determine how many developer resources to allocate to defect repair.

C. The project manager uses this information to determine if the project is on schedule.

D. The tester uses this information to determine which test should be run next.

A. During the creation of the test plan

B. At major project milestones

C. At the beginning of the test execution phase

D. Prior to test case creation

A. a and d.

B. c and e.

C. b and c.

D. a and c.

A. Defects that are projected but have not been found yet

B. Defects that have resulted from regressions

C. Defects that will be introduced to production

D. Defects fixed but not yet closed

A. Gathering metrics to determine the success of the review process

B. Selecting the review items and the appropriate review type

C. Calculating the ROI for the review process

D. Setting a minimum number of defects to be identified in each review

A. Defect resolution rate

B. Lines of code

C. Exit criteria

D. Post-implementation defect discovery rate

A. A cost-benefit analysis that includes the costs of evaluating and selecting the correct tool

B. A cost-benefit analysis that includes the costs of recurring licensing and support charges

C. Mitigation of the risk that the tool will not integrate well with the existing tool landscape

D. Estimation of the time that will be needed for each performance test run with the tool

E. Mitigation of the risk that the vendor's support may become less satisfactory over time