Q302. Management has asked you, a business analyst for your organization, to create the solution scope for an identified problem. In order to complete this task, you’ll need three elements.
All of the following are elements you’ll need in order to write the solution scope except for which one?
Explanation
The work breakdown structure (WBS) is not an element of the solution scope, but rather a project management tool that decomposes the project scope into manageable deliverables and tasks. The WBS is created after the solution scope is defined and approved, and it helps to plan, monitor, and control the project execution.
The other options are elements of the solution scope, which are:
B: Implementation approach, which describes how the solution will be delivered, such as the methodology, the phases, the roles and responsibilities, and the quality measures.
C: Solution scope definition, which describes what the solution is, what it does, and what it does not do, in terms of the features, functions, and characteristics that address the business need.
D: Dependencies, which describe the relationships and interactions between the solution and other internal or external factors, such as other projects, systems, processes, or stakeholders.
References:
CBAP Handbook, page 15, section 4.1.2.3
BABOK Guide, page 32, section 3.2.3
Solution Scope – An Insight
How To Write a Project Scope in 5 Steps (With Example)
Q307. A business analyst (BA) elicits requirements for the sales order processing of multiple product lines.
Elicitation reveals that the business processes for the sales orders of most products follow similar activity patterns that have been established over a number of years. Some of the new proposed seasonal products, however, will necessitate major variations in the process flow of some departments. The seasonal products are likely to be different every year. The business needs to carefully adapt its business practices so that the significant but seasonal variations in some of the business processes for the new products are handled adequately without disrupting the processes for the other established products.
Which of the following approaches must the BA take to manage the requirements for sales order processing in the long term?
Explanation
A high level of abstraction means that the requirements are expressed in general terms, without specifying details or implementation methods. This allows the requirements to be more flexible and adaptable to changing business needs and contexts. For the seasonal products, which are likely to be different every year and require major variations in some business processes, using a high level of abstraction would help to manage the requirements in the long term, as they would not need to be revised or updated frequently. On the other hand, using a low level of abstraction, which means that the requirements are expressed in specific and detailed terms, would make the requirements more rigid and prone to changes, as they would need to be aligned with the particular characteristics and constraints of each seasonal product and process variation.
References:
CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 3: Requirements Elicitation, p. 97-98
[BABOK Guide v3], Section 4.1: Prepare for Elicitation, p. 94-95
Certified Business Analysis Professional (CBAP) Specialization, Course 2: Business Analysis:
Requirements Analysis and Design Definition, Week 2: Requirements Classification and Prioritization, Video: Requirements Abstraction Levels
Q310. You are the business analyst for your organization. You are currently working with Steve on the organize requirements process. You and Steve have elected to use the user stories approach for this process.
What is the user stories approach for requirements organization?
Explanation
The user stories approach for requirements organization is a technique that involves describing the stakeholders’ objectives, needs, and expectations in a concise and simple way. User stories are usually written in the format of “As a [role], I want [goal], so that [benefit]”. User stories help to capture the essence of what the stakeholders want from the solution, without going into too much detail or specifying a particular solution.
User stories are useful for eliciting, prioritizing, and validating the requirements, as well as for communicating and collaborating with the stakeholders. User stories can also be used to create scenarios, use cases, and test cases1234. References: 1: User Stories | Examples and Template | Atlassian1 2: Chapter 15: Requirements and user stories – Agile Business2 3: Aligning User Stories, Use Cases and Requirements – Dice3 4: Writing User Stories for Requirements Gathering – Medium4
Q314. A health insurance provider undertakes enhancements to its mobile application platform and finalizes the following capabilities as part of the scope of the next release:
I). Ability to integrate online maps and global positioning system (GPS) technology with the mobile application In real time to display location of service providers in the subscriber’s vicinity that participate in the subscriber’s plan network.
II). Ability for the subscriber to lookup the service providers by specifying either a postal code or a search area radius in miles.
III). Ability for the subscriber to initiate the download of fee information for one or more service providers in a single request.
Through requirements workshops the business analyst elicits the following detailed business requirements:
1. The company’s mobile application platform must support real time integrate with the following third party systems:
A). GPS System
B). Postal Code Validation
What is the appropriate model type to assist the stakeholders in testing the performance and visual aspects of requirements 3 through 11?
Explanation
The appropriate model type to assist the stakeholders in testing the performance and visual aspects of requirements 3 through 11 is a usability prototype. A usability prototype is a model that simulates the look and feel of the user interface of the solution, such as the layout, navigation, colors, fonts, and graphics. A usability prototype can help the stakeholders to evaluate the user experience, the ease of use, the accessibility, and the satisfaction of the solution. A usability prototype can also help to identify and resolve any usability issues or defects before the final implementation of the solution. References:
CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model and Validate Requirements, p. 265-266 A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 6:
Requirements Analysis and Design Definition, Section 6.4: Model Requirements, p. 161-162 A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 10:
Solution Evaluation, Section 10.6: Validate Solution, p. 283-284
