A team is working on a user privilege and access control system. A business analyst (BA) selects use cases as the technique for requirements specification.
What is the relationship between use cases "Create a role" and "Find a role" when there is a high level of formality?
The relationship between the use cases 'Create a role' and 'Find a role' when there is a high level of formality is best described as 'Necessity'. This is because 'Find a role' can only make sense and be implemented if 'Create a role' is already in place. Without the creation of roles, finding them would be impossible, making 'Find a role' a dependent requirement on 'Create a role'.
• Necessity: when it only makes sense to implement a particular requirement if a related requirement is also implemented. BABOK Page-82
can be one way or bi-directional
derive
Based on V3, the correct relationship between "Create a role" and "Find a role" when there is a high level of formality would be: Option B: Derive This is because the "Find a role" requirement is derived from the "Create a role" requirement. In a formal context, the ability to find a role typically depends on roles being created first. Therefore, "Find a role" is derived from the prerequisite action of "Create a role." pg81: Derive: relationship between two requirements, used when a requirement is derived from another requirement. This type of relationship is appropriate to link the requirements on different levels of abstraction. For example, a solution requirement derived from a business or a stakeholder requirement.
C - Necessity "Find a role" is needed only if "Create a role" is implemented
"Find role" use case depends on "Create role". If the role doesn't exists, then it's impossible to find it. It's clearly not a derived relationship. Necessity is a depending relationship, so yes, answer C is correct
Necessity
its correct in both direction, create a role is a necessity for finding a role and finding a role can lead to a role creation ( if it is not available)