CCBA practice question 33 of 35

A business analyst (BA) is eliciting requirements for a pharmaceutical distribution company with an expansion plan across many states, each with their own tools and methods. To make the requirements as re-usable as possible, what should the BA do?

Full set: 638 questions
Answer options
A: Make specific references to applications or departments
B: Provide details for the requirements
C: Describe the requirements at a high level of abstraction Correct answer
D: Limit the relationships between requirements
Correct Answer:
C. Describe the requirements at a high level of abstraction
Explanation

To make requirements reusable across different contexts (states with varying tools and methods), they must be independent of specific implementations. Describing requirements at a high level of abstraction achieves this by focusing on the fundamental business need or goal (the "what") rather than the specific way it is accomplished (the "how"). This approach ensures the core requirement remains valid and can be implemented using different tools, applications, or departmental procedures, maximizing its reusability across the expanding organization.

Why Incorrect

A. Make specific references to applications or departments: This action directly contradicts the goal of reusability by tying the requirement to a specific context, making it difficult to apply elsewhere.
B. Provide details for the requirements: Excessive detail, especially implementation-specific detail, limits reusability as those details may not be applicable in other environments.
D. Limit the relationships between requirements: While managing dependencies is important, arbitrarily limiting them is not the primary method for achieving reusability. A set of related abstract requirements can be highly reusable.

References

- IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK Guide)

version 3

2015

Section 7.2.4.2 (Maintain Requirements - Maintain for Re-use)

p. 151.

- IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK Guide)

version 3

2015

Section 7.1.4.4 (Trace Requirements - Level of Formality)

p. 146.

Scroll to Top