What factors need to be taken into consideration when assessing the progress of testing and validation activities? There are many things to take into account. For the following 3 example projects below: 1. Recommend 3 steps to improve the next test iteration of that product and its efficiency. Base your evidence on interpretations of the test plan (staffing, risk, entry and exit criteria) and the S-Curves provided.

ect is system verification test (SVT) project is proposed to complete within 10 wecks. The product enhancements are simplistic changes to keywords on application commands. This product has just been through a unit test and function verification test (FVT) performed by the development organization. The function verification testing has found a small number of defects related to command syntax. Please refer to Figure 1 below for the S-curve associated with this project. Consider the following entry and exit criteria, risks and staffing/skills model statements. Entry Criteria 100% of the scenarios for the function verification test effort have been attempted 00% of the scenarios for the function verification test effort have been deemed complete and successful . No defects are open at system verification test entry . System verification test scenarios have been defined and reviewed with development and FVT Exit Criteria 100% of the scenarios for the function verification test effort have been attempted 95% of the scenarios for the function verification test effort have been deemed complete and successful . No high severity defects are open at the completion of the FVT Project Risks . Large number of defects are uncovered by the function verification test team o Mitigation action: weekly review of fiunction verification defects Function verification test does not compiete on schedule. Mitigation action: early education involvement by experienced system verification testers .Two system verification testers with minimum of 10 years of SVT experience . Each tester shouid have 5 years ofproduct experience Ils Approach for the Project .Two system verification testers with 8 and I2 years SVT experience respectively . Two system verification testers have & years ofproduct experience Test Project A v Projected Complete Projected Attempts Actual Complete Actual Attempts 600 550 500 450 400 350 300 250 200 150 100 50 Weoki Week2 ek3 Weok4 Week5 WeekG Week7 Week Week9 Week10 Figure 1 - Test Project A S-curve Test Proiect B This function verification test (FVT) project is scheduled to take place from 402010 and complete within 1Q2011. The system verification test team is expecting to begin its testing of this capability on 2/01/2011. The functionality that is being devcloped in the product is brand new and will be a new concept to customers and clients. This product has just been through a unit test performed by the developers of the product. Plcase refer to Figure 2 below for the S-curve associated with this project Consider the following entry and exit criteria, risks and staffing/skills model statements. Entry Criteria .Test environment fvirtualized) is available for ail function verification testers . Design documentation completed and available to function verification test . All code has been shipped into an officially packaged deliverable Exit Criteria 100% of the scenarios for the function verification test effort have been attempted 95% of the scenarios for the function verification test effort have been deemed complete and successful . No high severity defects are open at the completion of the FVT Project Risks None identified ls Requirements . One fiunction verification tester with 2 years of FVT experience . One function verification tester with 10 years of FVT experience . Proposed early involvement of FVTers during design phase of fiunctionality Sraffing/Skills Approach for the Project .Two fiunction verification testers with 2 years of FVT experience Testers are not available until Nov 15, 2010 Test Project C This system verification test (SVT) project is scheduled to complete within 10 wecks. The particular capability that has been added to the product is similar to support that has already been introduced in prior releases. Therefore, previous lessons leamed have been taken into account during the planning for this test. This product has just been through a unit test and function verification test performed by the development organization. Please refer to Figure 3 below for the S-curve associated with this project. Consider the following entry and exit criteria, risks and staffing/skills model statements. Entry Criteria 100% of the scenarios for the function verification test effort have been attempted 95% of the scenarios for the function verification test effort have been deemed complete and successful * * . No high severity defects are open at system verification test entry . Lower severity defects, that are open, have a plan in place to address them . A pre-defined SVT acceptance test is successful two weeks prior to actuai SVT schedule Exit Criteria 100% of the scenarios for the system verification test effort have been attempted * 100% of the scenarios for the system verification test effort have been deemed complete and . No high severity defects are open at the completion of the SVT . New developer ( I year experience) assigned to project and being coached by component- * Project Risks experienced mentor. Mitigation action: Experienced fiunction verification tester also on team. . cc++ programming skills required for test workload development . 2-3 years of technical experience in the product/component area under test Hs Approach for the Project . Two experienced system testers will be availabie fiull-time for the Test Project C validation plan One system tester has 5 years of c/c++ programming experience and