This is essentially the same result as that of the USAF Accelerated Acquisition Approach of the late 1970s. The ability of acquirers to define and derive “good” requirements is essentially eliminated in “capabilities-based” systems.
This results in innovative solutions at the expense of requirements equivalence from competing suppliers, and a general inability of acquirer engineering personnel to ensure requirements completeness because of the often very large number of “competing” requirements. When coupled with the complaint voiced earlier, the situation launches a “perfect storm” of inadequate specification and end-user
dissatisfaction.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Systems Engineering 2.pdf | application/pdf | 31.31 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
Since the discipline’s inception, the mission of
systems engineering (SE) has been to “engineer
the system” to meet acquirer/user needs within
budget and on schedule. In that same time
frame, the demands on SE have become more
challenging: to engineer larger and more complex
collaborative systems (what some call “systems
of systems”) that could not be conceived
of a half-century ago.