The business analyst (BA) should use penalties as a factor to guide the stakeholders when assigning a priority for the requirements that address compliance with regulations regarding access for people with disabilities. Penalties are the negative consequences or costs that may result from not implementing a requirement1. In this case, the penalties may include legal actions, fines, reputational damage, or loss of customers if the new customer portal does not comply with the accessibility regulations. Therefore, the BA should advise the stakeholders to assign a high priority to these requirements to avoid or minimize the penalties.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Business Analysis Planning and Monitoring knowledge area, where prioritizing requirements is a key task for the BA23. It also relates to the Requirements Life Cycle Management knowledge area, where the BA should manage changes to the requirements and communicate them to the stakeholders24. Additionally, the answer is supported by the web searchresults from the tool invocation, which provide more information and examples of prioritizing requirements based on penalties5

This answer is correct because keeping separate records for customers who are also vendors is a duplicate task that can be eliminated by using the new software module. This would improve efficiency and accuracy of data. The other options are not opportunities identified by the BA in this scenario. References: BABOK Guide v3, page 15; CCBA Mock Test, question 9

The type of business analysis stakeholder that Fran is in this scenario is project manager. According to the CCBA® Handbook1, a project manager is a stakeholder who is responsible for managing the project activities and ensuring that they are aligned with the business analysis activities. A project manager also collaborates with the business analyst to plan, monitor, and control the project scope, schedule, budget, and quality. The other options are not relevant to this scenario, as they describe different types of business analysis stakeholders, such as a regulator (A), who is a stakeholder who imposes constraints or standards on the solution, a sponsor ©, who is a stakeholder who authorizes and funds the initiative, or a domain subject matter expert (D), who is a stakeholder who has specialized knowledge or skills related to the business domain or the solution2. References: Business Analysis Expert Certification, CCBA® | IIBA®, CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS

According to ' A Guide to the Business Analysis Body of Knowledge’1, the two most common data models are the entity-relationship diagram and the class model. These are techniques for representing the data elements and their relationships within a system or a domain23. An entity-relationship diagram shows the entities (or objects) and their attributes, and the relationships among them. A class model shows the classes (or types) of objects and their properties, and the associations and generalizations among them4. The other options are not data models, but rather techniques for modeling different aspects of the system or the project, such as the project network diagram (B), which shows the sequence and dependencies of the project activities, the data flow diagram ©, which shows the flow of data and information among the processes, or the WBS (D), which shows the breakdown of the project scope into smaller components. References: Business Analysis Expert Certification, CCBA® | IIBA®, Certification of Capability in Business Analysis™(CCBA®), Business Analysis Certification Competencies, CCBA® | IIBA®, A GUIDE TO THE BUSINESS ANALYSIS BODY OF KNOWLEDGE

 The scenario describes a task that involves establishing a governance process for the project, which is a part of the business analysis planning and monitoring knowledge area. According to the CCBA® Handbook and the IIBA® website, the inputs for this task are the business analysis approach and the stakeholder engagement approach12. The business analysis approach defines the activities, tasks, techniques, deliverables, and roles and responsibilities for the business analysis work. The stakeholder engagement approach defines the strategies and plans for engaging and communicating with stakeholders throughout the project. These inputs provide the BA with the necessary information and guidance to identify and document the governance process for the project.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the business analysis planning and monitoring knowledge area, including the task of plan business analysis governance12. The CCBA® resources also describe the inputs and outputs for each task in the business analysis process12.

Comprehensive and Detailed Explanation:Conducting interviewsallows the BA toidentify missing or unrecognized stakeholders by discussing roles and responsibilities with existing stakeholders.

BABOK® Guide (Chapter 4.2 - Conduct Stakeholder Analysis)states thatinterviews help uncover stakeholders who might not have been initially identified.

Functional decomposition (Option A)breaks down processes but does not identify stakeholders.

Risk analysis (Option B)assesses risks but does not determine stakeholder involvement.

Lessons learned (Option D)improve future projects but do not resolve current stakeholder identification issues.

Brainstorming is a technique that involves generating a large number of ideas from a group of participants in a creative and spontaneous manner. The purpose of brainstorming is to explore different perspectives, stimulate innovation, and identify potential solutions. One of the rules for brainstorming is to allow any ideas for possible solutions, even if they are not in the defined area of interest. This rule encourages participants to think outside the box, avoid criticism or judgment, and build on each other’s ideas. This rule can help to generate more diverse and original ideas, and to discover new opportunities or connections12

Option A is incorrect because creating a goal for the number of ideas the group should generate is not a rule for brainstorming. While having a goal can help to motivate and focus the group, it can also limit the creativity and quality of the ideas. The goal should be flexible and realistic, and not compromise the purpose of brainstorming3

Option C is incorrect because setting a time limit for the session is not a rule for brainstorming. While having a time limit can help to manage the session and avoid wasting time, it can also pressure the group and hinder the flow of ideas. The time limit should be appropriate and adjustable, and not interfere with the process of brainstorming4

Option D is incorrect because rating each idea that is generated is not a rule for brainstorming. Rating ideas is a part of the evaluation and selection process, which should be done after the brainstorming session. Rating ideas during the session can discourage the group and reduce the quantity and diversity of the ideas. The rule is to defer judgment and evaluation until all the ideas are generated12 References: Business Analysis Techniques - ECBA, CCBA, CBAP Endorsed, Section 7.1: Brainstorming; Certification of Capability in Business Analysis (CCBA®) - Simplilearn, Module 6: Elicitation and Collaboration, Lesson 6.2: Prepare for Elicitation; Business Analysis Body of Knowledge (BABOK® Guide), Section 10.1: Brainstorming, 10.1.3.2: Time Limit; Doing Better Brainstorming: A Business Analyst’s Guide.

Time boxing/budgeting is a technique for delivering prioritized requirements based on the work the project team can deliver within a set period. It is typically used on Agile Projects characterized by fixed deadlines and solutions that require frequent enhancements. With this technique, the project team can guarantee the delivery of the most important requirements on specific dates, with other requirements scheduled for release on successive dates. References:

What Is Timeboxing? — Business Analyst Learnings

Prioritization techniques in business analysis - The Functional BA

The project manager is a key stakeholder in any project and has a vital role in the requirements workshop. The project manager will help elicit requirements from the stakeholders by asking relevant questions, clarifying ambiguities, resolving conflicts, and ensuring alignment with the project scope and objectives12. The project manager will also collaborate with the business analyst, who is the primary facilitator of the requirements workshop, to plan, prepare, conduct, and document the workshop outcomes34. References:

Requirements Management and Role of Project Managers, section “Requirements Management and the Role of Project Managers”

13 Key Project Manager Roles and Responsibilities, section “8. Monitoring progress and tracking roadblocks”

The project manager role — responsibilities, skills, and more, section “The project manager ensures each team member completes their assigned tasks”

15 Key Project Roles & Their Responsibilities, section “The project manager is the one who’s responsible for the project”

According to the BABOK Guide, validating performance measures and alignment with KPIs is a technique for evaluating solution performance. This technique can help the BA determine whether the system is performing as intended and address the concerns of the CEO, as it provides evidence of how well the system meets the expected outcomes and benefits3. By comparing the performance measures with the key performance indicators (KPIs), the BA can assess if the system is delivering value to stakeholders and meeting their needs and expectations. Therefore, the correct answer is D. References: BABOK Guide, [CCBA Mock Test]

The business analyst (BA) should have analyzed the completeness of the use case scenarios to avoid the situation of missing important pieces of information in the system. According to the BABOK Guide, completeness is “the degree to which a set of requirements contains all the information necessary to achieve the business objectives” 3. By analyzing the completeness of the use case scenarios, the BA can ensure that they cover all the possible paths, exceptions, preconditions, postconditions, and data elements of the system. Performing decision analysis, identifying assumptions, and preparing activity diagrams are useful techniques, but they do not directly address the issue of completeness. References: 3: BABOK Guide, Version 3, Section 8.2 Analyze Current State

Comprehensive and Detailed Explanation:This checklist aligns withrequirement verification, which ensures that the requirements arecomplete, clear, testable, and feasible before they are validated or implemented.

BABOK® Guide (Chapter 8.2 - Verify Requirements)states that requirements must be evaluated against criteria such asclarity, feasibility, testability, and correctnessto beconsidered complete and usable.

Validation (Option A)focuses on ensuring requirements meet business needs, butverification (Option D) ensures their structure and quality are correct.

Measuring solution performance (Option B)occurs after implementation, not during requirements definition.

Comprehensive and Detailed Explanation:Theimpact analysis should assess the number of systems affectedby the change to determine its feasibility and risk. TheBABOK® Guide (Chapter 5.5 - Assess Requirements Changes)states that understandinghow changes impact systems, stakeholders, and business objectivesis essential before implementing modifications.

Comprehensive and Detailed Explanation:Whenelicitation results are inconsistent, the BA shouldmodel the requirements and present them in a review meetingto facilitate stakeholder discussion and resolution.

BABOK® Guide (Chapter 3.3 - Confirm Elicitation Results)states that usingmodels such as use cases, process diagrams, or prototypes can help align stakeholder understanding and resolve inconsistencies.

Letting the project manager decide (Option B, C)is inappropriate because requirement alignment is abusiness analysis responsibility.

The BA selecting the requirements (Option D)without stakeholder input may introduce bias.

Comprehensive and Detailed Explanation:Requirements management toolsprovidea structured way to document requirement changes, maintain traceability, and track approvals.

BABOK® Guide (Chapter 5.1 - Trace Requirements)states thattraceability ensures every requirement is linked to its origin and tracks changes throughout the project lifecycle.

Risk analysis and management (Option A)addresses uncertainties but does not document requirement history.

Acceptance and evaluation criteria (Option B)define success conditions but do not track approvals.

Legal and regulatory information (Option D)ensures compliance but does not track requirement history.