If a requirement has been satisfied, why is it still considered a requirement?

The correct answer is B. Requirements are considered requirements even if the requirements have been satisfied. According to the BABOK® Guide, a requirement is a usable representation of a need. A requirement does not cease to be a requirement once it has been satisfied; it remains a requirement as long as the need exists and the solution is in use. Requirements may change over time due…

Requirements Life Cycle Management

Question

Options

AA requirement is considered a requirement as long as the requirement may be able to be
BRequirements are considered requirements even if the requirements have been satisfied.
CA requirement is considered valid as long as the business stakeholders need it.
DIf a requirement has been satisfied, it is no longer a requirement and should be purged from

How the community answered

(44 responses)

B
91% (40)
C
7% (3)
D
2% (1)

Explanation

According to the BABOK® Guide, a requirement is a usable representation of a need. A requirement does not cease to be a requirement once it has been satisfied; it remains a requirement as long as the need exists and the solution is in use. Requirements may change over time due to changes in the business environment, stakeholder needs, or solution performance1.

Topics

#requirements lifecycle#requirement status#requirements management

Community Discussion

No community discussion yet for this question.

Full CCBA Practice