Analyzing and reviewing the proposed system in detail with the user is
essential to determine the drivers for each operational requirement.
Operational requirements scrubbing involves eliminating those that have no
strong basis. This also provides the PMO and the user with an understanding of
what the real needs are and allows them to establish accurate system
requirements for the critical performance. Operational requirements scrubbing
essentially consists of developing answers to the following questions:
- Why is the requirement needed?
- What will the requirement provide?
- How will the capability be used?
- Are the requirements specified in terms of functions and capabilities,
rather than a specific design?
Cost/requirement trade studies are used to support operational requirements
scrubbing. These trades examine each requirement and determine the cost to
achieve various levels of the requirement (e.g., different airspeeds, range,
payloads). The results are then used to determine, with the user, whether a
particular requirement level is worth the cost of achieving that level. Trade
studies are an inherent part of the systems engineering process. (See
Deskbook 2.6.1 for details on systems engineering