Implementation and Integration

Stages

5. Detailed Design^D
6. Implementation and Integration (this stage)^A
7. Verification and Structural Coverage^D

Certification, program and supply milestones

Hardware and software assurance milestones

• Conceptual design baselined (CD)
• Detailed design review (DR) (technical readiness review TR2)
• Build baselined (BB)
• Verification complete (VC)

Disciplines

• Program and certification management^A
  • Detailed Design: maturity 0.5, Draft. Plans accepted; liaison follows the design through the design review, whose findings are recorded and closed.
  • Implementation and Integration: maturity 0.5, Draft. Plans accepted; liaison follows the design through the design review, whose findings are recorded and closed.
  • Verification and Structural Coverage: maturity 0.8, Feature complete. Verification review held and the compliance evidence gathered with the qualification results; accomplishment summaries drafted.
• Systems engineering and safety assessment^AO
  • Detailed Design: maturity 0.8, Feature complete. Preliminary assessment complete on the detailed design and common cause analysis under way; the system safety assessment drafted, waiting on verification results.
  • Implementation and Integration: maturity 0.8, Feature complete. Preliminary assessment complete on the detailed design and common cause analysis under way; the system safety assessment drafted, waiting on verification results.
  • Verification and Structural Coverage: maturity 1.0, Complete. System safety assessment closed on the verification results for this baseline, with the common cause analysis complete.
• Airborne electronic hardware design^A
  • Detailed Design: maturity 0.8, Feature complete. Detailed design reviewed against the design standards and traced, then built into programming files and frozen for verification; fixes only through problem reports.^D
  • Implementation and Integration: maturity 0.8, Feature complete. Detailed design reviewed against the design standards and traced, then built into programming files and frozen for verification; fixes only through problem reports.; Hardware design frozen for verification (milestone for one item)
  • Verification and Structural Coverage: maturity 1.0, Complete. Hardware verified on the frozen design, every requirement covered, and confirmed in its environment by qualification.
• Airborne software development^A
  • Detailed Design: maturity 0.8, Feature complete. Low-level requirements and source code reviewed against the standards and traced, and the executable object code built on the target and frozen for verification.^A
  • Implementation and Integration: maturity 0.8, Feature complete. Low-level requirements and source code reviewed against the standards and traced, and the executable object code built on the target and frozen for verification.
  • Verification and Structural Coverage: maturity 1.0, Complete. Executable object code verified on the target, with structural coverage closed on the frozen build.
• Hardware validation and verification^D
  • Detailed Design: maturity 0.8, Feature complete. Procedures reviewed against the detailed design and test benches running on each design drop; the formal runs wait for the build baseline.
  • Implementation and Integration: maturity 0.8, Feature complete. Procedures reviewed against the detailed design and test benches running on each design drop; the formal runs wait for the build baseline.
  • Verification and Structural Coverage: maturity 1.0, Complete. Verification results complete on the build baseline: every requirement verified, elemental analysis done where the level needs it, and the trace closed.^A
• Software verification^D
  • Detailed Design: maturity 0.8, Feature complete. Reviews of the low-level requirements and code done and the cases and procedures complete; tests dry-run on each build while the formal runs wait for the baseline.
  • Implementation and Integration: maturity 0.8, Feature complete. Reviews of the low-level requirements and code done and the cases and procedures complete; tests dry-run on each build while the formal runs wait for the baseline.
  • Verification and Structural Coverage: maturity 1.0, Complete. Requirements-based and robustness tests run on the baselined executable object code on the target, with structural coverage closed or justified.^D
• Process assurance and quality^A
  • Detailed Design: maturity 0.8, Feature complete. Design reviews audited and their records complete; the transition into the build and formal verification checked.
  • Implementation and Integration: maturity 0.8, Feature complete. Design reviews audited and their records complete; the transition into the build and formal verification checked.
  • Verification and Structural Coverage: maturity 1.0, Complete. Every development and verification transition audited against the plans with findings closed; the conformity review and production quality audits build on that record.
• Configuration and change management^A
  • Detailed Design: maturity 0.8, Feature complete. Design baselines and problem reports under control, and the configuration baseline record released for the build that goes to formal verification.
  • Implementation and Integration: maturity 0.8, Feature complete. Design baselines and problem reports under control, and the configuration baseline record released for the build that goes to formal verification.
  • Verification and Structural Coverage: maturity 1.0, Complete. Verified baseline recorded with every problem report dispositioned, and the qualified configuration identified.
• Tools and design environment^O
  • Detailed Design: maturity 0.8, Feature complete. Qualification data for the design tools largely complete and the environment controlled for the detailed design.
  • Implementation and Integration: maturity 1.0, Complete. Tool qualification data complete for every tool whose output is not otherwise verified, and the build environment controlled so builds can be reproduced.^O
  • Verification and Structural Coverage: maturity 1.0, Complete. Tool qualification data complete for every tool whose output is not otherwise verified, and the build environment controlled so builds can be reproduced.
• Environmental qualification and compliance^A
  • Detailed Design: maturity 0.5, Draft. Equipment qualification plan released with the conceptual design, and the detailed design analysed for thermal, electromagnetic and reliability margins.
  • Implementation and Integration: maturity 0.8, Feature complete. Qualification procedures released and test articles built to the build baseline; qualification testing under way.
  • Verification and Structural Coverage: maturity 0.8, Feature complete. Qualification procedures released and test articles built to the build baseline; qualification testing under way.
• Components, supply and export^A
  • Detailed Design: maturity 0.5, Draft. Component selection list issued for the conceptual design, with obsolescence and counterfeit risk reviewed for each part.
  • Implementation and Integration: maturity 0.8, Feature complete. Every part on the build baseline approved and bought through controlled sources; part qualification and derating evidence being gathered.
  • Verification and Structural Coverage: maturity 0.8, Feature complete. Every part on the build baseline approved and bought through controlled sources; part qualification and derating evidence being gathered.
• Production and manufacturing test^A
  • Implementation and Integration: maturity 0.0, Planned. Production approach, line and test strategy planned from the build baseline.
  • Verification and Structural Coverage: maturity 0.3, Early draft. Production transition started: manufacturing and test procedures drafted from the hardware build data.