IIBA Updated CCBA Exam Questions and Answers by tahlia

A. Supporting training activities and knowledge management: This is a correct objective of specifying and modeling requirements, as it helps to document and share the knowledge and information that are needed to understand, implement, and use the solution. Specifying and modeling requirements also helps to create training materials and guides for the end-users and other stakeholders who will interact with the solution.

B. Facilitating communication among stakeholders: This is a correct objective of specifying and modeling requirements, as it helps to convey the needs, expectations, and preferences of the stakeholders in a clear, consistent, and unambiguous way. Specifying and modeling requirements also helps to resolve conflicts, negotiate trade-offs, and reach agreements among the stakeholders who have different perspectives and interests.

C. Compliance with contracts and regulations: This is a correct objective of specifying and modeling requirements, as it helps to ensure that the solution meets the legal, ethical, and contractual obligations and standards that are applicable to the project and the organization. Specifying and modeling requirements also helps to identify and mitigate the risks and issues that may arise from non-compliance or violation of the contracts and regulations.

D. Increasing revenue and/or reducing costs within an organization: This is an incorrect objective of specifying and modeling requirements, as it is not directly related to the business analysis tasks, but to the business objectives and benefits of the solution. Specifying and modeling requirements helps to define the scope, features, and quality of the solution that will address the business problem or opportunity, but it does not guarantee that the solution will increase the revenue or reduce the costs within the organization. The actual impact of the solution on the organization’s performance and profitability depends on many other factors, such as the market demand, the customer satisfaction, the operational efficiency, the competitive advantage, etc.

According to the BABOK® Guide, a requirement is a usable representation of a need. A requirement does not cease to be a requirement once it has been satisfied; it remains a requirement as long as the need exists and the solution is in use. Requirements may change over time due to changes in the business environment, stakeholder needs, or solution performance1. References: 1: BABOK® Guide, version 3, section 3.2.1, page 34.

A vision statement is a document that states the business need, identifies the key stakeholders, and defines the positive impact the solution will bring to the organization and stakeholders. A vision statement provides a high-level description of the desired future state and the value proposition of the solution. It also helps to align the expectations and objectives of the stakeholders and to guide the scope and direction of the project12.

The other options are not correct because:

Requirements documentation is a document that describes the capabilities, features, and qualities of the solution that will meet the stakeholder needs. It does not state the business need or the positive impact of the solution3.

Business case is a document that provides the justification for initiating a project or task. It typically includes the business need, the expected benefits, the costs, the risks, and the alternatives of the proposed solution. It does not identify the key stakeholders or define the positive impact of the solution4.

Project charter is a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It typically includes the project purpose, objectives, scope, deliverables, milestones, roles and responsibilities, budget, and risks. It does not state the business need or the positive impact of the solution5.

References:

Vision Statement, section “Description of Change”

How to Write a Vision Statement for Your Business, section “What is a vision statement?”

Requirements Documentation, section “Description of Change”

Business Case, section “Description of Change”

Project Charter, section “Description of Change”

According to the BABOK® Guide, an assumption is a factor that is considered to be true for the purposes of planning and analysis, but has not been confirmed or proven. Assumptions are used to fill in the gaps of knowledge or uncertainty, and may affect the outcome of the project if they turn out to be false. An example of an assumption is the project manager’s belief that her project team members can program in COBOL, which may or may not be true, and may impact the project’s feasibility, scope, cost, and schedule1. References: 1: BABOK® Guide, version 3, section 10.25, page 336.