IIBA Updated CBAP Exam Questions and Answers by luka

A non-negotiable demand by a stakeholder during the requirements prioritization session is one that does not allow for any trade-offs, compromises, or alternatives. It is a demand that must be met regardless of the impact on other requirements, the feasibility of the solution, or the value to the organization. A stakeholder who insists that all requirements are ranked as high is making a non-negotiable demand, as this would prevent any meaningful prioritization and allocation of resources. Communication, cost-benefits ratio, and cost are not non-negotiable demands, as they can be negotiated,adjusted, or balanced with other factors during the requirements prioritization session. References: BABOK Guide v3, section 10.25 Requirements Prioritization; 1

Before making a presentation about the requirements for a large software development project, Gary should determine an appropriate format for the presentation. This means he should consider the following factors:

• The audience: Who are the stakeholders that will attend the presentation? What are their roles, interests, and expectations? How familiar are they with the project and the requirements? How much detail do they need to understand the requirements?
• The purpose: What is the goal of the presentation? Is it to inform, persuade, or seek feedback from the stakeholders? What are the key messages and takeaways that Gary wants to convey?
• The time: How much time does Gary have to present the requirements? How can he allocate the time effectively to cover the most important and relevant aspects of the requirements?
• The tools: What tools and resources does Gary have to create and deliver the presentation? Does he have access to a projector, a laptop, a microphone, or a whiteboard? What software or applications does he need to use to create the presentation slides or documents?
• The style: How can Gary make the presentation engaging, clear, and professional? What visual aids, diagrams, charts, or examples can he use to illustrate the requirements? How can he use colors, fonts, images, and animations to enhance the presentation? How can he structure the presentation to have a logical flow and a strong introduction and conclusion?

By determining an appropriate format for the presentation, Gary can ensure that he communicates the requirements effectively and efficiently to the stakeholders, and that he addresses their needs and concerns.

References:

• How to Make Interesting Presentations for Software Projects, paragraphs 1-3
• How To Write The Software Development Project Brief, steps 1-7
• Complete Guide to Software Development Requirements, paragraphs 1-2

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 requirements during the allocate requirements process. The purpose of allocating requirements to solution components is to ensure that each requirement is fulfilled by one or more solution components, and that each solution component contributes to one or more requirements123.

Assessment of proposed solution is not a solution component, but a technique that evaluates the feasibility, desirability, and suitability of a solution option. Assessment of proposed solution is used during the enterprise analysis process, which involves defining thebusiness need, assessing the capability gaps, determining the solution approach, defining the solution scope, and defining the business 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 dependencies that may affect the solution delivery456. 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 Traceability7 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

Total cost of ownership (TCO) is a financial estimate that helps consumers and enterprise managers determine direct and indirect costs of a product or system. TCO goes beyond the initial purchase price or implementation cost to consider the full cost of an asset over its useful life. It is a key concept in the business analysis tasks of enterprise analysis and solution assessment and validation. TCO can help evaluate the feasibility and viability of different solution options and compare them with the business need and expected benefits. References:

• IIBA BABOK Guide v3, p. 30, 176, 264
• CBAP 150 Practice Questions Flashcards, Question 1
• Production Costs: What They Are and How to Calculate Them - Investopedia
• Cost of Solution vs. Cost of Problem · Jens Oliver Meiert