CBAP Certified Business Analysis Professional Questions and Answers

The potential success rate of the mortgage origination process can be calculated by subtracting the percentage of total rejects from 100%. The current success rate is 70%, which means the current percentage of total rejects is 30%. If the verification rejects (8.4% of the total transactions) were to be reduced by 50%, there would be only 4.2% verification rejects remaining. This would decrease the percentage of total rejects to (30% - 4.2%) = 25.8%. Therefore, the potential success rate would be (100% - 25.8%) = 74.2%. However, this answer does not account for the effect of the documentation checklists, which would also reduce the documentation rejects (12.2% of the total transactions). Assuming that the documentation checklists would eliminate all the documentation rejects, the percentage of total rejects would further decrease to (25.8% - 12.2%) = 13.6%. Therefore, the potential success rate would increase to (100% - 13.6%) = 86.4%, which can be rounded to 86%.

References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 5: Solution Assessment and Validation, p. 211-212

Certified Business Analysis Professional™ (CBAP®) Specialization , Course 4: Business Analysis: Solution Evaluation, Week 2: Solution Performance Assessment, Video: Solution Performance Metrics

Basic Math Operations , Khan Academy

Scope is the important factor that the BA needs to understand to ensure the workshop remains focused on the topic in question. Scope is the boundary or extent of the business analysis effort, which defines what is included and excluded from the change initiative. Scope also provides the contex t and direction for the requirements elicitation and analysis activities. By understanding the scope, the BA can plan and facilitate the workshop effectively, and avoid any irrelevant, out-of-scope, or conflicting discussions or issues. The other options a re not the best answers, as they are not as critical as scope for keeping the workshop focused, although they may be related to the topic in question. For example, future state is the desired outcome of the change initiative, assets are the resources or ca pabilities of the enterprise, and risk register is the document that records the identified risks and their responses.  References :  CBAP Handbook ,  CBAP Study Guide ,  BABOK Guide

The BA needs to perform a root cause analysis to analyze the performance of the application and provide recommendations. A root cause analysis is a technique that involves identifying and addressing the underlying causes of a problem or an issue, rather than the symptoms or the effects. A root cause analysis can help the BA to find out why the solution implemented three months ago has decreased performance as the volume of transactions has increased, and to propose and implement appropriate solutions to improve the performance and prevent the problem from recurring. The other options are not the best actions for the BA to take, as they are more suitable for different purposes, such as measuring the per formance, evaluating the alternatives, or reviewing the existing metrics, rather than finding the root cause of the problem.  References :  Task: Assessing Solution Limitations ,  CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition ,  BABOK Guide

 The BA could have assessed the current state and stakeholder needs to prevent this situation. The current state is the description of the existing situation, including the problems, opportunities, capabilities, and constraints of the organization and its stakeholders. The stakeholder needs are the expectations, preferences, and requirements of the stakeholders that are relevant to the change initiative. By assessing the current state and stakeholder needs, the BA could have identified and documented the existing report “Consolidated Sales by Customer” as a requirement, and en sured that it was not affected or replaced by the new report “Customer Sales by Date”. The BA could have also verified and validated that the new report met the stakeholder needs and did not cause any negative impacts or trade-offs. The other options are n ot the best answers, as they are more related to the evaluation of the solution or the organization, rather than the identification and management of the requirements.  References :  CBAP Handbook ,  CBAP Study Guide ,  BABOK Guide

 Business or technical risk is a requirements prioritization approach that involves ranking the requirements based on the potential negative consequences or uncertainties associated with their implementation or non-implementation. This approach can help to identify and mitigate the most critical risks early in the project and reduce the likelihood of project failure. Busi ness or technical risk can be assessed by considering factors such as the impact on the business value, the feasibility of the solution, the complexity of the requirements, the dependencies among the requirements, the volatility of the requirements, and th e stakeholder satisfaction.  Business or technical risk is one of the common criteria for requirements prioritization, as it helps to balance the benefits and costs of the requirem ents 1 2 3 4 .  References :  1 : Requirement prioritiza tion 3   2 : The Ultimate Guide to Requirements Prioritization 4   3 : Business Analysis Techniques: Prioritizing Requirements 5   4 : Requirements Prioritization: How to Prioritize Requirements

Interface analysis is a technique that identifies and specifies the information that is exchanged between systems or system components. It defines the communications protocol, data format, and timing of the information exchange. Interface analysis is useful for designing and documenting the interactions between the PS and other systems. It can also help to identify potential issues or risks related to the integration of the systems.

Vertical prototyping is a technique that creates a working model of one or more aspects of a solution, such as the user interface, functionality, or performance. It is used to validate the requirements and design of the solution, and to obtain feedback from stakeholders. It is not directly related to defining the communications protocol between the systems.

Concept modelling is a technique that defines the terms and concepts relevant to a domain or a problem. It establishes a common vocabulary and understanding of the domain among the stakeholders. It is not focused on the technical details of the system interactions.

System analysis is a broad term that refers to the process of studying and understanding the current or desired state of a system. It involves identifying the system components, functions, inputs, outputs, and relationships. It is not a specific technique for defining the communications protocol between the systems.  References :

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 10: Techniques, pp. 402-403, 414-415, 420-421, 424-425.

[Business Analysis for Practitioners: A Practice Guide], Chapter 5: Requirements Analysis and Design Definition, pp. 123-124, 133-134, 140-141, 144-145.

 Requirements prioritizatio n is the process of assigning relative importance and urgency to the requirements based on various factors, such as business value, stakeholder needs, risk, dependency, and feasibility. Requirements prioritization helps to define the solution scope by dete rmining which requirements are essential, which are desirable, and which are optional for the solution. Requirements prioritization can be used with both plan- driven and change-driven approaches to business analysis, depending on the level of certainty and stability of the requirements. Requirements prioritization does not depend on the stakeholder importance, but rather on the stakeholder agreement and alignment on the requirements.  References :

BABOK® Guide , p. 54-55

CBAP / CCBA Certified Business Analysis Study Guide , p. 164-165

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 2, Week 1, Video: “Requirements Prioritization”

The specify and model requirements process is the process of defining and describing the requirements in detail and representing them in different formats, such as textual, graphical, or mathematical. The primary purpose of this process is to analyze the functioning of an organization and to provide an insight into opportunities for improvement. By specifying and modeling the requirements, the business analyst can identify the gaps, issue s, and needs of the organization and its stakeholders, and propose solutions that can address them. The specify and model requirements process also helps to communicate, validate, and verify the requirements with the stakeholders and ensure that they are a ligned with the business goals and objectives.  References :

BABOK® Guide , p. 50-51

CBAP / CCBA Certified Business Analysis Study Guide , p. 153-154

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 2, Week 1, Video: “Specify and Model Requirements”

The timing of business analysis work is the most impacted element by the organization’s change from a waterfall methodology to an agile approach. This is because the waterfall and agile methods have different ways of planning, executing, and delivering business analysis work.

In a waterfall method, the business analysis work is done in a sequential and linear manner, following predefined phases and milestones. The requirements are elicited, analyzed, and documented upfront, before the design and development stages. The changes to the requirements are minimized and controlled, and the deliverables are verified and validated at the end of the project. The timing of business analysis work is fixed and predictable, but it may also be rigid and inflexible.

In an agile method, the business analysis work is done in an iterative and incremental manner, following short cycles of development and feedback. The requirements are elicited, analyzed, and documented continuously, along with the design and development stages. The changes to the requirements are welcomed and managed, and the deliverables are verified and validated throughout the project. The timing of business analysis work is variable and adaptable, but it may also be challenging and uncertain.

Therefore, the business analyst (BA) needs to adjust the timing of business analysis work according to the agile method, which involves:

Breaking down the requirements into smaller and manageable chunks, called user stories or features, that can be delivered in each iteration or sprint

Prioritizing and refining the requirements backlog, which is the list of all the requirements that need to be addressed in the project, based on the business value and stakeholder feedback

Collaborating and communicating with the project team and stakeholders frequently and effectively, using various techniques and tools, such as daily stand-ups, retrospectives, demos, etc.

Adapting and responding to the changing requirements and business needs, using various techniques and tools, such as change requests, impact analysis, traceability, etc.

References :

[BABOK Guide v3], Section 2.4: Plan Business Analysis Work, p. 24-27

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 2: Business Analysis Planning and Monitoring, p. 43-44

Certified Business Analysis Professional™ (CBAP®) Specialization , Course 1: Business Analysis: Planning and Monitoring, Week 1: Introduction to Business Analysis Planning and Monitoring, Video: Waterfall vs. Agile

Agile vs. Waterfall | Pros, Cons, and Key Differences - ProductPlan

 Solution scope is the set of capabilities a solution must deliver in order to meet the b usiness need. It describes what is included in the solution, such as features, functions, and characteristics. Solution scope is not concerned with how the solution is delivered, but rather what the solution is. Solution scope is defined by the business an alyst based on the business needs and requirements of the stakeholders.  References :

Business Analysis Professional (CBAP) Certification

Solution Scope – An Insight

Solution Scope vs. Project Scope

 A parametric estimate is an estimate that uses a mathematical formula or model to calculate the time, cost, or resources required for a project or activity based on historical data and known variables. In this scenario, the 25 workstations per hour represents a parametric estimate of the productivity of the project team, which can be used to determine the total duration and cost of the installation. A parametric estimate is usually more accurate and reliable than other estimation techniques, such as expert judgment or analogy, as it is based on objective and quantifiable data.  References :

CBAP Certification Study Guide v3.0 , page 33

BABOK Guide v3 , page 16

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 3, Week 3, Video: “Project Management Concepts”

A flowchart is a business analysis technique that graphically depicts the steps or actio ns involved in a process or workflow. A flowchart consists of four main components: activities, decisions, forks, and joins. Activities are the tasks or steps that are performed in the process. Decisions are the points where a choice must be made between t wo or more alternatives. Forks are the points where the flow splits into two or more parallel paths. Joins are the points where two or more paths converge. Attributes are not a component of flowchart, but rather a term used to describe the characteristics or properties of an entity or object in a data model. 

 Functional decomposition is the analysis of complex systems by breaking them down into smaller simpler elements.  It inv olves breaking down processes, systems, functional areas, or deliverables into simpler components, so that each part can be analyzed separately 1 2 . By breaking down larger components into smaller parts, it allows the organization to measure and track each work effort involved in implementing the solution.  It also helps in the assessment of the effectiveness of each sub-component as it relates to other larger or smaller components 3 .  Functional decomposition is a tec hnique used in business analysis to facilitate the understanding and management of large and complex processes 2 .  It is also used in systems engineering, software architecture, database theory, machine learning, and a variety of other fields 2 .  References :  1 : Functional decomposition in business analysis – The Functional BA  2 : Functional Decomposition: Defini tion, Diagrams, and Applications  3 : 10.22 Functional Decomposition | IIBA®

The lead BA should track approvals at the level of individual requirements, as this is the first step to address the root cause of the problem, which is the lack of agreement and clarity on the requirements. By tracking approvals at the level of individual requirements, the lead BA can identify which requirements are causing the most disagreement or confusion, and focus on resolving them with the relevant stakeholders. This can also help to reduce the number of reviews and sign-offs needed, as well as the time and effort spent on them. Tracking approvals at the level of individual requirements can also provide objective evidence of the progress and quality of the requirements, and support the communication and collaboration among the stakeholders.

The other options are not the best actions to take first. Escalating the problem to the executive management may be necessary at some point, but it is not the first thing t o do, as it may create more conflict and pressure, and undermine the lead BA’s credibility and authority. Setting limits on duration of sign-offs and the number of reviews may be helpful to manage the expectations and deadlines, but it does not address the underlying issue of the requirements quality and agreement. Offering the stakeholders incentives to sign off documents sooner may be counterproductive, as it may encourage hasty or superficial approvals, and compromise the validity and value of the requir ements.  References : The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 6: Requirements Life Cycle Management, p. 202-203, 207-208, 211-212.

Business Analysis for Practitioners: A Practice Guide, Chapter 4: Requirements Life Cycle Management, p. 97-98, 101-102, 105-106.

 A task list is a tool that helps to organize and track the business analysis activities. Each task in the task list must have a unique number that identifies it and allows it to be referenced and tracked. The unique number can also be used to link the task to other elements, such as requirements, deliverables, stakeholders, or risks. The unique num ber can be assigned sequentially or based on a coding scheme that reflects the task hierarchy or category.  References :  BABOK Guide v3 , page 38;  CBAP / CCBA Certified Business Analysis Study Guide , page 77.

 A requirements package is a document that contains a set of requirements that have be en analyzed, refined, and formatted to meet the needs of various stakeholders. The primary goal of developing a requirements package is to communicate the requirements ef fectively and efficiently to the intended audience. A requirements package may include different levels of detail, different types of requirements, different formats and structures, and different supporting information depending on the stakeholder’s needs and preferences. A requirements package should be clear, concise, consistent, complete , correct, and testable.  References :

Certified Business Analysis Professional Handbook , page 24

BABOK Guide, page 121

Risk identification is a process that can start with the source of problems or with the problem itself. Risk identification is the process of determining the risks that may affect the project or the solution, and documenting thei r characteristics. Risk identification can be performed by analyzing the sources of risks, such as the project environment, the stakeholders, the requirements, the assumptions, the constraints, or the dependencies. Risk identification can also be performed by analyzing the problems or issues that may arise during the project or the solution, such as the gaps, conflicts, ambiguities, uncertainties, or changes.  Risk identification he lps to create a list of potential risks and their causes, impacts, and probabilities for further analysis and response planning 1 2 . Risk estimation is a process that follows risk identification. Risk estimation is the process of assessing the likelihood and impact of the identified risks, and prioritizing them according to their severity.  Risk estimation helps to quantify the level of risk exposure and the expected value of the risk for decision making 1 2 . Risk analysis is a process that follows risk estimation. Risk analysis is the process of evaluating the identified and prioritized risks, and dete rmining the appropriate responses to them.  Risk analysis helps to develop strategies and actions to avoid, reduce, transfer, or accept the risks, and to allocate resources and con tingency reserves for risk management 1 2 . Risk management is a process that encompasse s risk identification, risk estimation, risk analysis, and risk monitoring and control. Risk management is the process of planning, identifying, analyzing, responding to, and monitoring and controlling the risks throughout the project or the solution lifec ycle.  Risk management helps to minimize the negative effects and maximize the positive opportunities of the risks, and to ensure the project or the solution objectives are met 1 2 .  References :  CBAP® Handbook ,  CBAP® Exam Prep Study Guide

A feasibility study is a type of document that evaluates the potential solution alternatives and their expected benefits, costs, risks, and impacts on the organization and its stakeholders. A feasibility study also provides data and statistics to support the analysis and recommendations. A feasibility study helps the decision makers to select the most viable and beneficial solution for the business need.

References :

CBAP Handbook , page 10, section 3.4.2.3

BABOK Guide, page 100, section 6.1.5.2

 Functional decomposition is a technique that helps the business analyst understand the scope of the work by breaking down the scope into smaller work products. Functional decomposition i s the process of identifying the high-level functions or capabilities of a solution and then dividing them into lower-level functions or sub-functions. This technique helps to create a hierarchical structure of the solution scope, which can be used to defi ne the requirements, design the solution, and plan the project. Functional decomposition can also help to identify the dependencies, interfaces, and risks among the functions or sub-functions of the solution.  References :

BABOK Guide v3 , section 10.25, page 512-513

Solution Scope – An Insight , section 1.2, paragraph 2

Software Project Scope | Solution Scope in Business Analysis , paragraph 2

Benchmarking is the process of comparing the performance or quality of a product, service, or process against a standard or best practice. Bob and Susan are benchmarking the materials by testing them and measuring the results to see how they compare to each other. This will help them select the best material for their project.

References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 6: Enterprise Analysis, page 217.

BABOK® Guide , Version 3, Section 3.4: Strategy Analysis, page 50.

 A test plan is a document that describes the scope, objectives, strategy, and activities of testing a software product or system. A test plan is mandatory in most software development projects because it ensures that the software meets the quality standards and requirements of the stakeholders. A test plan also helps to identify and mitigate the risks, def ects, and issues that may affect the software functionality, performance, usability, and security. A test plan is different from a communication management plan, which is a document that describes how the project information will be communicated to the sta keholders. A test plan is also different from a disaster recovery plan, which is a document that describes how the project will resume its operations in the event of a disaster or emergency. A test plan is not a procurement plan, which is a document that d escribes how the project will acquire the goods and services needed from external sources.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 9: Solution Assessment and Validation, page 329-330.

How to write a software requirement document (with template) , paragraph 6

These testing methods should be mandatory for any software , paragraph 1

Software Testing Plan - Tutorialspoint , paragraph 1

A class model is a technique to represent the structure and behavior of the entities within a solution domain. It shows the attributes, operations, and relationships of the classes that define the entities. A class is a category or type of entity that has common characteristics and can perform certain functions. A class model helps to identify the entities, their properties, their behaviors, and their interactions for a solution. Entity Relationship is a technique to represent the data a nd information requirements of a solution. It shows the entities, attributes, and relationships of the data and information. An entity is a thing or object of interest that can be uniquely identified and has attributes that describe its properties. An enti ty relationship model helps to identify the data and information, their characteristics, their associations, and their constraints for a solution. Data dictionary is a technique to define and document the data and information elements of a solution. It pro vides a detailed description of each data and information element, such as its name, definition, format, type, source, owner, and usage. A data dictionary helps to standardize and clarify the data and information, their meaning, their structure, and their quality for a solution. CRUD matrix is a technique to analyze the alignment of the data and information elements with the business processes or functions of a solution. It shows the data and information elements and the business processes or functions that create, read, update, or delete them. A CRUD matrix helps to identify the data and information, their lifecycle, their dependencies, and their gaps for a solution.  References :  Class Model - iiba.org ,  Entity Relationship - iiba.org ,  D ata Dictionary - iiba.org ,  CRUD Matrix - iiba.org

 Voting is a technique of requirements prioritization that involves asking the stakeholders to express their preferences for the requirements using various methods, such as ranking, rating, or allocating points or money. Voting helps to achieve consensus and alignment among the stakeholders and to identify the most important and valuable requirements. In this scenario, the business analyst is using a voting method that assigns play money to the requirements, which reflects the relative importance and benefit of each requirement. The requirements with the highest amount of play money are prioritized over the ones with lower amounts.

References :

BABOK® Guide , p. 55, 376-377

CBAP / CCBA Certified Business Analysis Study Guide , p. 165-166

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 2, Week 1, Video: “Requirements Prioritization”

 A business case is a document that provides justification for undertaking a project, programme or portfolio. It evaluates the benefit, cost and risk of alternative options and provides a rationale for the preferred solution. The purpose of the business case is to communicate the value of the solution to the organization and help the decision-makers decide whether to approve the project or not. The business case should include the following elements:

Executive summary: A brief overview of the problem, opportunity, solution, benefits, costs, risks and recommendations.

Introduction: A description of the background, context, scope and objectives of the project.

Analysis: A detailed analysis of the current state, future state, gap, options, criteria, assumptions and constraints.

Evaluation: A comparison of the options based on the criteria, such as financial, strategic, operational, technical, social and environmental factors.

Recommendation: A clear statement of the preferred option and the reasons for choosing it over the others.

Implementation: A description of the implementation plan, including the schedule, resources, roles, responsibilities, governance, change management and risk management.

Appendices: Any supporting information, such as data, calculations, charts, diagrams, references, etc.

References :

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Approach, Task 3.4.3: Define Business Analysis P rocess, Technique 3.4.3.1: Decision Analysis, p. 66-67.

What is business case?  | APM

How to Write a Business Case: Template & Examples  | Adobe Workfront

 An entity relationship diagram (ERD) is a graphical representation of how entities and relationships are organized in a database or a system. An ERD consists of three main components: entities, attributes, and relationships. Entities are the objects or concepts that store data, such as customers, products, or orders. Attributes are the properties or characteristics of entities, such as name, price, or quantity. Relation ships are the associations or connections between entities, such as one-to-one, one-to-many, or many-to-many. Forks are not a component of an ERD, but rather a symbol used to represent a relationship type. A fork indicates that a relationship is either one -to-many or many-to-many, depending on the direction of the fork. For example, a fork pointing from an entity A to an entity B means that one instance of A can be related to many instances of B, while a fork pointing from an entity B to an entity A means t hat many instances of B can be related to one instance of A.  References :

ER Diagram (ERD) - Definition & Overview | Lucidchart , paragraph 1-2

A Guide to the Entity Relationship Diagram (ERD) - Database Star , paragraph 1-2

ERD Templates | ER Diagram Examples | Moqups , paragraph 1

What is an Entity Relationship (ER) Diagram - Creately , paragraph 1

Components of an ER Diagram - TAE - Tutoria l And Example , paragraph 1-2

Interface analysis is a technique of identifying and specifying the points of interactio n between a solution and its external entities, such as other systems, devices, or users. Interface analysis can help to determine the interoperability of the software, the databases, and the web application by defining the requirements for the data exchan ge, communication, and integration among them. Interface analysis can also help to identify any potential issues, risks, or dependencies related to the interfaces.  References :  BABOK Guide v3 , page 128;  CBAP / CCBA Certified Business Analysis Study Guide , page 184.

Writing the business case is a process of documenting the justification for initiating a project or a solution, based on the estimated costs, benefits, and risks. The inputs to this process are the business need, the assumptions and constraints, the stakeholder concerns, and the solution scope. Th e business need defines the problem or opportunity that the project or solution will address. The assumptions and constraints are the factors that affect the feasibility and viability of the project or solution. The stakeholder concerns are the expectation s, issues, or interests of the stakeholders that may influence the project or solution. The solution scope defines the features and functions of the product or service that will meet the business need and the stakeholder concerns. Requirements verification is not an input to this process, but rather an output of the verify requirements process, which is part of the requirements analysis and design definition knowledge area.  References :  BABOK Guide v3 , page 25;  CBAP / CCBA Certified Business Analysis Study Guide , page 69.

 Data flow diagramming is a technique that shows how data moves through a system, from external entities, through processes, to data stores. Data flow diagrams can be used to model the current state or the desired state of a system, and to identify gaps or redundancies in data processing. Data flow diagrams can also be decomposed to lower levels of detail to show the sub-process es and data elements involved in each function. Functional decomposition, work decomposition, and organization modeling are different techniques that can be used to break down a system, a project, or an organization into smaller components, but they do not focus on the data movement.  References :

BABOK® Guide , p. 10, 98-99

CBAP / CCBA Certified Business Analysis Study Guide , p. 240-241

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 2, Week 2, Video: “Data Flow Diagrams”

Prioritizing requirements is a process of determining the relative importance and urgency of the requirements based on the criteria and preferences of the stakeholders. Prioritizing requirements can help to allocate resources, manage scope, and resolve conflicts. One of the factors that can affect the prioritization of requirements is the dependency, which means that one requirement must be implemented before another requirement can be implemented. In this case, you are correct to move one of the requirements higher in the prioritization because it is needed to be implemented before some of the more important requirements are done. This way, you can ensure that the dependency is satisfied and that the project can deliver the expected value. Ra lph is incorrect to rank the requirements based on their level of difficulty, as this is not a relevant criterion for prioritization. The level of difficulty can be considered in the estimation and planning of the project, but not in the prioritization of the requirements.  References :  BABOK Guide v3 , page 52;  CBAP / CCBA Certified Business Analysis Study Guide , page 160.

Assessing capability gaps is a task of enterprise analysis that involves analyzing the current state of the organization and comparing it with the desired future state. The purpose of this task is to identify the new capabilities that the organization needs to acquire or enhance in order to meet the business need and achieve the organizational goals and objectives. These new capabilities can be related to processes, systems, people, or resources. As sessing capability gaps can help to determine the scope and feasibility of the solution, as well as the risks and benefits associated with it.  References :  BABOK G uide v3 , page 25;  CBAP / CCBA Certified Business Analysis Study Guide , page 69.

 A statement of work (SOW) is a narrative description of the work required for the project. It includes the project objectives, scope, deliverables, schedule, budget, quality standards, and acceptance criteria. It also defines the roles and responsibilities of the project team and the client, and the terms and conditions of the contract.  A SOW is a fo rmal document that establishes the agreement between the project provider and the project customer, and that guides the project execution and control 1 2 .

The other options are not correct. A. A contract work breakdown structure (CWBS) is a hierarchical decomposition of the contract deliverables into smaller and manageable components.  It helps to define the scope, cost, and schedule of the contract, and to monitor and report the contract performance 3 . B. A work breakdown structure (WBS) is a hierarchical decomposition of the project work into smaller and manageable components.  It helps to de fine the scope, cost, and schedule of the project, and to assign the work packages to the project team 4 . C. A contract statement of work (CSOW) is a document that describes the work to be performed by a contractor or a vendor under a contract.  It is similar to a SOW, but it is more specific and detailed, and it is used for procurement purposes 5 .  References :

What is a Statement of Work (SOW)? - Definiti on from WhatIs.com

Statement of Work: Definition & Examples - ProjectManager

Contract Work Breakdown Structure (CWBS) - AcqNotes

Work Breakdown Structure (WBS) - Project Management Institute

Contract Statement of Work (CSOW) - AcqNotes

The question asks about the time required to achieve the desired sales and retention goals, given the current rate of increase. To answer this question, we need to use the formula for compound growth rate, which is:

Final value = Initial value x (1 + Growth rate) ^ Number of periods

We can apply this formula to both sales and retention, using the given values and solving for the number of periods. For sales, we have:

1.15 = 1 x (1 + 0.06) ^ Number of periods

Taking the natural logarithm of both sides, we get:

ln(1.15) = ln(1 + 0.06) x Number of periods

Dividing by ln(1 + 0.06), we get:

Number of periods = ln(1.15) / ln(1 + 0.06)

Using a calculator, we get:

Number of periods = 2.29

Since each period is six months, we multiply by 6 to get the number of months:

Number of months = 2.29 x 6

Number of months = 13.74

Rounding up to the nearest whole number, we get:

Number of months = 14

Therefore, it will take 14 months, or about 18 months, to achieve the sales goal.

For retention, we have:

1.1 = 1 x (1 + 0.05) ^ Number of periods

Repeating the same steps as above, we get:

Number of periods = ln(1.1) / ln(1 + 0.05)

Number of periods = 1.86

Number of months = 1.86 x 6

Number of months = 11.16

Rounding up to the nearest whole number, we get:

Number of months = 12

Therefore, it will take 12 months, or 1 year, to achieve the retention goal.

References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 5: So lution Assessment and Validation, p. 211-212

Certified Business Analysis Professional™ (CBAP®) Specialization , Course 4: Business Analysis: Solution Eva luation, Week 2: Solution Performance Assessment, Video: Solution Performance Metrics

Compound Growth Rate Calculator

Problem tracking is not a technique for conducting elicitation, but rather a technique for managing requirements. Problem tracking is used to identify, document, and resolve issues that arise during the business analysis process. Problem tracking helps to ensure the quality and validity of the requirements and the solutions.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 4: Elicitation and Collaboration, p. 177

BABOK® Guide , Section 4.2: Conduct Elicitation, p. 106-107

BABOK® Guide , Sectio n 4.6: Manage Requirements, p. 121-122

Surveys are a type of requirements elicitation technique that involves sending a set of questions or statements to a large group of stakeholders and collecting their responses. Surveys can be conducted using various modes, such as online, email, phone, or paper. Surveys are useful for capturing the feelings and thoughts of a large and diverse population of stakeholders, identifying the common needs and wants of the majority, and analyzing the trends and patterns of the responses. Surveys can also help to gather quantitative and qualitative data, measure the level of satisfaction or dissatisfac tion, and obtain feedback on the existing or proposed solution. Surveys are different from interviews, which are a type of requirements elicitation technique that involves asking questions and documenting the responses from a single person or a small group of people. Interviews are useful for exploring the in-depth and detailed information from the key stakeholders, probing deeper into their needs and expectations, and clarifying any ambiguities or inconsistencies. Interviews can also help to establish rapp ort and trust with the stakeholders, observe their non-verbal cues, and tailor the questions according to the context and situation. Surveys are also different from trend analysis, which is a type of requirements elicitation technique that involves examini ng the historical or current data and information to identify the changes and developments over time. Trend analysis can help to understand the past and present performance and behavior of the system or the process, predict the future outcomes and scenario s, and anticipate the opportunities and threats. Trend analysis can also help to validate and verify the requirements, evaluate the feasibility and viability of the solution, and support the decision making and planning. Surveys are not focus groups, which are a type of requirements elicitation technique that involves inviting a group of stakeholders to a moderated discussion on a specific topic or issue. Focus groups can help to generate a large number of ideas and opinions, find solutions for a specific p roblem, and stimulate the interaction and debate among the participants. Focus groups can also help to gain insights and perspectives from different stakeholders, identify the areas of agreement or disagreement, and foster a sense of involvement and owners hip.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 4: Elicitation and Collaboration, page 180-181.

Top 10 Most Common Requirements Elicitation Techniques , paragraph 9

Software Engineering | Requirements Elicitation - GeeksforGeeks , paragraph 6

Elicitation Technique Guide | Info-Tech Research Group , paragraph 1

Requirements Elicitation Technique (RET) : 10+ Effective RET - Skillcubator , paragraph 4

The lead BA should implement key performance measures to identify areas of improvement, as this is the most effective way to assess the current state of the business analysis practices and the value they deliver to the organization. Key performance measures are quantifiable indicators that reflect the critical success factors of a project, process, or activity. They can be used to evaluate the quality, efficiency, and effectiveness of the business analysis deliverables and outcomes, as well as the satisfaction and engagement of the stakeholders. By measuring and analyzing the key performance indicators, the lead BA can identify the gaps, issues, and opportunities for improvement in the business analysis practices, and propose solutions to enhance them.

The other options are not the best actions to take. A BA time tracking system may help to monitor the effort and duration of the business analysis activities, but it does not provide information on the quality and value of the deliverables and outcomes. Templates for BAs to use may help to standardize and document the business analysis deliverables, but they do not ensure the alignment and agreement of the requirements and the stakeholder needs. Workload plans of the BA may help to manage the resources and priorities of the business analysis activities, but they do not measure the impact and benefits of the business analysis outcomes.  References : The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 2: Business Analysis Planning and Monitoring, p. 40-41, 48-49, 51-52.

Business Analysis for Practitioners: A Practice Guide , Chapter 4: Requirements Life Cycle Management, p. 93-94, 97-98.

The BA noticed that only 30% of trips have their orders ready for loading when a truck arrives, meaning 70% of the time, trucks are waiting an extra hour. If each truck can make two trips a day and there are 12 trucks, that’s a total of 24 trips per day. With 70% of these trips experiencing downtime, that’s approximately 17 trips (16.8 rounded up). Since each downtime lasts an hour, this results in approximately 17 hours lost to downtime each day.

However, the question asks if trucks are the only constraint - meaning we should consider the maximum capacity of trucks which is not being fully utilized due to other constraints (like workers or tallyers). In this case, we need to calculate how many more hours would be lost if the trucks were operating at full capacity.

The total capacity tons/day for workers is 89 tons/day and for tallyers is 74 tons/day which are less than the truck’s capacity of 101 tons/day. So, we consider worker’s capacity as a constraint here.

Now let’s calculate how many more trips could be made if there were no constraints from workers or tallyers:

101 (truck’s total daily tonnage capacity) /89 (worker’s total daily tonnage capacity) = approximately1.13

So if there were no constraints from workers or tallyers, each truck could make approximately one additional trip per day.

Now let’s add these potential additional trips to our original calculation:

17 (original downtime hours) +3 (additional potential downtime hours due to increased number of trips) =20 total downtime hours

So if trucks were the only constraint and all other factors allowed them to operate at full capacity, approximately20 hours would be lost due to this downtime.  References : This answer is inferred based on general business analysis principles as I need access to specific CBAP learning documents or resources for precise referenc ing and verification according to CBAP standards.

The lead BA is trying to improve the business analysis practices by finding out the root causes of the problems and inefficiencies in the current state. By measuring the time spent on planned and unplanned activities, the lead BA can identify the typical missing or wasteful activities that are affecting the quality and timeliness of the d eliverables. For example, the lead BA may discover that the BAs are spending too much time on rework, clarifications, or scope changes due to poor elicitation, validation, or prioritization techniques. The lead BA can then propose solutions to address thes e issues and enhance the business analysis performance and value.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 2: Business Analysis Planning and Monitoring, page 57

Senior Business Analysis Certification CBAP® | IIBA® , Business Analysis Planning and Monitoring, page 5

 Governance is the approach that contains a suitable set of attributes for specifying requirements. Governance refers to the set of policies, processes, standards, roles, and responsibilities that guide, monitor, and control the conduct of business analysis activities. Governance helps to ensure that the requirements are aligned with the business objectives, stakeholder needs, and quality criteria. Governance also helps to manage the changes, risks, issues, and dependencies related to the requirements. Some of the attributes that can be specified for requirements under governance are:

Requirement type (e.g., functional, non-functional, business, user, etc.)

Requirement status (e.g., proposed, approved, implemented, verified, etc.)

Requirement priority (e.g., mandatory, high, medium, low, etc.)

Requirement source (e.g., stakeholder, document, regulation, etc.)

Requirement owner (e.g., the person or role responsible for the requirement)

Requirement version (e.g., the number or identifier of the requirement revision)

Requirement traceability (e.g., the links between the requirement and other related requirements, deliverables, tests, etc.)

These attributes help to define, organize, communicate, and manage the requirements throughout the business analysis life cycle.

References :

[BABOK Guide v3], Section 2.5: Governance, p. 28-30

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Ch apter 2: Business Analysis Planning and Monitoring, p. 55-56

Certified Business Analysis Professional™ (CBAP®) Specialization , Course 1: Business Analysis: Planning and Monitoring , Week 2: Plan Business Analysis Governance, Video: Introduction to Business Analysis Governance

The BA can alleviate the concerns of the stakeholders in domain 2 by presenting a model applicab le for them. A model is a representation of a concept or system that is used to communicate, analyze, or design. A model can help the BA to convey complex or abstract information in a clear and concise way, using the appropriate level of detail, notation, and terminology for the audience. A model can also help the BA to elicit feedback, validate understanding, and resolve issues or conflicts. A survey, an estimation, or a backlog are not the best options to alleviate the concerns of the stakeholders in doma in 2, because they are either too general, too specific, or too technical, and they do not address the root cause of the problem, which is the lack of clarity and relevance of the presentation.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 7: Requirements Analysis and Design Definition, page 279

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 7: Requirements Analysis and Design Definition, section 7.5: Specify and Model Requirements, page 133

Business Analysis Professional Resources , IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Skillsoft Book, Chapter 7: Requirements Analy sis and Design Definition, page 279

 Collaborative games are a technique that can be used to elic it requirements in a workshop setting. They involve engaging the participants in structured activities that encourage creativity, collaboration, and consensus. Collaborative games can help to avoid disrupting the workshop by creating a positive and product ive atmosphere, reducing the potential for conflict, and increasing the buy-in and ownership of the requirements. Some examples of collaborative games are brainstorming, affinity diagramming, storyboarding, and prioritization games.  References :

Business Analysis Body of Knowledge (BABOK) Guide , section 10.18, Collaborative Games

CBA P / CCBA Certified Business Analysis Study Guide, 2nd Edition , chapter 6, Elicitation and Collaboration, page 223-224

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , chapter 10, Review Questions, question 10.14, page 440

Inf ormation architecture is the structure and organization of information within a system or process 1 .  It helps to ensure that the process models relate to each other by defining the relationships, dependencies, and interactions among the data, information, and knowledge that are used or produced by the processes 2 .  Information architecture also helps to align the process models with the business goals, objectives, and requirements 3 . 

 The BA is facing a situation where the stakeholders are not cooperating or engaged in the business analysis activities. To resolve this issue, the BA needs to use the competencies of negotiation, conflict resolution, and effective communication. Negotiation is the ability to reach an agreement that is acceptable to all parties involved. Conflict resolut ion is the ability to manage and resolve disagreements or disputes among stakeholders. Effective communication is the ability to convey information clearly and accurately, and to listen and respond appropriately to the needs and concerns of others. These c ompetencies will help the BA to understand the root causes of the stakeholders’ resistance, address their expectations and interests, and persuade them to participate and collaborate in the business analysis process.  References :  CBAP Competencies ,  CBAP Handbook ,  CBAP Study Guide

 The user interface is the part of a system that allows the actual users to interact with one another, the system, or data moved between two users. The user interface is the means by which the users can input, view, manipulate , or output information through the system. The user interface can be graphical, textual, auditory, tactile, or a combination of these. The user interface is an important aspect of the user experience and usability of the system. The user interface should be designed to meet the user needs, preferences, and expectations, as well as the system requirements and constraints.  References :  IIBA BABOK Guide v3 , section 9.1.2, page 326;  CBAP / CCBA Certified Business Analysis Study Guide , chapter 7, page 251;  CBAP Exam Questions - Institute i4 , question 241.

 A focus group is a technique for eliciting information from a group of stakehol ders who have knowledge or experience on a specific topic. It involves asking open-ended questions, facilitating discussions, and capturing feedback. A focus group can help the BA to gather information about the decision making authorities within the compa ny by engaging with the relevant stakeholders, such as project sponsors, managers, directors, or board members. The BA can use the focus group to understand the roles, responsibilities, and expectations of the decision makers, as well as the criteria, meth ods, and processes they use to make decisions. The other options are not suitable techniques for gathering this information. A market analysis is a technique for researching and analyzing the external factors that affect the demand, supply, and opportuniti es for a product, service, or solution. A survey is a technique for collecting quantitative or qualitative data from a large number of respondents using a predefined set of questions. A cost benefit analysis is a technique for comparing the costs and benef its of alternative solutions or courses of action.  References :  CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , C hapter 5: Elicitation and Collaboration, p. 164-165, 168-169, 171-172;  A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3 , Chapter 4: Eli citation and Collaboration, Section 4.2: Prepare for Elicitation, p. 94-95; Chapter 10: Techniques, Section 10.15: Focus Groups, p. 378-379.

 Milestone funding is an approach where the project is funded for enough capital to reach the next milestone, which is a predefined point in the project where some deliverables are completed or some criteria are met. Milestone funding helps to reduce the risk of investing too much money in a project that may not del iver the expected value or benefits. It also helps to monitor the progress and performance of the project and ensure that the project is aligned with the business objectives and stakeholder expectations. Milestone funding is a common practice in agile proj ects, where the project is divided into short iterations that deliver incremental value and feedback.  References :  CBAP / CCBA Certified Business Analysis Study Guide , chapter 5, page 229;  CBAP (Certified Business Analysis Professional): 230+ Exam Practice Questions with Detail Explanations and Case Study Based Questions , question 230.

 A milestone is a term used to describe a major deliverable or key event in the projec t used to measure project progress. A milestone is a significant point in time that marks the completion of a specific scope of work or a specific objective. A milestone can also be a checkpoint that indicates the readiness of the project to move to the ne xt phase or stage. A milestone can be used to monitor and control the project schedule, budget, quality, and risks. A milestone can also be used to communicate the project status and achievements to the stakeholders and sponsors. A milestone is usually ass ociated with a specific date and has no duration.  References :  IIBA BABOK Guide v3 , section 5.1.3, page 163;  CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , chapter 6, page 233;  CBAP Sample Questions , question 233 .

Decision analysis is a technique for identifying and evaluating the possible options for a given problem or situation.  It involves defining the criteria, alternatives, and consequences of each option, and applying a decision-making method to select the best option 1 2 . Decision analysis can be used for assessing and recommending solutions that fit an organization’s need for a new third-party sales tool, as it can help to compare the features, benefits, costs, and risks of differe nt vendors or products. The other options are not techniques for identifying suitable options, but rather tools or methods for other purposes.  A balanced scorecard is a tool for measuring and managing the performance of an organization or a solution 3 .  A vendor assessment is a method for evaluating the capabilities and suitability of a potential vendor or supplier 4 .  A process an alysis is a technique for understanding and improving the current or future state of a business process

The sorting stage should be assessed as the most likely to increase process inefficiencies, because it is a manual, error-prone, and time-consuming task that depends on the operator’s accuracy and speed. The sorting stage requires the operator to read the printed address on each package and place it in the correct delivery box, which may involve multipl e steps, movements, and decisions. The sorting stage may also introduce delays, bottlenecks, or rework if the operator makes mistakes or cannot keep up with the volume of packages. The loading, packaging, and printing stages are less likely to increase pro cess inefficiencies, because they are either automated or simpler tasks that involve fewer steps, movements, and decisions. The loading stage only requires the operator to load 100 cards after an alarm is raised, which is a straightforward and infrequent t ask. The packaging and printing stages are automated and do not require any human intervention, which reduces the risk of errors and delays.  References :

CBAP / CCBA Certifi ed Business Analysis Study Guide, 2nd Edition , Chapter 6: Strategy Analysis, page 248

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 5: Str ategy Analysis, section 5.2: Analyze Current State, page 95

Business Analysis Professional Resources , IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Skillsoft Book, Chapter 6: Strategy Analysis, page 248

 The medium i s the component of the communication model that is responsible for transferring the message between two or more entities. The medium is the channel or the tool that is used to transmit the message from the sender to the receiver. The medium can be verbal, written, visual, or a combination of these. The medium can also be electronic, such as email, phone, or video conference, or physical, such as paper, board, or face-to-face meeting. The medium acts as a translator by converting the message into a form that can be understood by the receiver. The medium also influences the effectiveness and efficiency of the communication, as different mediums have different advantages and disadvantages, such as speed, cost, feedback, and noise.  References :  IIBA BABOK Guide v3 , section 2.2.2.3, page 25;  CBAP / CCBA Certified Business Analysis Study Guide , chapter 6, page 236;  CBAP Business Analyst Exam Prep | Practice Quiz , question 256.

 Risk Analysis and Management is a technique that involves identifying, assessing, and treating the uncertainties and potential negative impacts that may affect the requirement or the solution. Risk Analysis and Management can help the BA to identify scenarios that would alter the benefit delivered by a requirement, because it can help the BA to quantify and prioritize the risks, determine the app ropriate responses and mitigation strategies, and monitor and control the risk exposure and outcomes. Risk Analysis and Management can also help the BA to communicate and report the risk status and issues to the stakeholders and the organization, and to en sure that the requirement delivers the expected value and benefit. Metrics and Key Performance Indicators, Data Modeling, or Document Analysis are not the best options for identifying scenarios that would alter the benefit delivered by a requirement, becau se they are either too specific, too general, or not directly related to the risk analysis and management process.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 8: Solution Evaluation, page 346

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 8: Solution Evaluation, sectio n 8.4: Assess Solution Limitations, page 158

Business Analysis Professional Resources , IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Skillsoft Book, Chapter 8: Solution Evaluation, page 346

 The timing and frequency of collaboration are aspects that should be taken into account when working on a stakeholder collaboration plan. This is because the timing and frequency of collaboration affect the availability, engagement, and satisfaction of the stakeholders, as well as the quality and efficiency of the business analysis work. The BA should consider the stakeholder preferences, expectations, and constraints, as well as the project schedule, scope, and complexity, when determining the optimal timing and frequency of collaboration. The BA should also ensure that the collaboration act ivities are aligned with the business analysis plan and the stakeholder communication plan. Collaboration skills of BA, solution design, or business governance plan are not the best options for the aspects that should be taken into account, because they ar e either irrelevant, inaccurate, or not the root cause of the problem.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 4: Elicitation and Collaboration, page 167

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 4: Elicitation and Collaboration, section 4.2: Conduct Elicitati on, page 77

Business Analysis Professional Resources , IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Skillsoft Book, Chapter 4: Elicitation and Collaboration, page 167

 The medium is the portion of the communications model that could be defined as the translator. The medium is the channel or the tool that is used to transmit the message from the sender to the receiver. The medium can be verbal, written, visual, or a combination of these. The medium can also be electronic, such as email, phone, or video conference, or physical, such as paper, board, or face-to-face meeting. The medium acts as a translator by converting the message into a form that can be understood by the receiver. The medium also influences the effectiveness and e fficiency of the communication, as different mediums have different advantages and disadvantages, such as speed, cost, feedback, and noise.  References :  IIBA BABOK Guide v3 , section 2.2.2.3, page 25;  CBAP / CCBA Certified Business Analysis Study Guide , chapter 6, page 236;  Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam , question 251.

A process diagram is a kind of asset that the BA should provide to fully specify the approval requirement. A process diagram is a visual representation of the sequence of activities and decisions involved in a business process or a system. It shows the inputs, out puts, roles, tasks, events, conditions, and flows that occur in each step of the process. A process diagram can help the BA specify the approval requirement by showing:

Which incident-related activities require approval and confirmation

Who are the authorized personnel for each activity

What are the criteria and triggers for approval and confirmation

What are the outcomes and exceptions of approval and confirmation

A process diagram can also help the EA compare the existing application and the new application by showing the similarities and differences in the process flows, data sources, and user interfaces.

References :

[BABOK Guide v3], Section 10.28: Process Modeling, p. 410-412

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 4: Requirements Elicitation and Collaboration, p. 161-163

Certified Business Analysis Professional™ (CBAP®) Specialization , Course 2: Business Analysis: Requirements Elicitation and Analysis, Week 4: Requirements Analysis Techniques, Video: Process Modeling

Option D shows the correct use of the  include  relationship between the three use cases. This means that the “Pass a two-factor authentication” use case is a mandatory part of both the “Change system parameters” and the “Setup new supervisor” use cases, and it always occurs whenever either of them is executed. The arrow points from the base use case to the included use case, as per the UML notation. Option C is incorrect because it uses the  protect  relationship, which is a non-standard extension of the UML notation. It indicates that the “Pass a two-factor authentication” use case is a s ecurity requirement for the other two use cases, but it does not specify how or when it is executed. Options A and B are incorrect because they use the  extend  relationship, which means that the “Pass a two-factor authentication” use case is an optional ext ension of the other two use cases, and it only occurs under certain conditions. This does not reflect the requirement that the two-factor authentication is mandatory for both functions.  References :

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3], Chapter 10: Techniques, pp. 424-425.

[UML 2.5 Specification], Chapter 18: Use Cases, pp. 637-638.

The driver’s average throughput is 0.6 tons/hour. To deliver 100 tons of merchandise, the total hours required would be ( \frac{100 \text{ tons}}{0.6 \text { tons/hour}} = 166.67 \text{ hours} ). If there are 15 drivers, then each driver would need to work ( \frac{166.67 \text{ hours}}{15 \text { drivers}} = 11.11 \text { hours/driver} ). However, since the options provided do not include 11, and it is not po ssible for a driver to work a fraction of an hour in this context, we round down to the nearest whole number which gives us option B: 9 hours per day.  References : This answer and explanation are inferred from general mathematical calculations as specific r eferences from Business Analysis Professional (CBAP) Learning documents or resources were not provided.

 In this scenario, the distribut or is under pressure to fully meet the year-round market demand in order to stay in business. The primary objective is not directly related to making more profit, defeating competitors, or stabilizing its performance but rather ensuring that customer order s are fulfilled even during peak demand periods. This aligns with one of the key aspects of business analysis - understanding and prioritizing the needs and expectations of stakeholders (in this case, customers) to deliver value.  References : Business Analy sis Professional (CBAP) Learning documents or resources available at  1  and  2

 A focus group is a technique that involves organizing a discussion with a small group of stakeholders to understand their perceived value and expectations of a set of requirements and design options. A focus group can help the BA to estimate the potential value delivered by the solution, as it allows the BA to collect feedback, opinions, preferences, and attitudes from the stakeholders in a structured and interactive way. A focus group can also help the BA to identi fy and resolve any conflicts or issues among the stakeholders, and to build consensus and buy-in for the solution. The other options are not the best techniques for this purpose, as they are more focused on generating and evaluating ideas, collecting infor mation from a large number of stakeholders, or interviewing stakeholders individually or in a group.  References :  CBAP Handbook ,  CBAP Study Guide ,  BABOK Guide

According to the CBAP competencies, one of the skills required for business analysis planning and monitoring is to guide practice in performing stakeholder analysi s 1 .  Stakeholder analysis is the process of identifying and assessing the needs, inte rests, and influence of stakeholders on a project or initiative 2 .  One of the outputs of stakeholder analysis is a stakeholder list, which identifies the key stakeholders and their roles, responsibilities, and expectations 3 .  A stakeholder list can also include information on the potential risks and issues that may arise from stakeholder in volvement or lack thereof 4 . Therefore, developing a risk plan to anticipate negative behavior from the Director of Human Resources is a valid act ivity that is included in performing a stakeholder analysis. This can help the team to mitigate the impact of the Director’s bitterness and resistance on the project’s success.

The other options are not included in performing a stakeholder analysis. Compar ing the expertise of the Director of Human Resources to other stakeholders is not relevant to the stakeholder analysis process, as it does not help to understand the Director’s needs, interests, or influence. Recommending excluding the Director of Human Re sources as a stakeholder is not a good practice, as it may create more conflict and resentment, and ignore the Director’s legitimate role and authority in the project. Implementing all of the Director of Human Resources suggestions to relieve tension is no t a realistic or effective strategy, as it may compromise the quality and feasibility of the project, and disregard the needs and interests of other stakeholders.  References :

1 : CBAP Competencies - International Institute of Business Analysis

2 : BABOK Guide v3, Section 2.2.2: Conduct Stakeholder Analysis

3 : BABOK Guide v3, Section 2.2.2.3: Outputs

4 : CBAP / CCBA Certified Business Analysis Study Guide, Chapter 3: Business Analysis Planning and Monitoring, p. 83

 Option B is both unambiguous and testable because it provides a specific color code (HEX #0000FF) that can be easily identified, verified, and tested. It leaves no room for interpretation or ambiguity, unlike the other options. A specific HEX code ensures that the exact shade of blue is understood and can be implemented consistently across different displays or prints.  References : T he answer is verified as per the Business Analysis Professional (CBAP) Learning documents or resources available on IIBA’s official website. Some of the relevant sources are:

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

Business Analysis Competency Model

Business Analysis for Practitioners: A Practice Guide

A data model is a diagram type that can describe the association between the subscriber, the medical plan, and the participating service providers. A data model is a visual representation of the data entities, attributes, and relationships involved in a business domain or a system. It shows the structure, constraints, and rules that govern the data and how they are stored, accessed, and manipulated. A data model can help the business analyst specify the data requirements for the mobile application platform and how the data is integrated from different sources. A data model can also help the enterprise architect compare the existing solution and the new solution by showing the similarities and differences in the data entities, attributes, and relationships.

References :

[BABOK Guide v3], Section 10.9: Data Modeling, p. 358-360

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 6: Requirements Analysis and Design Definition, p. 221-223

Certified Business Analysis Professional™ (CBAP®) Specialization , Course 2: Business Analysis: Requirements Elicitation and Analysis, Week 4: Requirements Analysis Techniques, Video: Data Modeling

Business rules analysis is a business analysis technique that involves identifying, analyzing, and documenting the rules that govern how an organization operates and makes decisions. Business rules analysis can help an organization to adapt to the change economy, new technologies, and an increase in competition by ensuring that the rules are aligned with the organizational goals and objectives, and that they are consistent, transparent, and flexible. Business rules analysis can also help to identify any gaps, conflicts, or redundancies in the existing rules, and to propose new or revised rules that can improve the organizational performance and efficiency.  References :  BABOK Guide v3 , page 142;  CBAP / CCBA Certified Business Analysis Study Guide , page 191.

Verification is the process of evaluating the stated requirements to ensure that they are well-formed, consistent, complete, correct, and aligned with the organizational standards for business analysis. Verification is usually done by the BA or a peer reviewer before presenting the requirements to the stakeholders for validation or acceptance. Verification helps to ensure the qu ality and accuracy of the requirements, and to avoid errors, ambiguities, or misunderstandings. The other options are not the states that the BA is attempting to move the requirements into, as they are more related to the evaluation of the requirements aga inst the business need, stakeholder expectations, or solution design.  References :  CBAP Handbook ,  CBAP Study Guide ,  BABOK Guide

The next task that the BA needs to do to complete the gap analysis is to define the future state capabilities. This means that the BA needs to describe the desired outcomes, benefits, and functions of the new syst ems and how they will support the business needs and stakeholder requirements. Defining the future state capabilities will help the BA to compare them with the current state of systems and identify the gaps, opportunities, and changes needed to achieve the future state. Identifying performance measures, categorizing risk factors, or selecting the stakeholder engagement approach are not the next tasks for completing the gap analysis, because they are either part of the current state analysis or the subsequen t tasks after the gap analysis.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 6: Strategy Analysis, page 254

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 5: Strategy Analysis, section 5.3: Define Future State, page 99

Business Analysis Professional Resources , IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Skillsoft Book, Chapter 6: Strategy Analysis, page 254

The planning stage of a project defines the number of risks and opportunities, including intense planning and anticipation of risk events. The planning stage is the process of establishing the scope, objectives, approach, and deliverables of the project. It involves defining the project requirements, assumptions, constraints, and dependencies. It also involves developing the project management plan, which includes the subsidiary plans for scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder management. The planning stage helps to identify and analyze the risks and opportunities that may affect the project, and to plan the approp riate responses and strategies to address them.  The planning stage also helps to align the expectations and involvement of the project stakeholders, and to obtain their approval and commitment for the project 1 2 . The executing stage of a project is the process of performing the work and producing the deliverables of the project. It involves implemen ting the project management plan, managing the project resources, executing the project activities and tasks, and creating the project outputs and outcomes. The executing stage helps to monitor and control the risks and opportunities that occur during the project, and to implement the planned responses and strategies to deal with them.  The executing stage also helps to communicate and collaborate with the project stakeholders, and to manage their expectations and satisfaction 1 2 . The initiation stage of a project is the process of authorizing and launching the project. It involves identifying the problem or opportunity that the project intends to address, and defining the purpose, objectives, scope, and ju stification of the project. It also involves developing the project charter, which is a document that formally approves and initiates the project. The initiation stage helps to identify and assess the high-level risks and opportunities that are associated with the project, and to determine the feasibility and viability of the project.  The initiation stage also helps to identify and engage the key proj ect stakeholders, and to obtain their support and endorsement for the project 1 2 . The closing stage of a project is the process of finalizing and terminating the project. It involves verifying and validating the project deliverables, evaluating and documenting the project performance, and closing the project c ontracts and accounts. It also involves developing the project closure report, which is a document that summarizes and communicates the project results and lessons learned. The closing stage helps to identify and resolve the remaining risks and opportuniti es that are related to the project, and to ensure the project objectives and benefits are achieved.  The closing stage also helps to acknowledge and appreciate the project stakeholders, and to transfer the project ownership and responsibility to the customer or sponsor 1 2 .  References :  CBAP® Handbook ,  Project Management Body of Knowledge (PMBOK® Guide) - Sixth Edition

An operational assessment is an input that is required to perform the assessment of enterprise limitations. An operational assessment is a technique that evaluates the current state of the business operations and identifies the gaps, issues, and opportunities for improvement. An operational assessment can help to determine how the solution will affect the existing business processes, policies, procedures, roles, and responsibilities, and how these factors may limit the value realization of the solution. An operational assessment can also help to identify the dependencies, assumptions, constraints, risks, and issues that may arise from the implementation of the solution and how they can be addressed or mitigated.

The other options are not inputs for the assessment of enterprise limitations, but rather outputs or outcomes of the task. Potential value is the expected benefit that the solution will provide to the enterprise and the stakeholders, and it is determined by comparing the current state and the future state of the enterprise. Solution performance analysis is a technique that measures and evaluates the actual performance of the solution against the expected performance and the business objectives. Organizational structure is the arrangement of the roles, responsibilities, and relationships within the enterprise, and it may be affected or changed by the solution.

References :

[BABOK Guide v3], Section 8.4: Assess Enterprise Limitations, p. 206-207

Measure Solution Performance , Task Card: Assess Enterprise Limitations, p. 2

How to assess enterprise limitations – The Functional BA , Blog Post, November 2019

A collaborative approach is a type of elicitation approach that involves working with multiple stakeholders simultaneously to elicit, analyze, and validate requirements. A collabo rative approach can help to complete requirements elicitation activities in a short period of time, as it can:

Reduce the number of individual meetings and interviews that need to be conducted

Increase the quality and quantity of information that can be gathered from different perspectives and sources

Enhance the communication and understanding among the stakeholders and the BA

Promote the consensus and agreement on the requirements and the solution scope

Identify and resolve any conflicts, issues, or gaps in the requirements

Some examples of collaborative elicitation techniques are:

Requirements workshops: A structured and facilitated session that brings together a group of stakeholders to elicit, analyze, and prioritize requirements

Brainstorming: A technique that generates a large number of ideas or solutions from a group of stakeholders in a creative and spontaneous manner

Focus groups: A technique that collects the opinions, preferences, and feedback of a group of stakeholders on a specific topic or issue

Prototyping: A technique that creates a simplified or partial version of the solution to elicit, demonstrate, and validate requirements

The other options are not correct because they are not types of elicitation approaches, but rather techniques that can be used within an elicitation approach. An experiment is a technique that tests a hypothesis or an assumption by observing the results of a controlled or simulated scenario. An estimation is a technique that approximates the size, cost, duration, or effort of a project or a solution. A research is a technique that collects and analyzes information from existing sources, such as documents, reports, databases, etc.

References :

[BABOK Guide v3], Section 4.2: Conduct Elicitation, p. 100-101

Types of Elicitation Techniques for the Business Analyst , Blog Post, September 2018

Elicitation Techniques Used by Business Analysts – Tips and Guidance , Blog Post, July 2023

The BA should provide process models as artifacts that can be used organization wide for the long-term. Process models are graphical representations of the activities, i nputs, outputs, and interactions of a business process. They can help to document, analyze, improve, and communicate the current and future states of a process. They can also serve as a basis for developing other artifacts, such as requirements, test cases , user manuals, and training materials. Process models can be useful for various stakeholders, such as business users, managers, developers, testers, and trainers, to understand and optimize the business process.  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. 263-264

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. 159-160

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 9: Solution Evaluation, Section 9.5: Assess Organizational Readiness, p. 261-262

 The first step for the BA is to understand the current state of the service provider’s business operations and the root causes of the reduced profit margin. This will help the BA to identify t he problems and opportunities for improvement, as well as to establish a baseline for measuring the effectiveness of the proposed solutions. The BA can use various techniques to conduct the current state analysis, such as document analysis, interviews, obs ervation, surveys, and SWOT analysis. The other options are not the first step, as they are either focused on the future state or the solution, without understanding the current situation and the underlying needs.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 3: Business Analysis Planning and Monitoring, Section 3.2: Plan B usiness Analysis Approach, p. 93-94

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 106-109

Relaying upper management support to stakeholders is a way to reduc e employee discontent and resistance to change. This can help the employees feel more confident and secure about the change initiative, as they perceive that the leaders are committed and supportive of the change. It can also help the employees understand the vision and goals of the change, and how it aligns with the organizational strategy and values. By communicating the benefits and rationale of the change, and addressing the concerns and fears of the employees, the BA can foster a positive and collabora tive attitude towards the change among the stakeholders.  References :

Emotional Reactions to Change in the Workplace , CMI

Reactions to Change in an Organization , Wonder

IIBA BABOK Guide , Section 5.5, Assess Organizational Readiness

Effectiveness is a performance measure that evaluates how well the work products meet the intended goals and objectives. It can be assessed by comparing the actual outcomes with the expected outcomes, and by measuring the degree of stakeholder satisfaction and value realization.  Effectiveness can help the BA to determine the quality and impact of the business analysis work, and to identify any gaps or areas for improvement 1 2 3 .  References :

1 : BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.5: Plan Business Analysis Performance Improvements

2 : BABOK Guide v3, Chapter 10: Tec hniques, Section 10.35: Root Cause Analysis, Section 10.36: Scope Modeling

3 : Performance Measurement - What Is It, Example, Methods, Types(https://www.wallstreetmojo.com/performance- measurement/)

 A communications management plan is a document that describes how the business analyst will communicate with the stakeholders throughout the project. It includes information such as the timing and frequency of communication, the location and mode of communication, the tools and techniques to be used, the delivery methods and formats, and the stakeholders’ preferences and needs. A communications management plan helps to ensure that the stakeholders are informed, engaged, and satisf ied with the project progress and outcomes. A stakeholder collaboration plan is a document that describes how the business analyst will collaborate with the stakeholders to elicit, analyze, validate, and manage the requirements. A business analysis plan is a document that describes how the business analyst will conduct the business analysis activities, such as the scope, approach, deliverables, tasks, resources, and schedule. A stakeholder analysis plan is a document that describes how the business analyst will identify, analyze, and prioritize the stakeholders and their needs, expectations, and influence.  References :  BABOK Guide v3 , Chapter 2: Business Analysis Planning and Monitoring, Section 2.5: Plan Business Analysis Communication, p. 38-40; Chapter 3: Business Analysis Governance and Information Management, Section 3.1: Plan Business Analysis Governance, p. 50-51.

 The requirement ‘’Ability to view policies created in the legacy system for a period of 6 months’’ is a transition requirement. A transition requirement is a temporary requirement that specifies the capabilities or conditions that the solution must have or meet during the transition from the current state to the future state. Transition requirements are typically relat ed to data conversion, training, migration, or decommissioning. In this case, the requirement is needed to ensure that the policies created in the legacy system are still accessible for a limited time after the system is decommissioned, until the new syste m is fully operational and stable.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Editi on , Chapter 2: Business Analysis Key Concepts, Section 2.4: Requirements Classification Schema, p. 66-67

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 2: Business Analysis Key Concepts, Section 2.4: Requirements Classification Schema, p. 34-35

Return on investment (ROI) is a financial calculation that measures the profitability of a solution proposal by comparing its benefits and costs. ROI is expressed as a percentage or a ratio of the net benefits (benefits minus costs) to the total costs. ROI can help to determine which solution is worth investing in based on its breakeven point, which is the point where the net benefits equal zero, or the benefits equal the costs. The solution with the highest ROI has the lowest breakeven point, meaning that it recovers its costs faster and generates more net benefits over time. Discount rate is a financial calculation that measures the present value of future cash flows by applying a d iscount factor that reflects the time value of money and the risk of the investment. Discount rate can help to compare the present values of different solution proposals, but it does not indicate the breakeven point. Net present value (NPV) is a financial calculation that measures the difference between the present value of the benefits and the present value of the costs of a solution proposal. NPV can help to determine which solution has the highest value in today’s terms, but it does not indicate the brea keven point. Internal rate of return (IRR) is a financial calculation that measures the annualized effective compounded return rate of a solution proposal by finding the discount rate that makes the NPV equal zero. IRR can help to determine which solution has the highest return rate, but it does not indicate the breakeven point.  References :  BABOK Guide v3 , Chapter 10: Techniques, Section 10.23: Financial Analysis, p. 529-531;  Free CBAP IIBA Actual Exam Questions & Answers , Question 464.

The stakeholders that were missed in the requirements are the end users. End users are the people who will use the solution or be affected by its outcomes. They are a key source of requirements, as they can provide valuable insights into the needs, expectations, preferences, and pain points of the solution. The BA should elicit requirements from the end users, as well as validate and verify them with their feedback. The BA should also ensure that the end users are involved throughout the project lifecycle, from planning to testing to implementation. The other options are not the stakeholders that were missed, as they are either not directly related to the solution or not the primary source of requirements.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 59-60

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 2: Business Analysis Key Concepts, Section 2.3: Stakeholders, p. 28-29

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.1: Prepare for Elicitation, p. 97-98

A change strategy is a plan that outlines how the project team will manage the transition from the current state to the future state of the system, and how they will address the impacts and risks of the change on the organization and the stakeholders. A change strategy is needed when system A is offline for 3 months, as this will affect the claims processing operations and the user experience. A change strategy should include the following elements:

Change vision and objectives : This defines the purpose and scope of the change, and the expected outcomes and benefits of the system upgrade.

Change readiness assessment : This evaluates the current level of awareness, willin gness, and ability of the organization and the stakeholders to adopt the change, and identifies any gaps or barriers that need to be addressed.

Change impact analysis : This identifies and analyzes the potential effects of the change on the business process es, roles and responsibilities, policies and procedures, systems and tools, and culture and behavior of the organization and the stakeholders.

Change communication plan : This specifies the key messages, channels, methods, and frequency of communication wit h the organization and the stakeholders, and how to solicit and incorporate feedback and input.

Change training plan : This defines the learning objectives, content, delivery modes, and evaluation methods of the training programs that will help the organiza tion and the stakeholders acquire the necessary knowledge and skills to use the upgraded system.

Change management roles and responsibilities : This clarifies the roles and expectations of the project team, the sponsors, the champions, the change agents, an d the end users in the change process, and how they will collaborate and coordinate with each other.

Change monitoring and evaluation plan : This establishes the metrics, indicators, and tools that will measure the progress and performance of the change pro cess, and how to report and act on the results.

References :

IIBA BABOK Guide , Section 5.6, Define Change Strategy

Change Management Strategy: A Guide with Best Practices , Smartsheet

How to Develop a Change Management Strategy , Indeed

A trigger for re-prioritization is an event or a change that affects the relative importance or urgency of the project’s requirements or deliverables 1 . A new initial public offering (IPO) in the stock market is an example of such an event, as it may create new opportunities or threats for the online sto ck trading system and its stakeholders. The project team may need to re-prioritize the requirements or deliverables to align with the new market conditions and stakeholder expectations.  The other options are not triggers for re-prioritization, but rather project issues or risks that need to be managed or mitigated.  References :  1

 The level of decomposition needed for the requirements depends on the complexity of the system, the level of detail required by the stakeholders, and the level of architecture decomposition that is necessary to specify the system being developed. The BA must t ake into account the stakeholder perspectives when decomposing the requirements, as different stakeholders may have different needs and expectations for the granularity and clarity of the requirements. The BA must also ensure that the decomposed requiremen ts are consistent, feasible, verifiable, and traceable to the higher-level requirements.  References :

BABOK Guide v3, Secti on 5.2.3: Decompose Requirements - Guidelines and Tools 1

Step 4: Analyze, Refine & Decompose Requirements - AcqNotes 2

MDRE: Developer Derived/Decomposed Requirements | SpringerLink 3

Requirements Decomposition - ArgonDigital | Making Technology a … 4

Requirements decomposition - No Magic Product Documentation

The number of communication channels in a project is calculated by the formula:

n(n−1)/2

, where

n

is the number of stakeholders. Therefore, if there are 50 stakeholders in the current project, the number of communication channels is:

50(50−1)/2=1225

Communication channels are the pathways or mediums through which information is exchanged among the stakeholders. The more stakeholders involved in a project, the more communication channels are needed, and the more complex the communicatio n management becomes. References : CBAP / CCBA Certified Business Analysis Study Guide , chapter 6, page 236; CBAP Sample Questions , question 248.

A survey is an elicitation technique that involves collecting information from a large number of stakeholders by using a predefined set of questions. Surveys can be conducted online, by phone, by mail, or in person. Surveys are useful for gathering quantitative data, such as ratings, rankings, frequencies, or percentages. Surveys can also include open-ended questions to gather qualitative data, such as opinions, feedback, or suggestions. Surveys are suitable for situations where the stakeholders are geographically dispersed, have limited availability, or have similar roles or perspect ives. In this case, the BA wants to gather information from 30 international facilities, which implies a large and diverse group of stakeholders. A survey would allow the BA to reach out to them efficiently and effectively, and to measure their satisfactio n with their jobs.  References :  9 Elicitation Techniques Used by Business Analysts – Tips and Guidance ,  Top 5 Requirements Elicitation Techniques for Business Analysts ,  The 50 Tech niques You Must Master to Become A CBAP ,  CCBA® and CBAP® Certifications Study Guide

The HAZOP technique, which stands for Hazard and Operability Study, is a qualitative technique that involves a disciplined analysis of the event sequences that could transform a potential hazard into an accident. The HAZOP technique is a systematic and structured method of identifying and evaluating the possible deviations from the intended design, operation, or functionality of a system, process, or product. The HAZOP technique uses a set of guide words, such as no, more, less, as well as, part of, and reverse, to generate different scenarios of what could go wrong and why.  The HAZOP technique helps to identify the causes, consequences, and safeguards of the deviations, and to recommend the ap propriate actions or controls to prevent or mitigate the hazards 1 2 . A failure mode and effects criticality analysis (FMECA) is a qualitative technique that involves an extension of the failure mode and effects analysis (FMEA) by adding a criticali ty rating to each failure mode. A FMECA is a method of identifying and evaluating the potential failures of a system, process, or product, and their impacts on the performance, safety, or reliability of the system, process, or product.  A FMECA helps to prioritize the failures based on their severity and frequency, and to determine the corrective actions or prev entive measures to reduce or eliminate the failures 1 3 . A failure mode and effects analysis (FMEA) is a qualitative technique that involves a systematic analysis of the potential failures of a system, process, or product, and their effects on the performance, safety, or reliability of the sys tem, process, or product. An FMEA is a method of identifying and evaluating the causes, modes, and consequences of the failures, and the existing or planned controls to detect or prevent the failures.  An FMEA helps to improve the design, operation, or functionality of the system, p rocess, or product, and to reduce the risk of failures 1 4 . A preliminary risk analysis (PRA) is a qualitative technique that involves a high-level assessment of the risks that may affect a project o r a solution. A PRA is a method of identifying and evaluating the sources, events, and impacts of the risks, and the existing or planned responses to the risks.  A PRA helps to determine the feasibility and viability of the project or the solution, and to establish the scope and objectives of the risk management process 1 5 .  References :

CBAP® Handbook

HAZOP Technique - iiba.org

Failure Mode and Effects Criticality Analysis - iiba.org

Failure Mode and Effects Analysis - iiba.org

Preliminary Risk Analysis - iiba.org

 A scribe is a participant who has to keep the minutes and details of the conversation during interviews. A scribe is a person who records the key points, questions, answers, and action items that are discussed during the interview. A scribe helps to capture the information accurately and completely, as well as to document any assumptions, issues, or risks that arise during the interview. A scribe also helps to prepare and distribute the interview notes and follow-up actions to the relevant stakeholders. A scribe can be a business analyst, a stakeholde r, or a third-party facilitator, depending on the availability and suitability of the role.  References :  IIBA BABOK Guide v3 , section 4.2.5.2, page 116;  CBAP / CCBA Certified Business Analysis Study Guide , chapter 4, page 178;  Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam , question 240.

Risk communication is the technique that involves coordinating and collaborating with other credible sources in risk. Risk c ommunication is the process of exchanging information and opinions about the nature, magnitude, significance, and control of the risks among the stakeholders. Risk communication helps to create a common understanding of the risks, to build trust and confid ence among the stakeholders, to inform and educate the stakeholders about the risk management activities and outcomes, and to solicit feedback and input from the stakeholders. Risk communication is an essential part of risk management, which also includes risk identification, risk analysis, and risk response.  References : [IIBA BABOK Guide v3], section 11.2.4, page 389;  CBAP / CCBA Certified Business Analysis Study Guide , chapter 5, page 233;  Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam , question 246.

The marketing department (AAC) is a key stakeholder for launching an existing product in another channel, as they are responsible for defining the requirements, confirming the elicitation results, and validating the solution. Therefore, they have a high influence on the project, as they can affect the decisions and outcomes of the project. They also have a high impact fr om the project, as they will be directly affected by the changes and benefits of the new channel.  According to the stakeholder analysis technique, influence and impact a re two dimensions that can be used to categorize and prioritize stakeholders 1 2 .  A stakeholder with high influence and high impact is considered a primary stakeholder, who should be actively involved and engaged throughout the project

The product scope statement defines the delivera ble the customer is expecting. It describes the features, functions, and characteristics of the product, service, or result that will be produced by the project. It also defines the acceptance criteria, assumptions, and constraints related to the product s cope. The product scope statement is a key input for developing the project scope statement, which defines the work that needs to be done to deliver the product scope. The product scope statement is usually created by the business analyst in collaboration with the customer and other stakeholders, and approved by the solution owner.  References :  IIBA BABOK Guide v3 , section 5.1.2, page 162;  CBAP / CCBA Certified Business Analysis Study Guide , chapter 6, page 233;  Free CBAP CBAP® Exam Questions - IIBA CBAP Exam - Study4Exam , question 242.

The approach that would help the BA to understand the functionality definition issues is to use a requirements traceability repository, as this is a technique that helps to track the origin, dependencies, and relationships of the requirements throughout the business analysis process. A requirements traceability repository can help the BA to identify the sources, o wners, and stakeholders of the requirements, as well as the changes, impacts, and risks associated with them. By using a requirements traceability repository, the BA can avoid duplication, inconsistency, and ambiguity in the functionality definition, and e nsure that the requirements are aligned with the business needs and objectives.  References : The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 6: Requirements Life Cycle Management, p. 209-210; Chapter 10: Requirements Traceability, p. 348-351.

Business Analysis for Practitioners: A Practice Guide , Chapter 4: Requirements Life Cycle Management, p. 99-100,

A presentation is a conversation between one or more speakers center ing on one specific topic, such as a business analysis technique, a solution option, or a project status update. Presentations are used to communicate information, persuade stakeholders, or demonstrate a solution. Presentations can be delivered in various formats, such as slides, videos, or posters. Presentations are one of the 50 business analysis techniques described in the BABOK® Guide.  References :

BABOK® Guide , section 10.41, Presentation

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , chapter 8, Eli citation and Collaboration Techniques, page 247

Certified Business Analysis Professional™ (CBAP®) | Coursera , course 3, Business Analysis: Elicitation a nd Collaboration, week 3, Presentation

A tornado diagram is a type of bar chart that shows the effect of varying different input parameters on an output variable. It is often used in sensitivity analysis to compare the relative importance of different factors or uncertainties that affect the outcome of a decision, project, or model. A tornado diagram typically has a horizontal baseline that represents the base case value of the output variable, and vertical bars that extend to the left and right of the baseline to show how the output changes when each input parameter is varied from its minimum to maximum value, while holding all other parameters constant. The bars are usually sorted by their length, creating a shape similar to a tornado. The longer the bar, the mor e sensitive the output is to that input parameter. A tornado diagram can help identify the key drivers of the output variable, as well as the parameters that have little or no impact. 

Variance analysis is the process of comparing the planned project results with the actual project results and identifying the causes and impacts of any deviations. Variance analysis helps project managers to monit or and control the project performance, identify and mitigate risks, and implement corrective actions or changes if needed. Variance analysis can be applied to various aspects of the project, such as scope, schedule, cost, quality, and resources.  Reference s :

A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition , Chapter 4.5.3, p. 123

Planned vs. Actual Progress Explained - SmartPM

 According to Herzberg’s two-factor theory of motivation, there are two sets of factors that influe nce job satisfaction: hygiene factors and motivators. Hygiene factors are those job factors that are essential for existence of motivation at workplace, but do not lead to positive satisfaction for long-term. They are also called dissatisfiers or maintenan ce factors, as they are required to avoid dissatisfaction. Hygiene factors include pay, company policies, fringe benefits, physical working conditions, status, interpersonal relations, and job security. Motivators are those factors that yield positive sati sfaction and enhance motivation. They are inherent to work and relate to self-growth and self-actualization. Motivators include recognition, sense of achievement, growth, responsibility, and advancement. The chance to excel is a motivator, not a hygiene fa ctor, according to Herzberg’s theory.  References :  Herzberg’s Two-Factor Theory Of Motivation-Hygiene - Simply Psychology ;  Herzberg’s Two-Factor Theory of Motivation - Management Study Guide ;  Two-factor theory - Wikipedia

The improvement opportunity that this situation represents is to enhance access to the relevant information. This means that the group of companies needs to im prove the way they collect, store, share, and use the data that is essential for making decisions on handling materials and allocating resources. By enhancing access to the relevant information, the group of companies can increase their efficiency, effecti veness, and profitability, as well as their competitiveness in bidding for government contracts. Enhancing access to the relevant information may involve deploying a new system across the companies or developing a repository of information from each compan y, but these are not the improvement opportunities themselves, but rather possible solutions or approaches to achieve the improvement opportunity. Creating a business model canvas to outline business needs is not the improvement opportunity, but rather a t echnique that can help to define and communicate the value proposition and the strategic direction of the group of companies.  References :

CBAP / CCBA Certified Business Ana lysis Study Guide, 2nd Edition , Chapter 6: Strategy Analysis, page 249

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 5: Strategy Analysis, section 5.4: Define Change Strategy, page 103

Business Analysis Professional Resources , IIBA Resource Collection, Business Analysis Body of Knowledge (BABOK) Guide

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Skillsoft Book, Chapter 6: Strategy Analysis, page 249

The lessons learned document is a document that captures and documents the successes, opportunities for improvem ent, failures, and recommendations for improving the performance of future projects or project phases. The lessons learned document is updated throughout the project lifecycle, not just at a specific phase. Updating the lessons learned document throughout the project lifecycle helps to ensure that the valuable knowledge and experience gained from the project are recorded, shared, and applied in a timely and effective manner.  It also helps to avoid repeating the same mistakes or missing the same opportunities in the current or future projects 1 . The lessons learned document is updated at the end of each project phase or iteration, or whenever a significant event or change occurs in the project.  The lessons learned document is also reviewed and finalized at the end of the project, as part of the project closure process 2 3 .  References :

CBAP® Handbook

Business Analysis Body of Knowledge (BABOK® Guide) - Version 3 , section 7.6 Manage Project Closure

Lessons Learned - iiba.org

 A desired outcome is a statement of what the organization wants to achieve as a result of the business analysis work. A desired outcome should be specific, measurable, achievable, relevant, and time-bound (SMA RT). A desired outcome should also be aligned with the organizational goals and objectives, and provide value to the stakeholders. Examples of desired outcomes are increase sales, reduce costs, and reduce time to deliver a product or service. Implement new machinery to complete the work processes faster is not an example of a desired outcome, but rather a possible solution or requirement that may help to achieve a desired outcome.  References :  BABOK Guide v3 , page 97;  CBAP / CCBA Certified Business Analysis Study Guide , page 217.

The CEO’s executive dec ision to start and complete the top 25 revenue-producing stores in the first year shows a risk-seeking or risk-taking attitude. This means that the CEO is willing to accept higher risks for higher rewards, and sees risks as opportunities rather than threat s. The CEO is not avoiding, mitigating, or neutral to the risks involved in the remodeling project, but rather embracing them and pursuing them aggressively. This may result in increased revenue and customer satisfaction, but also exposes the organization to potential losses and disruptions.  References :

Risk Attitude in Project Management: Definition, Types & Example , Web Article, August 2022

Risk Appetite vs. Risk Tolerance: What is the Difference? , Web Article, October 2022

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 3: Strategy Analysis, p. 95-96

Certified Business Analysis Professional™ (CBAP®) Specialization , Course 3: Business Analysis: Strategy Analysis, Week 1: Strategy Analysis Overview, Video: Risk Analysis

The BA should not simply adopt the structure of the solution consultants’ requirements catalog © or the corporate standard (D), because they may not be suitable for the branch’s specific needs an d preferences. The BA should analyze the existing structures and compare them with the branch’s definitions of user roles, tasks, and features, as well as with the best practices for specifying customization requirements.

The BA should not devise a structure that best fits the branch’s definition of user roles (A), because this may not capture all the relevant aspects of the customization requirements, such as the system features, the user tasks, the dependencies, the constraints, the acceptance criteria, etc. The BA should consider all these factors and use a comprehensive and consistent structure that facilitates communication and understanding among the stakeholders.

The BA should explore and apply best practices for specifying this type of requirements (B), because this will help the BA to create a clear, complete, and accurate specification that meets the expectations of the sponsor, the solution consultants, and the PGA staff. The BA should also ensure that the structure of the specification is aligned with the branch’s standards and conventions, and that it supports the project objectives and scope.

An activity diagram is a technique that is used to model the dynamic aspects of a system or a domain. It shows the sequence and conditions of the actions (or activities) that are performed by the actors or components involved in a business process or a use case. An activity diagram can also show the inputs, outputs, and res ources required for each action, as well as the exceptions and alternative paths that may occur. An activity diagram can help to identify and analyze the business processes that need to be performed and managed in the future state of the solution.  Referenc es : The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 9: Data Modeling, p. 326-331; Chapter 10: Data Flow Diagrams, p. 336-339; Chapter 10: Activity Diagrams, p. 340-343.

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Analysis and Design Definition, p. 125-126, 131-132.

Performance variance is the difference between the actual and expected results of a business activity or process. In this case, the business sponsor expected that the promotions would be viewed by at least 30% of the customers and that they would help reduce claims. However, the actual results showed that only 5% of the customers viewed the promotions and that claims increased by 20%. The business sponsor wanted to understand the reasons for this discrepancy and how to improve the effectiveness of the promotions.

The BA should approach the solution limitation by assessing the impact on t he business operations. This means that the BA should analyze how the inability to meet the SLA in one out of five scenarios would affect the business goals, objectives, performance, value, and risks. The BA should also consider the frequency, severity, an d likelihood of the scenarios, and the expectations and needs of the stakeholders. Based on the impact assessment, the BA can then recommend the best course of action, such as modifying the SLA, changing the business process, increasing the scope, or defer ring the requirement to a future release. The other options are not the best approaches, as they may either be unrealistic, unnecessary, or ineffective without a proper impact assessment.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 311-312

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 269-270

 A concept model is a visual representation of the business concepts and their relationships. It helps to clarify the meaning of the terms and concepts used in the requirements. However, different stakeholders may have different levels of understanding and interest in the concept model, depending on their roles and perspectives. Therefore, the BA should use an appropriate level of abstraction to support d iffering viewports, which are views of the same model that focus on different aspects or levels of detail. This way, the BA can tailor the presentation of the concept model to suit the needs and expectations of each stakeholder group, and help them underst and the impacts to their respective daily tasks.  References :  BABOK Guide v3 , p. 112-113;  CBAP/CCBA Study Guide , p. 140-141.

 A satisfy relationship is a type of traceability relationship that indicates that a model element (such as a requirement, a design element, or a test case) fulfills the intent of another model element ( such as a stakeholder need, a business requirement, or a regulatory requirement). By using a satisfy relationship, the BA can link the solution components that implement the regulatory requirements and show how they meet the compliance criteria.  References :

Overview of working with requirements (SysML)

SysML: Establishing Traceability using Matrix and ETL Table

IIBA BABOK Guide , Section 7.6, Traceability and Monitoring

The business analysis information architecture would help the BA expedite the approval process for the analysis phase. The business analy sis information architecture is the structure and format of the business analysis information, such as the requirements, designs, and models. It defines how the information is organized, stored, accessed, and communicated to the stakeholders. It also inclu des the standards, guidelines, and templates for creating and presenting the information. Having a clear and consistent business analysis information architecture can help the BA to ensure the completeness, quality, and traceability of the requirements pac kage, as well as to facilitate the review and approval process by the stakeholders.  References :

CBAP / CCBA C ertified Business Analysis Study Guide, 2nd Edition , Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Information Management, p. 103-104

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 3: Business Analysis Planning and Monitoring, Section 3.4: Plan Business Analysis Information Management, p. 69-70

The company’s response to the vendor’s request is to deny it because of the company’s risk aversion. Risk aver sion is the tendency to avoid or minimize exposure to uncertain or potentially negative outcomes. A conservative company with rigorous risk control plans and internal audit rules would be highly risk-averse and would not grant remote access to quality and production data to an external vendor, even if the vendor provides routine maintenance for the core business application. Remote access could pose security, privacy, and compliance risks for the company and its data, and the company would prefer to restric t and control the access and maintenance to be on-site. The company would not accept the vendor’s request, even if the company has an urgent problem to solve or if the immediate remote access could resolve the issue, because the company would prioritize ri sk mitigation over convenience or efficiency.  References :

CBAP / CCBA Certified Business Analysis Study Guide , 2nd Edition , Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 311-312

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 7: Solution Evaluation, Section 7.2: Analyze Performance Measures, p. 269-270

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.3: Assess Enterprise Limitations, p. 277-278

The contract terms may affect the timing of the business analysis activities, as they may specify the deadlines, deliverables, and milestones that the BA must adhere to. The contract terms may also influence the business analysis approach, the level of detail and formality of th e deliverables, and the stakeholder involvement. The other options are not directly related to the timing of the business analysis activities, although they may have some influence on the scope, quality, and complexity of the work.  References :

Business analysis approach planning – The Functional BA , paragraph 5

Introdu ction & Guidance To Business Analysis Planning and Monitoring , section “Plan Business Analysis Approach”, paragraph 4

Planning the Analysis Phase: using a Work Breakdown … - Modern Analyst , paragraph 1

A stakeholder engagement approach is a plan that describes how the BA will interact with the stakeholders, identify their needs and expectatio ns, and address their concerns and issues. A stakeholder engagement approach can help the BA avoid disagreements and conflicts by ensuring that the stakeholders are involved and informed throughout the business analysis process, and that their feedback and input are considered and incorporated. A stakeholder engagement approach can also help the BA build trust and rapport with the stakeholders, and manage their expectations and influence levels. By following a stakeholder engagement approach, the BA can ens ure that the business analysis approach and the budget estimates are aligned with the stakeholder needs and agreed upon by all the relevant parties.  References :

IIBA BABOK Guide , Section 3.2, Plan Stakeholder Engagement

Five-Step Approach to Stakeholder Engagement , BSR

5 steps to creating a stakeholder engagement plan (with template) , Asana

Based on the table in the image, the total cost of upgrad ing system A with the first 8 features is $3.5 million, which is equal to the budget for the initiative. This option would also allow the company to retain the system that is preferred by the claim processors and has more flexibility to be modified. The ot her options would either exceed the budget or compromise the functionality and usability of the system. Therefore, upgrading system A with the first 8 features is a feasible solution to make sure the project stays within budget.  References :

IIBA BABOK Guide , Section 10.23, Decision Analysis

Cost Benefit Analysis: An Expert Guide , Smartsheet

How to Choose the Right Software Vendor , CIO

A model is a simplified representation of a complex reality that is useful for understanding that reality and making decisions regarding it. A model can describe a situation or problem, define boundaries for the business domain, describe thought processes and action flows, and other aspects of the requirements. However, a model cannot define the resources that will be needed on the project team, as this is not part of the requirements but rather part of the pr oject management plan.  References :  BABOK Guide v3 , page 123;  CBAP/CCBA Study Guide , page 181.

The project manager is the stakeholder who must approve the business analysis approach to ensure that it is compatible with the other project activities. The project manager is responsible for overseeing the project execution, managing the project resources, and ensuring that the project meets its objectives, scope, schedule, and budget. The project manager also coordinates the work of the project team, including the business ana lyst, and ensures alignment between the project management approach and the business analysis approach. The project manager needs to approve the business analysis approach to ensure that it supports the project goals, fits the project constraints, and does not conflict with the project plan. The project manager also needs to monitor and control the business analysis activities and deliverables throughout the project lifecycle.  The project manager and the business analyst should collaborate closely to define and document the business analysis approach, as well as to communicate and manage changes to the approach as needed 1 2 3 4 .  References :  1 : How to Choose the Right Business Analysis Approach 1   2 : Business analysis approach planning 2   3 : Approve Requirements 3   4 : Defining the Business Analysis Approach in 2023 5

 A dependency is a relationship or a condition that affects the completion or the quality of a task or an activity. A dependency can be internal or external, mandatory or discretionary, or positive or negative. In this case, the inspector’s signoff on the initial deliverable s is a dependency because it is a condition that must be met before the task can be completed. The inspector’s signoff is an external and mandatory dependency, as it involves an outside party and it is required by the project scope or contract. A dependenc y is not the same as an assumption (A), which is a factor that is considered to be true without proof, a milestone ©, which is a significant point or event in the project, or a constraint (D), which is a factor that limits the options or performance of the project.  References :

What is a Dependency in Project Management? - Wrike , paragraph 1

Project Dependencies: Types, Examples, and Tips for Project Managers , paragraph 1

CBAP Certification Study Guide v3.0 , Chapter 4: Requirements Life Cycle Management, Section 4.3: Trace Requirements, page 4-10

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.3.1

A business case is a document that provides the rationale and justification for initiating a project or an investment. It describes the business problem or opportunity, the proposed solution, the expected benefits, costs, risks, and assumptions. A business case also includes an analysis of the alternatives and a recommendation for the best option. A business case helps management to make a go/no go decision based on the value proposition and the return on investment of the project.  A business ca se is one of the key outputs of the enterprise analysis process, which involves defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the business case 1 2 3 4 .  References :  1 : BABOK Guide v3, section 3.4, pages 68-77  2 : CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, pages 107-108  3 : Business Analysis Techniques: Developing the Business Case, pages 25-2 6  4 : How to Write a Business Case: 4 Steps to a Perfect Business Case Template

The number of communication channels in a project is an indicator of the complexity of communication among the stakeholders.  It is calculated by using the following formula 1 :

Number of communication channels = N x (N - 1) / 2

Where N = Number of stakeholders

In this case, N = 435, so the number of communication channels is:

435 x (435 - 1) / 2 = 188,790

Therefore, the correct answer is A. 188,790.  References :

Communication Channels in Project Management: Formula & Examples

Number of Communication Channels (+ PMP® Formula & Calculator)

Change requests are more likely to occur in the early stages of a project, when the requ irements are being elicited, analyzed, and validated. During this time, stakeholders may discover new needs, identify gaps, or revise their expectations. Change requests may also arise due to changes in the business environment, such as new regulations, ma rket trends, or competitor actions. Change requests are less frequent in the later stages of a project, when the requirements are more stable and the solution is being designed, developed, and tested.  References :

A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 4: Requirements Life Cycle Management, Section 4.5: Manage Changes 1

CBAP Certification Study Guide v3.0, Chapter 4: Requirements Life Cycle Management, Section 4.5: Manage Changes 2

 Benchmarking is a technique for comparing the performance or practices of an organization with those of other organizations, usually considered to be the best in the field. It i s not a technique for identifying the solution approach, which is the process of defining the most feasible and appropriate way to implement a change that addresses a business need. The other techniques are useful for identifying the solution approach. Dec ision analysis helps to evaluate multiple options and select the best one based on criteria and trade-offs. Risk analysis helps to identify and assess the uncertainties and potential impacts of the solution approach. Brainstorming helps to generate and exp lore diverse ideas for the solution approach.  References :

BABOK® Guide v3 , section 10.17 Benchmarking, section 10.18 Brainstorming, section 10.25 Decision Analysis, section 10.33 Risk Analysis and Management, section 11.2 Define Solution Approach

CBAP® Handbook , section 5. Review the Exam Blueprint

Tips for Earning a Business Analysis Certification , section 4. Leverage a variety of study resources

The implementation approach is a component o f the solution scope that describes how the chosen solution approach will deliver the solution scope. The solution approach is the method or process that will be used to implement the solution, such as a predictive or adaptive approach.  The solution scope is the set of capabilities and features that the solution must provide to meet the business need 1 . The implementation approach explains how the solution approach will be applied to achieve the solution scope, such as the phases, activities, tasks, deliverables, and resources involved.  The implementation approach also considers the risks, issues, assumptions, and constraints that may affect the implementation process 2 3 .

The other options are not correct. A. The implementation approach is not described in terms of the major features and functions that are to be included, as this is part of the solution scope, not the impl ementation approach. B. The implementation approach does not define major business and technical dependencies that impose constraints to the effort to deploy the solution, as this is part of the risk analysis, not the implementation approach. C. The implem entation approach does not describe the new capabilities required to meet the business need, as this is part of the solution scope, not the implementation approach.  References :

Solution Scope - IIBA®

Defining the Business Analysis Approach in 2023 | Free Template

Business Analysis Planning an d Monitoring - IIBA®

Solution components are the parts of the physical architecture that implement the solution requirements. They include business processes , business policies, business rules, software applications, hardware devices, data structures, and other elements that constitute the solution. Solution components are identified and defined during the design process, and they are allocated to the requirem ents during the allocate requirements process.  The purpose of allocating requirements to solution components is to ensure that each requirement is fulfilled by on e or more solution components, and that each solution component contributes to one or more requirements 1 2 3 .

Assessment of proposed solution is not a solution component, but a technique that evaluates the feasibility, desirability, and suitability of a so lution option. Assessment of proposed solution is used during the enterprise analysis process, which involves defining the business need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the busine ss case.  The purpose of assessing the proposed solution is to compare the expected benefits and costs of the solution option, and to identify the risks, assumptions, and de pendencies that may affect the solution delivery 4 5 6 .  References :  1 : BABOK® Guide v3, section 7.2 Allocate Requirements, page 254  2 : CBAP / CCBA Certified Business Analysis Study Guide, chapter 7, page 243  3 : Allocation and Traceability 7   4 : BABOK® Guide v3, section 3.4.5.1 Assessment of Proposed Solution, page 75  5 : CBAP / CCBA Certified Business Analysis Study Guide, chapter 4, page 122  6 : Business Analysis Techniques: Assessing the Proposed Solution, page 27

A plan-driven approach to business analysis is a methodology that focuses on minimizing up-front uncertainty and ensuring that the solution is fully define d before implementation begins in order to maximize control and minimize risk. This approach tends to be preferred in situations where requirements are stable and clear, and where changes are costly and disruptive. Therefore, a plan-driven approach has the most business analysis work at the beginning of the project or during the start of a project phase, as it involves detailed planning, analysis, and documentation of the requirements and the solution.  A plan-driven approach also requires formal approval and sign-off of the requirements and the solution before moving to the next phase 1 2 3 .  References :  1 : How to Choose the Right Business Analysis Approach 1   2 : Plan driven projects versus change driven 2   3 : Business Analysis Methodology 3

Opportunities to prioritize requirements is not something that Rachel should include in her business case, a s it is not relevant for the decision-making process. A business case is a document that clearly identifies the reasoning for initiating a project to justify the resources required.  It includes the following items 1 2 :

A business problem or opportunity

Possible solutions and their benefits and disadvantages

Risks associated with the main solution

Costs

Implementation timeline

Consequences for implementing a solution and for retaining the status quo

Opportunities to prioritize requirements is not one of these items, as it is part of the business analysis process, not the business case. Prioritizing requirements is a technique that helps to rank the requirements in order of importance, urgency, or value for the stakeholders. It helps to determine which requirements should be im plemented first, and which ones can be deferred or excluded.  Prioritizing requirements is useful for managing the scope, schedule, and budget of the project, but it is not a factor that influences the approval or rejection of the project 3 4 .

The other opt ions are things that Rachel should include in her business case, as they are relevant for the decision-making process. A. Time to break even is the period of time required for the project to recover its initial investment.  It is a measure of the profitability and feasibility of the project, and it helps to compare different solution options 5 . C. Follow-on opportunities are the potential benefits or outcomes that can be achieved after the completion of the project, such as new markets, customers, products, or services. They are part of the qualitative and quantitative benefits of the project, and they help to demonstrate the valu e and alignment of the project with the business vision and strategy. D. Qualitative and quantitative benefits are the positive impacts or results that the project will deliver to the organization and the stakeholders, such as increased revenue, customer s atisfaction, efficiency, or quality. They are expressed in both non-numerical and numerical terms, and they help to justify the costs and risks of the project.  References :

How to Write a Business Case (Template Included) - ProjectManager

How to Write a Business Case | Smartsheet

Pr ioritizing Requirements - IIBA®

How to Prioritize Requirements: Techniques, Tools, and Examples

Break-Even Analysis - Definition, Formula, Example, and Advantages

[How to Write a Business Case (with Examples & Template to Help) - Pingboard]

[Cost-Benefit Analysis: A Quick Guide with Examples and Templates]

 Root cause analysis is a technique that help s identify the underlying causes of failures or difficulties in accomplishing business analysis work. It involves asking a series of questions to determine the origin of a problem and the factors that contributed to it. By finding and addressing the root c auses, the business analyst can prevent the problem from recurring and improve the performance of the business analysis process.  References :

CBAP® Handbook , page 18, section 4.5. Manage Business Analysis Performance

BABOK® Guide , page 387, section 10.25. Root Cause Analysis

Tips for Earning a Business Analysis Certification , section 2. Understand the BABOK® Guide

 A repository is a centralized place where project requirements are stored and managed throughout the project lifecycle. A repository ca n be a physical or electronic system that allows business analysts to access, update, and track the status of the requirements. A repository can also facilitate the communication, collaboration, and verification of the requirements among the stakeholders. A repository is not the same as a change manage ment system (A), a project scope statement ©, or a requirements register (D), which are different tools or documents that serve different purposes in project management.  References :

IIBA BABOK Guide v3 , p. 30, 176, 264

How to Write Project Requirements | Smartsheet , paragraph 3

What is Requirements Management? | IBM , paragraph 1

SWOT anal ysis is a technique for assessing the internal and external factors that may affect the feasibility, acceptability, and suitability of a proposed solution or solution approach. It evaluates the strengths and weaknesses of the solution or solution approach, as well as the opportunities and threats in the business environment. SWOT analysis helps to identify the key issues and risks that need to be addressed or mitigated, as well as the potential benefits and advantages that can be leveraged or enhanced.  References :

A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 10: Techniques, Section 10.50: SWOT Analysis

SWOT Analysis: How To With Table and Example - Investopedia

SWOT - Definition, Examples, Process, Uses - Corporate Finance Institute

A methodology is a set of principles, rules, and processes that guide the business analysis activities and deliverables within a project or organization. A methodology can be based on a standard, such as the BABOK Guide, or a specific framework, such as Waterfall or Agile. A methodology helps the business analyst to plan, execute, monitor, and control the business analysis work in a consistent and effective way.  References :

BABOK Guide , Chapter 2: Business Analysis Planning and Monitoring, Section 2.1: Plan Business Analysis Approach, p. 24-25

Business Analysis Methodology  | What is this and is it real?

The solution scope definition is a document that describes the features and functions of the solution that will address the business need and deliver the expected benefits. It also defines the boundaries and assumptions of the solution, as well as the criteria for its acceptance and evaluation. The solution scope definition should include the following elements:

Solution vision: A brief statement that summarizes the purpose, value proposition, and target audience of the solution.

Solution objectives: A list of measurable and achievable goals that the solution aims to accomplish, aligned with the business goals and objectives.

Solution requirements: A detailed and specific description of the stakeholder and solution requirements that define the scope and functionality of the solution, organized by categories, types, and priorities.

Solution constraints: A list of factors that limit the options or performance of the solution, such as technical, legal, regulatory, or organizational constraints.

Technical de pendencies : A list of relationships or interactions between the solution and other systems, components, or technologies that affect the solution’s design, development, or implementation.

Solution risks: A list of potential threats or uncertainties that may affect the solution’s success, along with their probability, impact, and mitigation strategies.

Solution scope statement: A concise statement that defines what is in and out of scope for the solution, and clarifies any ambiguities or conflicts among the solution requirements.

The solution scope definition does not include the business case (A), which is a separate document that justifies the need for the solution and analyzes its costs and benefits. The solution scope definition also does not include the elicitation techniques ©, which are the methods or tools used to gather information from the stakeholders and discover the requirements. The solution scope definition also does not include the organization readiness assessment (D), which is an analysis of the organization’s ability and willingness to adopt the solution and manage the change.

References :

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 30, section 3.1 1

Solution Scope – An Insight - Modern Analyst , paragraphs 2-3

Scoping a Solution | Microsoft Solutions Framework Essentials … - Flylib , paragraph 1

[Solution Scope vs. Project Scope - Enfocus Solutions Inc], paragraph 2

[How to Write Project Requirements | Smartsheet], paragraph 3

A requirements re-use repository is a collection of reusable requirements that can be applied to similar projects or products. It can help streamline the requirements gathering process by reducing the effort and time needed to elicit, analyze, and document requirements. It can also improve the quality and consistency of requirements by leveraging best practices and lessons learned from previous projects. A requirements re-use repository can also facilitate traceability, change management, and communication among stakeholders.

B. Implementing project templates is not the best answer because project templates are more related to project management than requirements gathering. Project templates can help standardize the project planning and execution processes, but they do not necessarily address the specific requirements of each project or product.

C. Implementing a requirements gathering form is not the best answer because a requirements gathering form is a tool for capturing and documenting requirements, not for streamlining the requirements gathering process. A requirements gathering form can help structure and organize the requirements, but it does not reduce the effort and time needed to elicit, analyze, and document requirements.

D. Implementing scope solution models is not the best a nswer because scope solution models are used to define and communicate the boundaries and features of a solution, not to streamline the requirements gathering process. Scope solution models can help clarify and validate the solution scope, but they do not reduce the effort and time needed to elicit, analyze, and document requirements.  References :

Using Scope Models to Manage Solution Scope - Business Analyst Artic les …

What is requirements gathering? Template and examples

Top 10 Requirements Gathering Templates with Samples and Examples

 Influence and attitude are two factors that the business analyst must consider when conducting stakeholder analysis. Influence is the stakeholder’s ability to affect the project or the solution, either positively or negatively. Attitude is the stakeholder’s level of support or resistance to the change, either en thusiastic or reluctant. By assessing these two factors, the business analyst can determine the stakeholder’s impact and interest in the project, and plan the appropriate engagement and communication strategies for each stakeholder group.  References :

CBAP® Handbook , page 15, section 4.1.2.3

BABOK® Guide , page 32, section 3.2.3

How To Create a Stakeholder Analysis (With Example)

How to Conduct a Thorough Stakeholder Analysis - CloudApp Bl og … - Zight

 A top-down estimate is an estimate based on past projects to predict the current cost and/or duration of the current project.  It is also called an analogous estimate, as it involves using data fr om previous, similar projects to estimate activity durations 1 . Top-down estimates are usually done at the early stages of a project, when there is not enough detail or information available to perform more accurate estimates. They are useful for providing a rough order of magnitude (ROM) or a ballpark figure for the project scope, cost and schedule.  Top-down estima tes are typically faster and cheaper to produce than bottom-up estimates, but they are also less accurate and reliable 2 3 .  Ref erences :  2 : Project Cost Esti mation: How to Estimate Project Cost - ProjectManager 2   3 : 11 Cost Estimating Methods (With Formulas and Examples) | Indeed.com 3   1 : Understanding the Analogous Estimating Technique | Runn 1

 Risk Data Quality Assessment is a technique that evaluates the degree to which the data about individual project risks is useful for risk management. It involves examining the extent to which the risk data is accurate, reliable, timely, complete, and realistic. This helps t o determine the quality and credibility of the information used for risk analysis and response planning.  References :

BABOK® Guide v3 , section 11.6.5.8, page 417

CBAP® Exam Prep Study Guide , chapter 9, page 339

CBAP® Certification Study Guide v3.0 , chapte r 9, page 301

A work product is any output of the business analysis process that is used to communicate, document, or manage requirements 1 .  Examples of work products include requirements documentation, i nterview questions and notes, meeting agendas and minutes, models, diagrams, matrices, traceability reports, and business cases 2 . Presentation slides are not a work product, as they are no t used to capture or manage requirements, but rather to present or summarize them to an audience. Presentation slides may contain information from work products, but they are not work products themselves.  References :

Work Product Definition & Meaning | Merriam-Webster Legal

Examples of ownership of work product clauses in contracts - Afterpattern

The type of project or initiative affects the business analysis duties that need to be performed, as different types of projects may require different approaches, techniques, deliverables, and stakeholders. For example, a software development project may have different business analysis needs than a business process improvement project. The business analyst should plan the business analysis process according to the project type and its character istics, such as scope, complexity, risk, methodology, and lifecycle.  References :

A Checklist for Business Analysis Planning

Business Analysis Process Flow: Step by Step Tutorial

What is Business Analysis? Process & Techniques

How do you plan a business analysis approach?

Enterprise analysis is a knowledge area that describes the business analysis activities that take place for an enterprise to identify business opportunities, build a business architecture, determine the optimal project investment path for the enterprise and implement new business and technical solutions 1 .  Enterprise analysis c an be triggered by different need generation approaches, such as bottom-up, external drivers, middle management, or top-down 2 .  In this case, the business need stems from external drivers, which are factors outside the organization that influence its performance, such as customers, competitors, regulations, or market trends 3 . A customer requesting new software for collecting customer information is an example of an external driver that creates a business need for the organization. The organization should conduct enterprise analysis to understand the customer’s requirements, assess the current capabilities and gaps, evaluate the feasibility and risks of the proposed solution, and define the business case and scope for the project.  References :

What is Enterprise Analysis: does it differ from Enterprise Architecture?

[Enterprise Analysis - Business Analyst Training]

[External Drivers: Definition & Examples - Video & Lesson Transcript | Study.com]

Benchmarking is a business analysis approach that involves comparing one’s own performance, processes, or products w ith those of other organizations, especially the best performers or industry leaders, to identify gaps and opportunities for improvement. Benchmarking can help business analysts understand the competitive landscape, identify best practices, set realistic g oals, and measure progress. In this question, Sally and her business analysis team are using benchmarking to determine what the competition is offering and how they can increase their revenue by remaining competitive.  References :

CBAP® Handbook , page 15, section 4.1.2.3

BABOK® Guide , page 32, section 3.2.3

CBAP / CCBA Certified Business Analysis Study Guide , page 96, section 3.2.3

What is a Competitive Analysis — and How Do You Conduct One?

A business case is a document that clearly identifies the reasoning for initiating a project to justify the resources required. It is written to justify the resources required for the project (money or effort) and align the project objectives to the business needs.  It also includes the costs , benefits, and risks of the proposed solution, and compares it with alternative options 1 .  A busin ess case is an important input for the project initiation and approval process, as it helps the decision makers to assess the value and feasibility of the project 2 .

To write a business case, you need four main inputs: feasibility study, assumptions and constraints, business need, and solution options 3 .  A feasibility study is an analysis that evaluates the technical, economic, social, and environmental aspects of the project, and determines whether it is viable and worth pursuin g 4 . Assumptions and constraints are factors that affect the project scope, cost, schedule, and quality, and that need to be identified and documented in the business case.  Assumptions are things that are believed to be true or certain, while constraints are things that limit or restrict the project 5 . Business need is the problem or opportunity that the project aims to address, and that aligns with the strategic goals and vision of the organization. Solution options are the different ways of solving the business need, and their respective costs, benefits, and risks.

Stakeholder concerns are not an input for writing a business case, but rather an output of stakeholder analysis. Stakeholder analysis is a process of identifying and prioritizing the people or groups who have an interest or infl uence in the project, and understanding their needs, expectations, and perspectives. Stakeholder concerns are the issues or challenges that the stakeholders face or anticipate in relation to the project, and that need to be addressed or resolved. Stakehold er concerns are important for defining the requirements, managing the communication, and ensuring the stakeholder satisfaction, but they are not directly used for writing the business case.  References :

How to Write a Business Case (Template Included) - ProjectManager

How to Write a Business Case | Sma rtsheet

Business Case Examples, explained in simple language - Chase Consulting

Feasibility Study: Definition, Metho ds, and Examples

Project Assumptions and Constraints: Examples and Differences

[Business Need - IIBA®]

[Solution Options - IIBA®]

[Stakeholder Analysis: Overview, Tools and Techniques - KnowledgeHut]

[Stakeholder Concerns - IIBA®]

 A business analysis communication plan is a document that describes how the business analyst will communicate with the stakeholders, including the stakeholder groups, communication needs, level of formality, frequency, format, and methods of communication. It is one of the outputs of the business a nalysis planning and monitoring knowledge area, and it helps to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis process and deliverables. A business analysis communication plan is not the same as a project commu nication plan, which covers the overall communication needs of the project and is typically created by the project manager. A business analysis communication plan focuses on the specific communication needs related to the business analysis activities and r equirements.  References :

IIBA BABOK Guide v3 , p. 36, 38, 40, 42

How to Create a Stakeholder Management Plan Smartsheet

CBAP 150 Practice Questions Flashcards , Question 5

How To Create an Effective Stakeholder Communication Plan

According to the BABOK Guide, defining the business needs is the process of identifying the ends that the organization is seeking to achieve. Business goals and objectives are statements of the desired outcomes of the change initiative that align with the organization’s strategy and vision. They provide the context for identifying and evaluating alternative solutions that can satisfy the business needs. Alternative identification, solution as sessment, and requirements are parts of other processes that follow defining the business needs.  References :

BABOK Guide , Chapter 5: Strategy Analysis, Section 5.1: Define the Business Need, p. 100-101

CBAP Certification Study Guide v3.0 , Chapter 5: Strategy Analysis, Section 5.1: Define the Business Need, p. 5-3 to 5-4

The conduct stakeholder analysis task is one of the tasks in the business analysis planning and monitoring knowledge area.  According to the BABOK® Guide 1 , this task involves identifying and analyzing the stakeholders of a change, assessing their attitudes, expectations, influence, and interests regarding the change, and determining the best ways to engage and communicate with the m. The purpose of this task is to ensure that the business analysis activities are aligned with the needs and concerns of the stakeholders, and that the stakeholders are appropriately involved and informed throughout the change.

The other options are not accurate descriptions of the conduct stakeholder analysis task, but rather:

A. This is a partial description of the define business need task, which identifies the business problem or opportunity that requires analysis.

C. This is a partial description of the assess capability gaps task, which compares the current and future states to identify the gaps that must be addressed by a solution.

D. This is a vague and incomplete description of the conduct stakeholder analysis task, as it does not mention the analysis, assessment, and engagement aspects of the task.

References :

CBAP® Handbook , page 15, section 4.1.2.3

BABOK® Guide , page 32, section 3.2.3

CBAP / CCBA Certified Business Analysis Study Guide , page 96, section 3.2.3

How To Create a Stakeholder Analysis (With Example)

How to Perform a Stakeholder Anal ysis | Lucidchart

 Videoconferencing is a communication technique that allows business analysts to interact with stakeholders who are not collocated. It enables real-time audio and visual communication, which can facilitate collaboration, feedback, and decision making. Videoconferencing can also help build rapport and trust among stakeholders, as well as reduce travel costs and time.  Videoconferencing is one of the many communication techniques that business analysts can use to elicit information and collaborate with stakeholders in different geographical locations 1 2 3 4 .  References :  1 : How to create a business analysis communication plan - Lucidchart  2 : Business Analysis Techniques: Eliciting Information and Collaborating with Sta keholders  3 : Key sets of BA: analysis and communication techniques - Exposit  4 : Communication strategy for stakeholder engagem ent – SustaiNet

 In addi tion to existing regulations and contracts, the BA also checks the policies of the organization that may constrain the project. Policies are the guidelines or principles that govern the decision making and actions of the organization. They reflect the valu es, vision, and mission of the organization and provide a framework for achieving its goals and objectives. Policies can also influence the scope, feasibility, and acceptance of the project and its solution. Therefore, the BA should identify and analyze th e policies that are relevant to the project and ensure that they are aligned with the requirements and the solution.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 206-207

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 5: Strategy Analysis, Section 5.1: Analyze Current State, p. 106-107

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 10: Solution Evaluation, Section 10.3: Assess Enterprise Limitations, p. 277-278

 The BA should recommend to assign the feature a lower priority for future release . This means that the feature will not be included in the initial release of the solution, but it may be considered for later releases depending on the availability of resources, the feedback from the stakeholders, and the alignment with the business objec tives. This approach can help to balance the value and the effort of the feature, as well as to avoid scope creep and unnecessary complexity in the initial release. The other options are not the best recommendations, as they may either ignore the needs of the stakeholders, disrupt the existing business process, or increase the risk and cost of the project.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 6: Requirements Analysis and Design Definition, Section 6.3: Prioritize Requirements, p. 255-256

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.3: Prioritize Requirements, p. 155-156

A performance assessment is a business analysis artifact that evaluates the effectiveness and efficiency of the business analysis work. It can be used to identify and document the improvement areas for the next piece of analysis work, as well as to measure the value delivered by the bu siness analysis outcomes.  A performance assessment can include metrics, indicators, targets, and feedback mechanisms that help the BA to monitor and improve the business analysis performance 1 2 .  References :

1 : BABOK Guide v3, Chapter 2: Business Analysis Planning and Monitoring, Section 2.5: Plan Business Analysis Performance Improvements

2 : Tasks Mapped To Artifacts(https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/5769/Tasks-Mapped-To-Artifacts.aspx)

 A use case diagram is a technique that helps to depict the interactions between a system and its actors using graphical symbols and relationships. A use case diagram shows the actors that are involved in the system, the use cases that represent the functions or services that the system provides, and the associatio ns that indicate how the actors and use cases are related. A use case diagram can be used with a state diagram to verify that all functions are defined to work with entity “User” for the different roles, as it can help to identify the use cases that corres pond to the states and transitions of the entity, and to ensure that the use cases are complete, consistent, and accurate. A sequence diagram is a technique that helps to represent the sequence and timing of the messages that are exchanged between the obje cts or components of a system. A sequence diagram shows the objects or components that participate in the interaction, the messages that are sent and received by the objects or components, and the time order of the messages. A sequence diagram can help to illustrate the dynamic behavior and logic of the system, but it does not show the interactions between the system and its actors. A functional diagram is a technique that helps to represent the functions or processes that are performed by a system or a sol ution using graphical symbols and relationships. A functional diagram shows the functions or processes that are relevant to the domain, the inputs and outputs of each function or process, and the decomposition and hierarchy of the functions or processes. A functional diagram can help to define and analyze the functional requirements, but it does not show the interactions between the system and its actors. A data flow diagram is a technique that helps to create a high-level overview of a business process by showing the movement and transformation of data between entities and processes. A data flow diagram uses graphical symbols and arrows to represent the sources and destinations of data, the processes that manipulate data, the data stores that store data, an d the data flows that transfer data. A data flow diagram can help to understand and document the data logic and structure of the business process, but it does not show the interactions between the system and its actors.  References :  BABOK Guide v3 , Chapter 10: Techniques, Section 10.50: Use Case Diagram, p. 564-566; Section 10.49: Sequence Diagram, p. 562-563; Section 10.22: Functional Decomposition, p. 528-529; Section 10.18: Data Flow Diagrams, p. 522-524.

The elicitation tech nique that the BA should select to enable the customer and the key stakeholders to visualize the final product is prototyping. Prototyping is a technique that involves creating a simplified or partial version of the solution that can demonstrate its featur es, functions, and appearance. Prototyping can help to elicit, validate, and verify the requirements, as well as to obtain feedback and approval from the stakeholders. Prototyping can also help to reduce the risks, costs, and time of the project by identif ying and resolving any issues or gaps before the final implementation of the solution.  References :

CBAP / CCBA Certified Business Analysis S tudy Guide, 2nd Edition , Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 167-168

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 103-104

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 fishbone diagram is a technique that helps identify, explore, and display the possible causes of a specific problem or quality characteristic. It can also be used to analyze the root causes of a problem or a gap between the current and desired states of a solution. By using a fishbone diagram, the BA can understand the reason why the performance of the solution does not meet the expected benefits and identify potential corrective actio ns.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 10: Solution Evalua tion, page 393

Business Analysis Body of Knowledge (BABOK ®) Guide , Version 3, Section 10.23: Fishbone Diagrams, page 382-383

 A business process model is a graphical representation of the activities, flows, events, and decisions that make up a business process. It can help to describe the current and future states of the process, identify the inputs, outputs, roles, and resources involved, and analyze the performance, value, and quality of the process. A business process model is a useful requirements viewpoint for presenting the requirements for an auto insurance product to domain and implementation SMEs, as it can show how the product will support the business goals, meet the customer needs, and integrate with the existing systems and processes.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 6: Requirements Analysis and Design D efinition, Section 6.4: Model and Validate Requirements, p. 263-264

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. 159-160

The next step for the BA after selecting a passive approach for establishing performa nce metrics is to identify the performance measures. Performance measures are the indicators that are used to evaluate the effectiveness and efficiency of a process, a solution, or an outcome. They can be quantitative or qualitative, and they can be based on various criteria, such as time, cost, quality, customer satisfaction, or compliance. The BA should identify the performance measures that are relevant, measurable, achievable, and aligned with the objectives and requirements of the project. The BA shoul d also define the baseline and target values for each performance measure, as well as the data sources and collection methods.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 7: Solution Evaluation, Section 7.1: Measure Solution Performance, p. 307-308

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 7: Solution Evaluation, Section 7.1: Measure Solution Performance, p. 267-268

Before the BA can proceed with any analysis of the features, t hey need to confirm that the feature requests are valid and aligned with the product vision and goals. Customer support calls may not reflect the actual needs and preferences of the target market, and may include requests that are out of scope or inconsist ent with the product strategy. Therefore, the BA should first validate the feature requests with the product owner and other stakeholders, and eliminate any irrelevant or invalid ones.  References :

BABOK Guide v3 , section 7.2.2.1: “The business analyst validates that the requirements and designs are aligned with the business need and the solution scope.”

Guide to building a product roadmap (with template and examples) , section “How to create a product roadmap”: “The first step in creating a product roadmap is to define the product vision. This is the overarching goal or purpose of the product, and it should guide all subsequent decisions and actions.”

The BA presented an opportunity to increase efficiencies by simplifying the process of shipping to new countries and reducing the dependency on IT. By eliminating the need to maintain different variations of ship-to-country and location-to-route for various freight carriers, the BA enabled the business to save time and resources, and avoid potential er rors or delays. This is an examp le of how a BA can add value to the business by identifying and proposing solutions that improve the current state and address the root causes of the problems.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 2: Business Analysis Planning and Monitoring, page 50

Business Analysis Body of Knowledge (BABOK ®) Guide , Version 3, Chapter 6: Solution Evaluation, section 6.5.2: Assess Enterprise Limitations, page 176

Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 4: Business Analysis Planning and Monitoring, Week 2: Plan Business Analysis Approach, video: “Solution Evaluation”

 A purchase solution approach is one that involves acquiring a COTS software package from an external vendor or provider, rather than developing a custom solution in-house. A purchase solution approach can offer several benefits, such as faster delivery, lower cost, higher quality, and reduced risk. Howeve r, a purchase solution approach also has some drawbacks, such as limited customization, dependency on the vendor, compatibility issues, and licensing fees. A BA should evaluate the pros and cons of a purchase solution approach against the business needs an d requirements, and compare it with other possible solution approaches, such as outsource, exploit, or create.  References :

Evaluating Candidate COTS Packages , ArgonD igital

Seven Insights: Agile and Custom Off The Shelf (COTS) packaged software , Kenny & Company

COTS Software Procurement Methodology , IGI Global

 In order to gain consensus between the CFO and other management, the BA could estimate the potential value delivered by each option and present the results to the stakeholders. This would involve assessing the benefits, costs, and risks of each option, as well as the alignment with the strategic objectives and customer needs. By estimating the value, the BA could help the stakeholders understand the trade-offs and implications of each option, and facilitate a rational and informed decision-making process.  References :

IIBA BABOK Guide , Section 9.4, Evaluate Solution Options

How to Estimate the Value of a Business Analysis Solution , Bridging the Gap

Business Analysis Techniques: Estima ting Value , Business Analyst Learnings