Requirement Relationships in BA
Requirement Relationships in BA are a matter of life and death for every business analyst, and she must clearly identify the relationships between them in order to achieve the appropriate solution.
Here’s a summary of the different types of relationships considered in traceability for business analysis:
- Derive
- Links requirements at different abstraction levels.
- Used when a requirement is derived from another.
- Example: A solution requirement derived from a business or stakeholder requirement.
- Depends
- Shows dependency between two requirements.
- Types of dependency:
- Necessity: One requirement must be implemented for another to make sense.
- Effort: One requirement is easier to implement if another is implemented.
- Satisfy
- Connects an implementation element with the requirement it fulfills.
- Example: A functional requirement linked to the solution component that implements it.
- Validate
- Links a requirement to a test case or other verification element.
- Ensures that the solution meets the requirement.
Types of Requirement Relationships in Traceability
📌 1. Derive
📍 What it means: A requirement is created based on another requirement.
📍 Use case: Helps connect different levels of abstraction.
📍 Example: A business requirement leads to a solution requirement.
🔗 2. Depends (Two types)
🔹 Necessity: Requirement A must exist for Requirement B to make sense.
🔹 Effort: Requirement A makes it easier to implement Requirement B.
📍 Example: A login system (Requirement A) must exist before implementing multi-factor authentication (Requirement B).
✅ 3. Satisfy
📍 What it means: Links an implemented solution to the requirement it fulfills.
📍 Example: A mobile payment feature satisfies the requirement for contactless transactions.
🛠 4. Validate
📍 What it means: Ensures that a requirement has been met through testing.
📍 Example: A test case confirms that a checkout process meets the functional requirement.
Other Business Analysis Articles:
