. "2 Relationship Between Systems Engineering and Program Outcome." Pre-Milestone A and Early-Phase Systems Engineering: A Retrospective Review and Benefits for Future Air Force Acquisition. Washington, DC: The National Academies Press, 2008.
The following HTML text is provided to enhance online
readability. Many aspects of typography translate only awkwardly to HTML.
Please use the page image
as the authoritative form to ensure accuracy.
Pre-Milestone A and Early-Phase Systems Engineering: A Retrospective Review and Benefits for Future Air Force Systems Acquisition
responsibility, authority, and accountability to perform the SE functions (including analysis, modeling and simulation, architecture development, requirements management, and so on). Some of the “program discipline” needs to be in pre-Milestone A management.
It is necessary to manage the maturity of technologies prior to Milestone B and to avoid reliance on immature technologies. Technology maturity and risk mitigation plans should be carefully managed as an integral part of program plans.
The above represent lessons learned as a result of problems that arose or successes that were achieved on past or current programs. They are applicable in general. It is crucial for programs currently being formulated or beginning the acquisition process, TSAT and Space Radar being cases in point, that these lessons be applied early. It is incumbent on senior operational and acquisition leadership to enforce the discipline implied by these findings and shared lessons.