Stakeholder Needs and Concept of Operations Flashcards
6 cards from real ASEP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Stakeholder Needs and Concept of Operations flashcards as text
In systems engineering, what does 'voice of the customer' (VOC) analysis help achieve?
Answer: Translating customer statements into actionable system requirements
VOC analysis captures and translates customer statements, desires, and pain points into structured requirements that engineers can design to.
A 'mission profile' in a ConOps typically describes:
Answer: The sequence of phases, environments, and durations the system will experience during a typical mission
A mission profile describes the sequence of operational phases, the environments experienced, and the time spent in each phase during a representative mission.
Which conflict resolution approach is MOST appropriate when two stakeholder groups have opposing needs?
Answer: Facilitate a structured negotiation to find an acceptable trade-off backed by objective data
Structured negotiation using objective data (trade studies, cost-benefit analysis) is the most appropriate way to resolve stakeholder conflicts while keeping all parties engaged.
What is the purpose of a 'needs validation' review early in a project?
Answer: To confirm that the elicited needs accurately reflect what stakeholders truly require before requirements are written
A needs validation review ensures that the captured stakeholder needs are accurate, complete, and agreed upon before they are translated into formal requirements.
In the ASEP body of knowledge, what distinguishes 'functional requirements' from 'non-functional requirements'?
Answer: Functional requirements describe what the system must do; non-functional requirements describe quality attributes like performance, reliability, or usability
Functional requirements specify system functions (what it must do), while non-functional requirements specify quality attributes (how well it must do it).
Why is it important to engage stakeholders throughout the entire system life cycle, not just at the beginning?
Answer: Because stakeholder needs and operational environments can evolve, requiring requirements to be updated accordingly
Stakeholder needs and external conditions change over time; ongoing engagement ensures the system continues to address real needs and allows requirements to be updated before changes become too costly.