Pearson CBAP New Attempt

A model is a representation of a concept or system that is used to help people understand, change, or simulate the concept or system. A model can have various purposes, such as categorizing and creating hierarchies of items, defining boundaries for business domains, and showing business logic. However, a model does not define the risk and reward for the requirements, as this is a function of the business analysis approach and the stakeholder analysis. References:

• CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Business Analysis Planning and Monitoring, p. 133
• BABOK® Guide, Section 9.1: Plan Business Analysis Approach, p. 100
• BABOK® Guide, Section 9.2: Conduct Stakeholder Analysis, p. 104

A horizontal prototype is a type of prototype that focuses on the user interface and the look and feel of the system, without much attention to the functionality or the back-end processes. It is useful for demonstrating the appearance and navigation of the system to the customer and getting feedback on the design. A horizontal prototype is also called a mock-up prototype or a storyboard prototype.

References:

• Certified Business Analysis Professional Handbook, page 19
• Certified Business Analysis Professional Specialization, Course 4, Week 3, Lesson 3.1
• CBAP / CCBA Certified Business Analysis Study Guide, page 261

Change requests are more likely to occur in the early stages of a project, when the requirements 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, market trends, or competitor actions. Change requests are less frequent in the later stages of aproject, 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 Changes1
• CBAP Certification Study Guide v3.0, Chapter 4: Requirements Life Cycle Management, Section 4.5: Manage Changes2

 A business analysis plan is a document that describes the scope of work, the deliverable Work Breakdown Structure (WBS), the activity list, and estimates for the business analysis activities. It also includes the business analysis approach, the roles and responsibilities of the business analyst and other stakeholders, the communication plan, the requirements management plan, the change management plan, and the risk management plan12. Abusiness analysis plan is an important input for the business analysis execution and monitoring process, as it helps to guide and control the business analysis work, and to ensure that the business analysis deliverables meet the quality standards and stakeholder expectations3.

The other options are not correct. A project management plan is a document that describes how the project will be executed, monitored, and controlled. It covers the project scope, schedule, cost, quality, resources, communication, risk, procurement, and stakeholder management. An implementation plan is a document that describes how the solution will be deployed, transitioned, and integrated into the business operations. It covers the implementation strategy, schedule, resources, tasks, roles, responsibilities, risks, and issues. A requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, verified, prioritized, traced, and maintained throughout the project lifecycle. It is a component of the business analysis plan, not a separate document. References:

• Business Analysis Plan - IIBA®
• Business Analysis Planning and Monitoring - IIBA®
• Business Analysis Execution and Monitoring - IIBA®
• [Project Management Plan - PMI]
• [Implementation Plan - PMI]
• [Requirements Management Plan - IIBA®]