Exam CBAP topic 1 question 300 discussion

• Necessity: when it only makes sense to implement a particular requirement if a related requirement is also implemented. BABOK Page-82

Basically you cannot create the "Find a Role Requirements" if there is no role available. Hence, the find a role requirement entirely depends on the Create Role functionality. So under Depend come Necessity and Effort and the best choice is Necessity

"Flour" is necessary for creating "Bread" (Necessity). You validate the quality of the "Flour" to ensure the "Bread" turns out well (Validate). The "Bread" is derived from the "Flour" (Derive). And finally, the "Bread" satisfies the hunger or dietary need (Satisfy).

I go w B

In a user privilege and access control system, “Create a role” and “Find a role” have a necessity relationship because the ability to find a role is necessary to perform certain actions related to roles, such as modifying or assigning them. If a user cannot find an existing role, managing roles effectively becomes impossible. This type of relationship indicates that one use case (“Find a role”) is required or essential for the other use case (“Create a role”) to function correctly in the system’s overall workflow.

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

derive

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)