MENU
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?
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
12 comments · newest first
KE
Kenda
1 year ago
Surprised that high-level is the best approach here!
TE
Teri
1 year ago
Definitely need to provide details for clarity.
DO
Donte
1 year ago
Wait, isn't limiting relationships a bad idea?
AL
Alyce
1 year ago
Totally agree, specifics can limit flexibility.
NG
Nguyet
1 year ago
High-level abstraction is key for reusability!
EV
Eva
1 year ago
I recall something about limiting relationships between requirements could lead to confusion. I’m not sure if that’s the right approach here.
MA
Maia
1 year ago
I practiced a similar question where we had to balance detail and abstraction. I think high-level descriptions are key for broader applicability.
MA
Madalyn
1 year ago
I'm not entirely sure, but I feel like making specific references to applications might limit how reusable the requirements are.
NI
Nina
1 year ago
I remember we discussed the importance of abstraction in requirements gathering. I think describing the requirements at a high level could help with reusability.
FR
Franklyn
1 year ago
Alright, let me break this down step-by-step. The question is asking about the location of an XML file used by URL Scan, which is part of the EMPS application. Based on my understanding of the typical EMPS installation structure, I believe the correct answer is option D.
LE
Lettie
1 year ago
Okay, I've got this. Import quotas are a type of non-tariff barrier, so the answer has to be D. Tariffs are a different kind of trade barrier.
TR
Truman
1 year ago
I think the key here is to identify the methods that allow the organization to produce a single invoice for a customer based on multiple contract projects. Based on that, I would go with B) creating a program where all costs roll up to the program level, which can then be billed, and C) running the invoice consolidation concurrent request to produce a single invoice.