Requirements Definition and Analysis 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 Requirements Definition and Analysis flashcards as text
Which verification method is most appropriate for confirming that a system meets a quantitative performance requirement?
Answer: Test
Testing is the preferred verification method for quantitative performance requirements because it provides objective, measured evidence of compliance under controlled conditions.
What is the significance of the 'shall' keyword in requirements statements according to systems engineering standards?
Answer: It denotes a mandatory, binding requirement that must be met
In requirements engineering, 'shall' indicates a mandatory requirement that the system must satisfy, distinguishing it from 'should' (goal) and 'may' (optional).
During requirements elicitation, why is it important to identify and resolve conflicting requirements early?
Answer: Unresolved conflicts lead to design compromises, rework, and potential system failures if discovered late
Unresolved conflicting requirements create design problems, force costly rework, and may lead to system failures if contradictions are discovered during integration or testing.
What distinguishes functional requirements from non-functional requirements in systems engineering?
Answer: Functional requirements describe what the system must do; non-functional requirements describe how well it must perform or constraints it must satisfy
Functional requirements define what the system must do (capabilities and behaviors), while non-functional requirements define quality attributes and constraints on how the system performs.
What is the purpose of requirements decomposition in the systems engineering Vee model?
Answer: To progressively refine high-level requirements into increasingly detailed specifications at each level of the system hierarchy
Requirements decomposition breaks high-level requirements into progressively more detailed specifications at each hierarchical level (system, subsystem, component) along the left side of the Vee.
Why should requirements include specific acceptance criteria?
Answer: To enable objective verification by providing clear, measurable conditions that determine whether the requirement has been met
Acceptance criteria define the specific, measurable conditions that determine whether a requirement is satisfied, enabling objective and repeatable verification.