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
What characteristic distinguishes a well-formed requirement from a poorly written one according to INCOSE guidelines?
Answer: It is singular, unambiguous, measurable, and verifiable
INCOSE guidelines specify that well-formed requirements must be singular (addressing one need), unambiguous, measurable, and verifiable through testing or analysis.
What is the primary purpose of requirements validation as opposed to requirements verification?
Answer: To confirm that the requirements accurately reflect stakeholder needs and expectations
Requirements validation confirms that the documented requirements actually capture what stakeholders need, while verification confirms the system meets those requirements.
In requirements analysis, what does 'derived requirement' mean?
Answer: A requirement that emerges from design decisions, analysis, or architectural choices rather than directly from stakeholder needs
Derived requirements emerge from design decisions, architectural choices, or analysis rather than being directly traceable to an originating stakeholder requirement.
Which requirements analysis technique uses structured scenarios to explore system behavior under various conditions?
Answer: Use case analysis
Use case analysis employs structured scenarios describing actor-system interactions to explore and document system behavior under normal and exceptional conditions.
What risk does requirements creep pose to a systems engineering program?
Answer: It introduces uncontrolled growth in scope, potentially impacting cost, schedule, and technical performance
Requirements creep is the uncontrolled addition of new requirements after baselines are established, which can increase cost, extend schedule, and degrade system performance.
What is the purpose of a Requirements Traceability Matrix (RTM) in systems engineering?
Answer: To document bidirectional links between requirements at different levels and to verification activities
An RTM documents the bidirectional trace between requirements at all levels (stakeholder, system, subsystem) and links them to design elements and verification activities.