When examining requirements relationships, the business analyst (BA) ensures the relationships satisfy the following quality criteria:

Question

Options

• Atestable.
• Bindependent.
• Cmeasurable.
• Dunambiguous.

• A
  2% (1)
• B
  5% (2)
• D
  93% (39)

Explanation

When a BA examines relationships between requirements (dependencies, conflicts, derivations), the relationship itself must have exactly one interpretation-unambiguous-so all stakeholders understand it the same way. A relationship that could mean two different things undermines the entire model of how requirements connect.

A (Testable) is a quality criterion for individual requirements, asking whether you can verify a requirement is met-it doesn't apply to the connection between requirements. B (Independent) actually contradicts the premise: examining a relationship presupposes requirements are related; independence is an Agile user-story principle (the "I" in INVEST), not a relationship quality. C (Measurable) applies to individual requirements or acceptance criteria where you need quantifiable outcomes, not to the nature of a link between requirements.

Memory tip: Think of a relationship as a road sign between two cities-if the sign is ambiguous ("maybe turn here?"), no one reaches the right destination. Requirements relationships must point clearly in one direction: Unambiguous = Unidirectional in meaning.

No community discussion yet for this question.