Overview
This activity defines the planned testing schedule for each test site. The schedule is coordinated with the software development schedule and overall project schedule.
Roles and Responsibilities
The software test manager completes the Software Test Plan (STP) (see Appendix E) section on determining the test schedule.
The software engineering process group (SEPG) members may be consulted to provide information on historical testing durations.
Controls
See parent activity 1.1.3 Plan Software Testing.
Inputs
The test approach as defined in activity 1.1.3.2 Define Testing Approach.
The software test environment identified in activity 1.1.3.1 Identify Software Test Environment.
Procedures
The testing schedule has the same essential elements as any other schedule, that is, milestones with dates, when all resources (e.g., people, machines, tools, facilities) are needed, and when testing activities are planned to be performed. However, testing schedules are very difficult to estimate because they depend on others’ work (e.g., if the circuit boards for the flight box have not yet been manufactured then the flight software cannot be tested). Schedules are still very useful and essential tools in testing because they provide an element of predictability, maximize productivity, and are imperative for progress tracking. Cem Kaner, et al, give additional guidance on preparing testing schedules in [Kaner, 1993, pp. 352 - 358]. The software test manager iteratively follows the following steps to prepare a test schedule:
1) Reads the Software Development Plan (SDP) (see Appendix E), concentrating on the Schedules and Activity Network section, to understand how the software development effort is expected to proceed. The software test manager focuses on software and project milestones. Additional important information is provided by previously completed STP sections.
2) Creates a top-level schedule based on the software project delivery schedule. This schedule should show all start and finish dates for testing each software delivery package, as well as all major software and project milestones. In addition, resource-needed dates for every element in the test environment are included. The software test manager reviews this top-level schedule with the project software manager. If it is determined that the testing schedule is unsatisfactory for some reason, the managers work together to determine alternatives.
3) Adds more detail to or "fleshes out" the schedule and each of the testing activities. SEPG members may be consulted, as well as some cost models to determine the amount of time to perform lower-level activities. The dates and durations for the upper-level activities may need to be updated based on these estimates. Activities which can be done in parallel should be identified, thus, reducing the amount of time needed to test. The critical path for the testing effort is then generated.
4) The software testing schedule should be placed in the Test Schedules section of the STP.
Outputs
The Software Test Schedule which has been documented in the Test Schedules section of the STP.