During the requirement life cycle management, what should a business analyst (BA) do to extend the value of requirements beyond the current initiative?

Question

Options

• AAssess
• BMaintain
• CTrace
• DPrioritize

• A
  5% (1)
• B
  91% (20)
• C
  5% (1)

Explanation

Maintain is correct because maintaining requirements means managing them as living assets - keeping them accurate, current, and reusable - so they deliver value in future initiatives, not just the one they were created for. This is the only option that explicitly extends requirements beyond the current initiative by treating them as organizational knowledge worth preserving.

Why the distractors are wrong:

• A. Assess - Assessing requirements evaluates their quality or feasibility within the current initiative; it doesn't inherently preserve or extend their value afterward.
• C. Trace - Tracing links requirements to other artifacts (tests, designs, goals) for coverage and impact analysis, which is valuable during an initiative but doesn't specifically extend value beyond it.
• D. Prioritize - Prioritizing determines what gets worked on first in the current initiative scope; it's a scoping activity, not a lifecycle-extension activity.

Memory tip: Think of Maintain = Museum curator. A curator doesn't just display artifacts for one event - they preserve, catalog, and make them available for future visitors. A BA who maintains requirements does the same: they keep them alive and accessible for future teams and projects.

No community discussion yet for this question.