The BA should inform the stakeholders that the regulatory requirement takes precedence over other requirements, bec ause it is a mandatory constraint that must be satisfied by the solution. The BA should explain the rationale and implications of the regulatory requirement, and how it affects the other requirements and the solution scope. The BA should also seek to resol ve any conflicts or issues that may arise from the stakeholders, and ensure that they understand and accept the priority of the regulatory requirement. Measuring the value of the other requirements against the penalty of not meeting the regulatory requirem ent, comparing the regulatory requirement to the recommended solution, or determining a means to work around the regulatory requirement are not the best options, because they do not address the root cause of the problem and may result in non-compliance, le gal liability, or stakeholder dissatisfaction.  References :

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition , Chapter 3: Requirements Life Cycle Management, page 122

Business Analysis Body of Knowledge (BABOK) Guide , Version 3, Chapter 3: Requirements Life Cycle Managemen t, section 3.5: Prioritize Requirements, page 62

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 3: Requirements Life Cycle Management, page 122

A resource break down structure (RBS) is a type of chart that shows which resources are needed in the project and allows you to group the resources by project phase or other attributes. A resource is anything that is required to perform the project activities, such as huma n resources, equipment, materials, facilities, etc. A RBS is a hierarchical representation of the resources, where each level represents a category or a subcategory of resources. A RBS helps to plan, allocate, monitor, and control the resources for the pro ject. A RBS also helps to identify the dependencies and constraints among the resources, as well as the potential risks and opportunities related to the resources.  References :  CBAP / CCBA Certified Business Analysis Study Guide , chapter 6, page 237;  CBAP Sample Questions , question 237.

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

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 . 

 A proven and tailored analysis approach is suitable for this project because it allows the business analyst to adapt to the specific needs and context of the project, while leveraging the best practices and standards of the profession. A proven and tailored analysis approach can also accommodate the different cultures, lang uages, regulations, and time zones of the countries involved in the project.  A proven and tailored analysis approach is based on the following principles 1 :

Business analysis is performed in alignment with the organization’s strategy and objectives

Business analysis is driven by stakeholder needs and values

Business analysis is collaborative and iterative

Business analysis is adaptive and responsive to change

Business analysis is supported by effective communication and documentation

Business analysis is guided by ethical and professional conduct

References :

1 : CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 1: Introduction to Business Analysis, page 8 2

2 :  CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition

 The kinesthetic learning approach is a style of learning that involves physical movement, hands-on activities, and experimentation. Kinesthetic learners prefer to learn by doing rather than by reading, listening, or watching. They learn best by experiencing the topic through simulations, role-plays, demonstrations, exercises, or games. They also benefit from freque nt breaks, movement, and feedback. The other statements describe different learning approaches. The learners who learn best by reading and pondering are verbal learners. The learners who learn best by seeing the topic in a model or through storyboards are visual learners. The learners who are not interested in the topic unless they can immediately apply it to their lives or jobs are pragmatic learners.  References :  Learning Styles: The Four Modalities ,  Learning Styles and the Business Analyst ,  Learning Styles and the CBAP Exam

 A request for quote (RFQ) is a procurement form that asks the vendor to provide only a price for a standard or fixed product or service, such as a commercial-off- the-shelf (COTS) solution. An RFQ is used when the requirements are well-defined and there is no need for negotiation or customization. An RFQ is different from a request for proposal (RFP), which asks the vendor to provide a detailed proposal for a comple x or customized product or service, including the price, schedule, approach, and qualifications. An RFQ is also different from a purchase order (PO), which is a formal document that authorizes the purchase of a product or service from a specific vendor. An RFQ is also different from a request for information (RFI), which asks the vendor to provide general information about their products or services, capabilities, or references, without asking for a price or a proposal.  References :  CBAP / CCBA Certified Business Analysis Study Guide , Chapter 9: Solution Assessment and Validation, page 275.  Certified Business Analysis Professional (CBAP®) Handbook , page 6.

Work breakdown structure creation is a technique that can be used to plan and manage the business analysis work, but it is not a technique to specify or model requirements. Organization mode ling, data modeling, and state diagrams are all techniques that can be used to describe different aspects of the requirements, such as the stakeholders, the data, and the behavior of the solution.  References :

CBAP Handbook, page 6, Exam Blueprint, Knowledge Area 4: Requirements Analysis and Design Definition

BABOK Guide, Chapter 10: Techniques, Section 10.1: Acceptance and Evaluation Criteria Definition, Section 10.8: Data Modeling, Section 10.34: State Modeling, Section 10.37: Work Breakdown Structure

 A business analysis communications plan is a document that describes how the business analysis information will be communicated to the stakeholders, including the format, frequency, content, and recipients of the com munication. A business analysis communications plan can help to ensure that the stakeholders are informed, engaged, and satisfied with the business analysis work, and that the business analysis deliverables are validated and approved. A business analysis c ommunications plan is part of the business analysis plan, which is a comprehensive document that covers all aspects of the business analysis approach, activities, and deliverables.  References :  BABOK Guide v3 , page 37;  CBAP / CCBA Certified Business Analysis Study Guide , page 75.

 According to the BABOK® Guide, a risk is “an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives such as scope, schedule, cost, and quality” (p. 10). A risk can have both positive and negative impacts, depending on the perspective of the stakeholders and the objectives of the solution. For example, a risk of adopting a new technology may be that it increases the productivity of the employees (positive) but also requires more trainin g and maintenance (negative). A risk analysis in the business case should consider both the probability and the impact of the risks, as well as the strategies to mitigate or exploit them.  References :  BABOK® Guide , p. 10, 114-115;  Certified Business Analysis Professional™ (CBAP®) | Coursera , Course 3, Week 2, Video: “Risk Analysis and Management”