Appendix A Acronyms
Appendix B Glossary
Appendix C How to Write a Good Requirement— Checklist
Appendix D Requirements Verification Matrix
Appendix E Creating the Validation Plan with a Validation Requirements Matrix
Appendix F Functional, Timing, and State Analysis
Appendix G Technology Assessment/Insertion
Appendix H Integration Plan Outline
Appendix I Verification and Validation Plan Outline
Appendix J SEMP Content Outline
Appendix K Technical Plans
Appendix L Interface Requirements Document Outline
Appendix M CM Plan Outline
Appendix N Guidance on Technical Peer Reviews/Inspections
Appendix O Reserved
Appendix P SOW Review Checklist
Appendix Q Reserved
Appendix R HSI Plan Content Outline
Appendix S Concept of Operations Annotated Outline
Appendix T Systems Engineering in Phase E
H.1 Purpose
The integration plan defines the integration and verification strategies for a project interface with the system design and decomposition into the lower-level elements. The integration plan is structured to bring the elements together to assemble each subsystem and to bring all of the subsystems together to assemble the system/product. The primary purposes of the integration plan are: (1) to describe this coordinated integration effort that supports the implementation strategy, (2) to describe for the participants what needs to be done in each integration step, and (3) to identify the required resources and when and where they will be needed.
H.2 Questions/Checklist
- Does the integration plan include and cover integration of all of the components and subsystems of the project, either developed or purchased?
- Does the integration plan account for all external systems to be integrated with the system (for example, communications networks, field equipment, other complete systems owned by the government or owned by other government agencies)?
- Does the integration plan fully support the implementation strategy, for example, when and where the subsystems and system are to be used?
- Does the integration plan mesh with the verification plan?
- For each integration step, does the integration plan define what components and subsystems are to be integrated?
- For each integration step, does the integration plan identify all the needed participants and define what their roles and responsibilities are?
- Does the integration plan establish the sequence and schedule for every integration step?
- Does the integration plan spell out how integration problems are to be documented and resolved?
H.3 Integration Plan Contents
Title Page
The title page should follow the NASA procedures or style guide. At a minimum, it should contain the following information:
- INTEGRATION PLAN FOR THE [insert name of project] AND [insert name of organization]
- Contract number
- Date that the document was formally approved
- The organization responsible for preparing the document
- Internal document control number, if available
- Revision version and date issued
1.0 Purpose of Document
This section gives a brief statement of the purpose of this document. It is the plan for integrating the components and subsystems of the project prior to verification.
2.0 Scope of Project
This section gives a brief description of the planned project and the purpose of the system to be built. Special emphasis is placed on the project’s deployment complexities and challenges.
3.0 Integration Strategy
This section tells the reader what the high-level plan for integration is and, most importantly, why the integration plan is structured the way it is. The integration plan is subject to several, sometimes conflicting, constraints. Also, it is one part of the larger process of build, integrate, verify, and deploy, all of which should be synchronized to support the same project strategy. So, for even a moderately complex project, the integration strategy, which is based on a clear and concise statement of the project’s goals and objectives, is described here at a high but all-inclusive level. It may also be necessary to describe the analysis of alternative strategies to make it clear why this particular strategy was selected.
The same strategy is the basis for the build plan, the verification plan, and the deployment plan. This section covers and describes each step in the integration process. It describes what components are integrated at each step and gives a general idea of what threads of the operational capabilities (requirements) are covered. It ties the plan to the previously identified goals and objectives so the stakeholders can understand the rationale for each integration step. This summary-level description also defines the schedule for all the integration efforts.
4.0 Phase 1 Integration
This and the following sections define and explain each step in the integration process. The intent here is to identify all the needed participants and to describe to them what they have to do. In general, the description of each integration step should identify the following:
- The location of the activities.
- The project-developed equipment and software products to be integrated. Initially this is just a high-level list, but eventually the list should be exact and complete, showing part numbers and quantity.
- Any support equipment (special software, test hardware, software stubs, and drivers to simulate yet-to-be-integrated software components, external systems) needed for this integration step. The same support equipment is most likely needed for the subsequent verification step.
- All integration activities that need to be performed after installation, including integration with onsite systems and external systems at other sites.
- A description of the verification activities, as defined in the applicable verification plan, that occur after this integration step.
- The responsible parties for each activity in the integration step.
- The schedule for each activity.
5.0 Multiple Phase Integration Steps (1 or N steps)
This and any needed additional sections follow the format for Section 3.0. Each covers each step in a multiple-step integration effort.