When a potential requirement is identified, what is the next logical step?

Question

Options

• AMaintain
• BTrace
• CPrioritize
• DAssess

• A
  4% (2)
• B
  2% (1)
• C
  6% (3)
• D
  88% (44)

Explanation

Assessing (D) is the correct next step because a "potential" requirement is unvalidated - before investing effort in it, you must evaluate whether it's feasible, necessary, and aligned with business goals. Assessment determines if the requirement should even enter the formal process.

Why the distractors are wrong:

• A. Maintain - Maintenance is an ongoing lifecycle activity for requirements already accepted and baselined, not a first response to something newly identified.
• B. Trace - Tracing establishes relationships between requirements and other artifacts, but there's nothing meaningful to trace until the requirement has been validated.
• C. Prioritize - Prioritization ranks requirements against each other, but you can't responsibly rank something you haven't yet confirmed is valid or feasible.

Memory tip: Think of the sequence as a funnel - Identify → Assess → Prioritize → Trace → Maintain. "Assess" is the gatekeeper: a potential requirement must pass evaluation before it earns a place in the pipeline. If you jump straight to prioritizing or tracing, you risk wasting effort on something that shouldn't exist at all.

No community discussion yet for this question.