Free IIBA CBAP Practice Exam with Questions & Answers | Set: 2

Risky requirements are those that have a high probability of causing problems or failures in the project. By addressing them early in the prioritization, the project team can identify and resolve any issues before they affect the rest of the requirements or the project deliverables. This way, the project can avoid rework, delays, and cost overruns that may result from risky requirements. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 6: Requirements Analysis, page 203. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

 An assumption is a factor that is considered to be true, real, or certain for the purpose of planning, analysis, or evaluation, without having absolute proof or evidence. Assumptions are made when there is uncertainty or ambiguity about the future state of the organization or the solution. Assumptions can affect the feasibility, viability, and desirability of the solution, as well as the risks and benefits associated with it. The business analyst must document the assumptions and their characteristics and risks, in case they prove to be invalid or inaccurate, and impact the solution performance or outcome. References: BABOK Guide v3, page 36; CBAP / CCBA Certified Business Analysis Study Guide, page 74.

 Decision analysis is a technique of evaluating the possible outcomes of different alternatives and choosing the best one based on the criteria and preferences of the stakeholders. Decision analysis can be used to assess potential risks that may impact the solution and the cost and benefits associated with it, by using methods such as decision trees, decision tables, or expected value analysis. Decision analysis can help to select the optimal solution that maximizes the value and minimizes the risk for the organization. References: BABOK Guide v3, page 130; CBAP / CCBA Certified Business Analysis Study Guide, page 185.

Enterprise analysis is a knowledge area that covers the activities of identifying and defining business needs and opportunities, and determining feasible solutions to meet the organizational goals and objectives. Enterprise analysis includes the following tasks: define business need, assess capability gaps, determine solution approach, define solution scope, and define business case. Solution performance assessment is not a task of enterprise analysis, but rather a task of solution evaluation, which is another knowledge area that covers the activities of measuring and validating the value delivered by a solution. References: BABOK Guide v3, page 25; CBAP / CCBA Certified Business Analysis Study Guide, page 69.

Implementation subject matter experts are the stakeholders who would need detailed technical interface requirements. These are the people who are responsible for designing, developing, and deploying the solution components that interact with other systems or applications. Technical interface requirements specify the format, structure, protocol, and security of the data exchange between the solution and the external entities. Project manager, regulators, and testers are other types of stakeholders who may need different levels of information related to the requirements, but not necessarily the technical interface details. References:

BABOK® Guide, p. 29, 36, 51, 54

CBAP / CCBA Certified Business Analysis Study Guide, p. 45, 49, 50, 52

Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 1, Week 3, Video: “Stakeholder Analysis”

A change request is not one of the three inputs the business analyst will use as he prepares for requirements elicitation. A change request is a document that proposes a modification to the project scope, schedule, budget, or quality after the project has been initiated. A change request is usually submitted by a stakeholder who wants to add, remove, or change a requirement or a feature of the project. A change request is not an input for preparing for requirements elicitation, but rather an output of the requirements management process12.

The other options are the three inputs the business analyst will use as he prepares for requirements elicitation. They are3:

Solution scope: The solution scope defines the boundaries and features of the solution that will address the business need. It helps the business analyst to focus on the relevant requirements and to avoid scope creep.

Business need: The business need is the problem or opportunity that the project aims to solve or exploit. It aligns with the strategic goals and vision of the organization. It helps the business analyst to understand the purpose and value of the project and to elicit the stakeholder needs and expectations.

Stakeholder list: The stakeholder list identifies and categorizes the people or groups who have an interest or influence in the project. It helps the business analyst to plan the appropriate elicitation techniques, communication methods, and stakeholder engagement strategies.

References:

Change Request - IIBA®

Change Request - PMI

Prepare for Elicitation - IIBA®

A current state domain model is a visual representation of the existing business domain, including the entities, attributes, relationships, and rules that define the current situation. A current state domain model can help identify opportunities for improvement by highlighting the gaps, issues, or inefficiencies in the current domain. A current state domain model can also help validate the solution scope with business and technical stakeholders by providing a common understanding of the current domain and its boundaries. A current state domain model can also help assist stakeholders in understanding the current state by showing the structure and logic of the current domain in a simple and clear way. However, a current state domain model cannot help the business analyst create Pareto charts for process improvement, as Pareto charts are a different type of analysis tool that show the frequency and impact of different types of problems or causes. Pareto charts are not based on the current state domain model, but rather on the data collected from the current processes or activities. References: BABOK Guide v3, page 123; CBAP / CCBA Certified Business Analysis Study Guide, page 181.

 A procurement document is a document that is used to solicit proposals or quotations from potential suppliers or vendors of products or services for a project. A procurement document describes the problem or need, the desired solution, the evaluation criteria, and the contractual terms and conditions. A procurement document can be a request for proposal (RFP), a request for quote (RFQ), a request for information (RFI), or an invitation for bid (IFB). An invitation for bid (IFB) is a type of procurement document that is used to request bids from prospective sellers of products or services. An IFB describes the specifications, quantity, quality, and delivery schedule of the products or services. An IFB invites sellers to submit a sealed bid that indicates the cost of providing the products or services. An IFB is used when the buyer has a well-defined or standard problem or need, and wants to select the lowest bidder among the qualified sellers123. A project work breakdown structure (WBS) is not a procurement document, but a project management document. A WBS is a hierarchical decomposition of the project scope into smaller and manageable components. A WBS defines the deliverables, activities, and tasks that are required to complete the project4. A project charter is not a procurement document, but a project management document. A project charter is a document that formally authorizes the initiation of a project. A project charter defines the purpose, objectives, scope, assumptions, constraints, risks, stakeholders, roles, responsibilities, and authority of the project. A vision document is not a procurement document, but a business analysis document. A vision document is a document that describes the desired future state of a solution. A vision document defines the goals, benefits, features, and scope of the solution. References: CBAP® Handbook, CBAP® Exam Prep Study Guide, Project Management Institute, Project Work Breakdown Structure, [Project Charter], [Vision Document]

 Business rules analysis is a technique used to identify, express, validate, refine, and organize the rules that shape day-to-day business behavior and guide operational business decision making. Business rules are specific, actionable, testable directives that support a business policy. Business rules can relate to access control, policy, calculation, or inference. Business rules should be atomic, explicit, and separated from the process that implements them. References:

IIBA®, 10.9 Business Rules Analysis

Business Rules Analysis — Business Analyst Learnings

Using Business Rules Analysis to Model and Analyze BI Requirements

Business rules analysis – The Functional BA

When the number of stakeholders is too large or dispersed to involve them all in the requirements elicitation process, one possible approach is to use representatives or proxies. These are stakeholders who can act on behalf of a larger group of stakeholders and provide their input, feedback, and approval for the requirements. The representatives should be selected based on their knowledge, experience, authority, and availability. They should also communicate regularly with the group they represent and ensure that their views and needs are accurately reflected. Meeting with a small group of administrative assistants that will serve as representatives for the remaining administrative assistants can help to manage and gather requirements from these 2,400 administrative assistants in an efficient and effective way. References: BABOK Guide v3, page 51; CBAP / CCBA Certified Business Analysis Study Guide, page 159.