CPSM CPSM Requirements Engineering & Analysis 2

Question 1

What is the purpose of a Software Requirements Specification (SRS) document?

Accepted Answer

To provide a complete description of the system's behavior and constraints

Answer

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?

Accepted Answer

Acceptance testing

Answer

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?

Accepted Answer

The tendency of requirements to change during the project lifecycle

Answer

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?

Accepted Answer

Must have, Should have, Could have, Won't have

Answer

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?

Accepted Answer

Different team members interpreting requirements differently, leading to rework

Answer

Ambiguous requirements lead to inconsistent implementations because team members may interpret them differently, resulting in costly rework.

(CPSM) Certified Software Project Manager Practice Test