Which of the following processes provides guidance to the system designers and form the basis of major events in the acquisition phases, such as testing the products for system integration?

Question

Options

• AOperational scenarios
• BFunctional requirements
• CHuman factors
• DPerformance requirements

• A
  91% (42)
• B
  2% (1)
• C
  4% (2)
• D
  2% (1)

Explanation

Operational scenarios are narrative descriptions of how a system will be used in real-world conditions, giving system designers a concrete picture of intended use cases. Because they capture the "who, what, when, where, and how" of system employment, they serve as the foundational reference point for major acquisition milestones - including system integration testing, which must validate that the system performs as envisioned in those scenarios.

B (Functional requirements) are wrong here because they are derived from operational scenarios, not the other way around - they define what the system must do, but scenarios provide the guiding context that generates those requirements. C (Human factors) is an engineering discipline applied during design; it's a consideration, not a process that structures acquisition phases. D (Performance requirements) specify how well the system must perform (speed, accuracy, etc.) but, like functional requirements, they flow downstream from operational scenarios.

Memory tip: Think of operational scenarios as the master story of the system - everything else (requirements, tests, milestones) is written to match that story. If integration testing asks "does it work?", the scenario already answered "work for what?"

No community discussion yet for this question.