What CBAP Questions and Answers feature?

 This question is based on a case study that compares two scenarios for Company C, a software development firm. In Scenario 1, Company C uses a traditional waterfall approach to develop a software product for a client. In Scenario 2, Company C uses an agile approach to develop the same product. The question asks for the increased cost in Scenario 2, which is the difference between the total cost of Scenario 2 and the total cost of Scenario 1. According to the case study, the total cost of Scenario 1 is $1,236,210 and the total cost of Scenario 2 is $1,444,000. Therefore, the increased cost in Scenario 2 is $1,444,000 - $1,236,210 = $207,790. References: The case study is available in the CBAP® Exam Sample Questions and Exam Blueprint document1. The answer is also verified by the CBAP® Exam Answer Key document2. Both documents are accessible from the IIBA® website3.

 A purchase solution approach is one that involves acquiring a COTS software package from an external vendor or provider, rather than developing a custom solution in-house. A purchase solution approach can offer several benefits, such as faster delivery, lower cost, higher quality, and reduced risk. However, a purchase solution approach also has some drawbacks, such as limited customization, dependency on the vendor, compatibility issues, and licensing fees. A BA should evaluate the pros and cons of a purchase solution approach against the business needs and requirements, and compare it with other possible solution approaches, such as outsource, exploit, or create. References:

Evaluating Candidate COTS Packages, ArgonDigital

Seven Insights: Agile and Custom Off The Shelf (COTS) packaged software, Kenny & Company

COTS Software Procurement Methodology, IGI Global

The elicitation technique that the BA should select to enable the customer and the key stakeholders to visualize the final product is prototyping. Prototyping is a technique that involves creating a simplified or partial version of the solution that can demonstrate its features, functions, and appearance. Prototyping can help to elicit, validate, and verify the requirements, as well as to obtain feedback and approval from the stakeholders. Prototyping can also help to reduce the risks, costs, and time of the project by identifying and resolving any issues or gaps before the final implementation of the solution. References:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 167-168

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 4: Elicitation and Collaboration, Section 4.2: Conduct Elicitation, p. 103-104

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model Requirements, p. 161-162