CPSM Requirements Engineering & Analysis Flashcards
6 cards from real CPSM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 CPSM Requirements Engineering & Analysis flashcards as text
What is the purpose of a Software Requirements Specification (SRS) document?
Answer: To provide a complete description of the system's behavior and constraints
An SRS formally documents all functional and non-functional requirements, serving as a contract between stakeholders and the development team.
Which requirements validation technique involves executing the software with test data to check requirements implementation?
Answer: Acceptance testing
Acceptance testing validates that the implemented software meets the agreed requirements before final delivery to the customer.
What does 'requirements volatility' refer to in software project management?
Answer: The tendency of requirements to change during the project lifecycle
Requirements volatility describes how frequently requirements change over time, which significantly impacts project planning and risk management.
In requirements prioritization, the MoSCoW method categorizes requirements into which groups?
Answer: Must have, Should have, Could have, Won't have
MoSCoW stands for Must have, Should have, Could have, and Won't have — a technique to prioritize requirements by necessity.
What is the main risk of having ambiguous requirements in a software project?
Answer: Different team members interpreting requirements differently, leading to rework
Ambiguous requirements lead to inconsistent implementations because team members may interpret them differently, resulting in costly rework.
Which technique involves creating a working model of the system to help stakeholders clarify requirements?
Answer: Prototyping
Prototyping creates an early working version of the system to help stakeholders visualize and refine their requirements.