A chart showing the trend in the lag time from defect reporting to resolution during system testing is also available. The chart shows that the daily closure period is consistently and significantly above the rolling closure period for a long period of the system testing phase.
Almost all defects found during system testing have been related to the system as a whole, not related to single units or integrations issues. Almost all quality risks have been addressed during the unit and integration testing phase and no residual quality risks were present in the integrated system. This has been confirmed by exploratory testing sessions performed during system testing, targeted at finding defects in these quality risk areas.
Based on the given information only, which one of the following areas would you expect to be considered more in the retrospective meeting in order to be improved?
Number of correct responses: 1
K33 credits

• A. The requirements review
• B. The system design and architecture design reviews
• C. The quality risk analysis process
• D. The defect management process

You have been carefully monitoring the progress of testing for your project. You have been using the established traceability to verify that the requirements and test conditions are being adequately addressed. The test team is proceeding well in their test case execution and you can see that you are achieving about 80% coverage of the test conditions per the traceability mapping in your test management system. You have seen a number of defects being logged against test conditions that are failing, but you do not see a mapping of the test cases to those conditions.
What is likely to be occurring in the testing area that is causing the traceability to break down? [2]

• A. The testers are not updating the test execution information in the test management system.
• B. The test cases are mapped to the test strategy and are bypassing the test conditions.
• C. The testers are executing the wrong tests.
• D. The testers are running exploratory tests that are not mapped to the test conditions.

Test Management
You are the Test Manager of a new project aimed at developing a software system that must be certified at level B of the DO-178B standard. The project will follow a V-Model software development life cycle and it will have four formal levels of testing: component, integration, system and acceptance testing.
You must produce the test plan documentation for this project by providing an adequate coordination across the four levels of testing in order to assure auditability.
Which of the following answers would you expect to best describe how to organize the test plan?
Number of correct responses: 1
K32 credits

• A. Produce four separate detailed level test plans, one for each level, without a master test plan
• B. Produce a master test plan describing the relationship between the four levels, and four separate detailed level test plans, one for each level
• C. Produce a master test plan that covers three levels (component, integration, system test) and a separate acceptance test plan
• D. Produce a single master test plan that covers in detail all four levels, describing the particular activities for all test levels

Your company is installing a third-party enterprise-wide business software package. This is the first time the company has done anything like this.
Which technique would be the best one to use to estimate the testing effort? [3]

• A. Estimated developer effort and lines of code
• B. Industry averages
• C. Review of the installation guide
• D. Past experience with in-house projects