When examining requirements relationships, " unambiguous " is a key quality criterion . It ensures that the nature of the relationship between two or more requirements is clearly understood and not open to multiple interpretations . This clarity is critical for supporting impact analysis, traceability, requirement decomposition, and requirement allocation.
Poorly defined or ambiguous relationships can result in incorrect assumptions about dependencies or sequencing, potentially leading to implementation errors.
Additional Criteria Related to Requirement Relationships (from BABOK Guide v3, Section 5.1 - Trace Requirements):
* Necessity: The relationship exists because one requirement depends on another.
* Correctness: The relationship accurately represents the dependency.
* Consistency: The relationship does not conflict with other requirement links.
* Unambiguity: All stakeholders interpret the relationship in the same way.