MENU
A business analyst (BA) is eliciting requirements for a pharmaceutical distribution company with an expansion plan across many states, each with its own tools and methods. To make the requirements as reusable as possible, what should the BA do?
Suggested Answer: A
Get Premium CCBA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Comprehensive and Detailed To makerequirements reusable, they must beabstracted from specific tools, applications, or regions. TheBABOK Guide (Chapter 5.3 - Specify and Model Requirements)suggests thathigh-level abstraction ensures that requirements remain applicable across different locations. Adding too many specifics limits adaptability and reuse.
25 comments · newest first
PA
Paola
6 days ago
Right! We need a framework that fits all scenarios.
CH
Chandra
11 days ago
Exactly! A keeps it broad and applicable everywhere.
FA
Fallon
16 days ago
D could lead to confusion with too many specifics.
PA
Paris
22 days ago
C seems risky. Relationships are important for context.
JE
Jeannetta
27 days ago
Too many details might limit adaptability. A is safer.
KR
Kristian
1 month ago
But what about B? Details can help clarify requirements.
PA
Paola
1 month ago
Agreed! It keeps things flexible for different states.
CH
Chandra
1 month ago
I think A is the best choice. High-level abstraction helps in reusability.
RO
Rory
2 months ago
Yes, we need a framework that can grow with the company.
JO
Josphine
2 months ago
Exactly! A keeps it broad and applicable everywhere.
JA
Jacki
2 months ago
D is too specific. It won't work across all states.
EL
Eleonora
2 months ago
C seems risky. Limiting relationships might cause issues later.
BE
Bea
2 months ago
True, but too many details can limit adaptability.
MA
Marica
2 months ago
But what about B? Details can help clarify requirements.
RO
Rory
3 months ago
I agree, A makes sense. It keeps things flexible for different states.
JO
Josphine
3 months ago
I think A is the best choice. High-level abstraction helps in reusability.
JA
Jamika
3 months ago
I think A) is right, but B) shouldn't be ignored completely.
CR
Crista
3 months ago
C) makes sense. Keeping relationships simple can help with clarity.
KA
Kayleigh
3 months ago
Surprised that anyone would choose D). That limits flexibility!
LI
Lilli
3 months ago
I disagree, B) is more important. Details matter for implementation.
PH
Phuong
4 months ago
A) is definitely the way to go! High-level abstraction helps with reusability.
CL
Clarinda
4 months ago
Making specific references to applications or departments could limit reusability, right? I think we should focus on a more general approach instead.
KI
Kirk
4 months ago
Limiting relationships between requirements seems risky; I feel like they need to be interconnected to make sense, but I can't recall the exact reasoning.
ST
Stacey
4 months ago
I remember a practice question where we had to decide between high-level and detailed requirements, and I think high-level was favored for broader applicability.
LA
Lavelle
4 months ago
I think describing the requirements at a high level of abstraction makes sense for reusability, but I'm not entirely sure if that's the best approach.