Software Engineering

4.2.
 Software Test Plan (Overview)
4.2.1.
  Software Test Strategy
4.2.2.
  Software Test Environment
4.2.3.
  Software Test Cases
4.2.4.
  Test and evaluation Schedule and Milestones
4.3.
  Software Quality Assurance Plan
4.3.1.
  Software Quality Inspections
4.3.2.
  Software Quality Audits
4.3.3.
  Software Quality Schedule and Milestones

---

303
17.7 
Reviews, milestones, and baselines
5.
  Software Control
5.1.
 Updated Project Plans and Schedule
5.2.
 Updated Specification Tree
5.3.
 Updated Work Breakdown Structure
5.4.
  Engineering Artifact Repository
5.5.
 Change History Repository
5.6.
 Technical Risk Repository
5.7.
 Software Nomenclature Registry
2. 
Establish the requirements baseline
. The SWE-IPT should place the software 
requirements specifications under technical configuration control upon success-
ful completion of the software requirements review. These specifications form 
the architectural requirements baseline and establish the foundation for develop-
ing the product functional and physical architectures. The functional baseline 
is comprised of the software product, interface, and computing environment 
specifications. Once the requirements baseline is established it requires techni-
cal CCB approval of a change request or proposal to make any changes to these 
specifications.
The operational model should be captured in the software engineering artifact 
repository since it was the basis for deriving the software requirements. The pre-
liminary functional and physical architectures should not be controlled at this time. 
The functional and physical architectures will continue to evolve during the pre-
liminary architecture definition stage and provide the technical infrastructure for 
expanding the software architectural solution.

---

This page intentionally left blank

---