nerdexam
IIBA

CBAP · Question #352

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 "

The correct answer is B. Derive. At a high level of formality in use case modeling, 'Create a role' has a derive relationship with 'Find a role' because the creation functionality logically depends on and is derived from the search capability.

Requirements Analysis and Design Definition

Question

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?

Options

  • AValidate
  • BDerive
  • CNecessity
  • DSatisfy

How the community answered

(28 responses)
  • A
    7% (2)
  • B
    79% (22)
  • C
    11% (3)
  • D
    4% (1)

Why each option

At a high level of formality in use case modeling, 'Create a role' has a derive relationship with 'Find a role' because the creation functionality logically depends on and is derived from the search capability.

AValidate

Validate is a requirements relationship used to confirm that a requirement meets a defined condition or criterion, not to describe a functional dependency between two related use cases.

BDeriveCorrect

In BABOK formal requirements relationships, a derive relationship indicates that one requirement or use case is logically derived from another, meaning it cannot be fully defined or executed without the other. 'Create a role' derives from 'Find a role' because any role creation process must incorporate a search to validate that the role does not already exist. This functional dependency at a high formality level is formally expressed as a derive relationship.

CNecessity

Necessity is not a standard formal use case relationship in BABOK for expressing the logical dependency between use case functionality in a high-formality model.

DSatisfy

Satisfy is a requirements relationship where an implementation model element fulfills a requirement, and is not applicable to describing the functional derivation between two use cases within the same specification.

Concept tested: Formal use case relationships - derive dependency

Source: https://www.iiba.org/standards-and-resources/babok/

Topics

#use cases#requirements relationships#formal specification#access control modeling

Community Discussion

No community discussion yet for this question.

Full CBAP Practice