Sign In
App icon


Available Now!
Get the App
Click Here to Continue Browser Session   ❯


F35 construction


The Integration process provides a framework to systematically assemble lower-level system elements into successively higher-level system elements, iterative with verification until the system itself emerges. Integration is essential to increasing system maturity, reducing risk and preparing the system for transition to the warfighter.

Role of the PM and SE

The Program Manager (PM), with support from the Systems Engineer, is responsible for planning, managing and executing the Integration process. Experience has shown that programs that develop an integration plan are more successful. This plan defines the stages of integration during which system elements are successively integrated to form higher-level elements and eventually the finished product. Alternative integration paths should be considered. The integration plan should include a description of the required Systems Integration Laboratories or other facilities, personnel, test stands, harnesses, testing software and integration schedule.

Interface Management

The Interface Management process is critical to the success of the Integration process. Interface control specifications or interface control documents should be confirmed early on and placed under strict configuration control. All of the program’s external interfaces and dependencies should be documented in the program’s Systems Engineering Plan (SEP). The SEP Outline requires that all programs with external dependencies and/or interfaces establish Memoranda of Agreement (MOA) in order to formally establish commitments and management procedures. A current table showing the status of all MOAs is mandated as part of the program SEP, which is updated in each phase.

Integration activities support the Interface Management process by verifying that accurate and effective interface specifications are documented. In parallel, the verification methods for each integration level are developed and included in the allocated baseline. The successive integration phases follow the sequence defined in the program’s integration plan and lead to the final product being ready for verification and validation.


Key Terms


Source: DAU Glossary

Statutes, Regulations, Guidance

DASD(SE) Initiative

SoS Systems Engineering

DAU Training Courses

Products and Tasks

Product Tasks
AWQI 6-1-1: Verified internal and external system interfaces
  1. Obtain DoD architecture framework (DoDAF) products and technical baselines (functional, allocated and / or initial product) as they are approved.
  2. Identify all program and product internal and external interfaces.
  3. Identify memoranda of agreement / understanding (MOA/MOU) for all programs with external dependencies and / or interfaces and record them in the program’s systems engineering plan (SEP).
  4. Document the technical definition and performance stability of all external interfaces.
  5. Generate acquisition documents to transmit changes in external interfaces to the developer.
  6. Approve the developer’s integration strategy and sequence addressing external and internal interface verification in an iterative progression from components to subsystems to the system.
  7. Approve the developer’s mechanism for “problem control / resolution” process.
  8. Document integration testing and integration “problem control/resolutions” in accordance with the integrated master schedule (IMS).
  9. Approve interface documents which comply with the configuration management plan/system using applicable guidance.
  10. Compare the physical asset against the technical documentation to verify accounting and accuracy of all interfaces.
  11. Document verification of internal and external system interfaces and submit to decision maker.

Source: AWQI eWorkbook