If a requirement has been satisfied, why is it still considered a requirement?
A) A requirement is considered a requirement as long as the requirement may be able to be changed.
B) Requirements are considered requirements even if the requirements have been satisfied.
C) A requirement is considered valid as long as the business stakeholders need it.
D) If a requirement has been satisfied, it is no longer a requirement and should be purged from the requirements set.

Question

If a requirement has been satisfied, why is it still considered a requirement?
A) A requirement is considered a requirement as long as the requirement may be able to be changed.  
B) Requirements are considered requirements even if the requirements have been satisfied.
C) A requirement is considered valid as long as the business stakeholders need it.
D) If a requirement has been satisfied, it is no longer a requirement and should be purged from the requirements set.

Quizplus · Accepted Answer

A requirement is considered valid as long as the business stakeholders need it. This is true for ongoing requirements that are reused in the organization. Answer: D is incorrect. This isn't a valid statement as to why satisfied requirements are still considered requirements. Answer: B is incorrect. This isn't a valid statement as to why satisfied requirements are still considered requirements. Answer: A is incorrect. This isn't a valid statement; the ability to change a requirement doesn't make it necessarily a satisfied requirement.

If a Requirement Has Been Satisfied, Why Is It Still