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…

The most effective and standard-compliant approach for a complex, safety-critical project is a hierarchical documentation structure. A Master Test Plan (MTP) should be created to define the overall test strategy, objectives, resources, and schedule for all four test levels, ensuring coordination and a unified approach. It establishes the relationships and dependencies between the levels. Four separate, detailed Level Test Plans (LTPs) should then be produced, one for each test level (component, integration, system, acceptance). Each LTP focuses on the specific scope, items, and procedures for its level, while referencing the MTP for common project-wide information. This structure provides both high-level oversight for auditability and detailed guidance for specific test teams, aligning with ISTQB principles and the rigor required by DO-178B.

A. A single, monolithic test plan covering all details is impractical to manage, maintain, and distribute to different teams responsible for each test level.
B. Excluding the acceptance test plan from the master plan's oversight breaks the coordination and traceability chain, which is critical for overall project verification.
D. Without a master test plan, there is no formal mechanism to coordinate the four test levels, leading to potential gaps, overlaps, and inconsistencies.

1. ISTQB Advanced Level Syllabus, Test Manager, Version 2012, Section 3.2, Test Planning: "The test planning process may also produce a master test plan and separate test plans for test levels (e.g., system or acceptance testing) or for separate test types (e.g., usability or performance testing). ... A master test plan may be produced which covers all test activities for a project or product. In this case, the level-specific test plans need only contain the information specific to that test level and can refer to the master test plan for information that is common to all test levels."

2. Rierson, L. (2013). Developing Safety-Critical Software: A Practical Guide for Aviation Software and DO-178C Compliance. CRC Press. Chapter 11, Software Verification Process, discusses the required planning artifacts for DO-178. The Software Verification Plan (SVP) serves as a master plan outlining the verification strategy across all levels, while the detailed Software Verification Cases and Procedures (SVCP) document the specifics for each verification activity, analogous to level test plans. This hierarchical structure is essential for certification. (See Section 11.2, Software Verification Plan).

3. IEEE Std 829-2008, IEEE Standard for Software and System Test Documentation. This standard, which forms the basis for ISTQB test documentation, defines a hierarchy of test plans. It specifies a Master Test Plan (Section 5) to coordinate all testing on a project and Level Test Plans (Section 6) to detail the planning for specific test levels or phases. This structure directly supports option C.