CPSM CPSM Requirements Engineering & Analysis 2 — Questions and Answers
Question 1: What is the purpose of a Software Requirements Specification (SRS) document?
- To document the project budget
- To provide a complete description of the system's behavior and constraints (Correct answer)
- To outline the team's daily tasks
- To list hardware procurement needs
Correct 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.
Question 2: Which requirements validation technique involves executing the software with test data to check requirements implementation?
- Requirements review
- Prototyping
- Model validation
- Acceptance testing (Correct answer)
Correct answer: Acceptance testing
Acceptance testing validates that the implemented software meets the agreed requirements before final delivery to the customer.
Question 3: What does 'requirements volatility' refer to in software project management?
- The number of requirements documents produced
- The tendency of requirements to change during the project lifecycle (Correct answer)
- The complexity of technical requirements
- The speed at which requirements are gathered
Correct 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.
Question 4: In requirements prioritization, the MoSCoW method categorizes requirements into which groups?
- Major, Secondary, Core, Wishlist
- Must have, Should have, Could have, Won't have (Correct answer)
- Mandatory, Optional, Suggested, Cancelled, Ongoing
- Mission-critical, Standard, Conditional, Waived
Correct 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.
Question 5: What is the main risk of having ambiguous requirements in a software project?
- Faster development cycles
- Different team members interpreting requirements differently, leading to rework (Correct answer)
- Reduced documentation overhead
- Improved stakeholder engagement
Correct 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.
Question 6: Which technique involves creating a working model of the system to help stakeholders clarify requirements?
- Benchmarking
- Prototyping (Correct answer)
- Gap analysis
- Root cause analysis
Correct answer: Prototyping
Prototyping creates an early working version of the system to help stakeholders visualize and refine their requirements.
CPSM CPSM Requirements Engineering & Analysis 2
What is the purpose of a Software Requirements Specification (SRS) document?