The evolution of the five baselines is illustrated in

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: and kept current for the entire project life cycle. 4.7.1 Baseline Evolution The project-level system engineer is responsible for ensuring the completeness and technical integrity of the technical baseline. The technical baseline includes: • • • • • • Functional and performance requirements (or specifications) for hardware, software, information items, and processes Interface requirements Specialty engineering requirements Verification requirements Data packages, documentation, and drawing trees Applicable engineering standards. The project baseline evolves in discrete steps through the project life cycle. An initial baseline may be established when the top-level user requirements expressed in the Mission Needs Statement are placed under configuration control. At each interphase control gate, increased technical detail is added to the maturing baseline. For a typical project, there are five sequential technical baselines: • Functional baseline at System Requirements Review (SRR) • • • • "Design-to" baseline at Preliminary Design Review (PDR) "Build-to" (or "code-to") baseline at the Critical Design Review (CDR) "As-built" (or ''as-coded,,) baseline at the System Acceptance Review (SAR) "As-deployed" baseline at Operational Readiness Review (ORR). The evolution of the five baselines is illustrated in Figure 17. As discussed in Section 3.7.1, only decisions made along the core of the "vee" in Figure 7 are put under configuration control and included in the approved baseline. Systems analysis, risk management, and development test activities (off the core of the vee) must begin early and continue throughout the decomposition process of the project life cycle to prove that the core-level decisions are sound. These early detailed studies and tests must be documented and retained in the project archives, but they are not part of the technical baseline. 4.7.2 Techniques of Configuration Management...
View Full Document

This document was uploaded on 02/26/2014 for the course E 515 at University of Louisiana at Lafayette.

Ask a homework question - tutors are online