CBAP Exam Dumps : Certified Business Analysis Professional

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

 A data dictionary is a technique that is used to define the data elements of a system or a domain. It provides detailed information about the attributes of each data element, such as name, description, type, format, length, range, default value, validation rules, relationships, and constraints. A data dictionary helps to ensure a common understanding of the data elements among the stakeholders and to maintain consistency and accuracy in the data usage and manipulation. A data dictionary can be used to complement a class diagram, which is a graphical representation of the classes and their associations in an object-oriented system or domain. References: The answer can be verified from the following sources:

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide) Version 3, Chapter 9: Data Modeling, p. 326-331; Chapter 10: Data Dictionary, p. 332-335.

Business Analysis for Practitioners: A Practice Guide, Chapter 5: Requirements Analysis and Design Definition, p. 123-124, 129-130.

Prioritizing requirements is a process that helps business analysts and stakeholders to rank the requirements according to their importance, value, urgency, and dependency. Prioritizing requirements helps to ensure that the most critical requirements are addressed first, and that the available resources are allocated effectively. Prioritizing requirements also helps to manage the scope, schedule, and budget of the project, and to deal with changes and uncertainties. Prioritizing requirements is not only about determining the cost or the schedule of each requirement, but also about understanding the impact and the benefit of each requirement on the business need and the solution. Prioritizing requirements is not only about identifying the risks associated with each requirement, but also about mitigating or avoiding those risks by choosing the best solution option. References:

[A Guide to the Business Analysis Body of Knowledge (BABOK Guide)], version 3, page 402, section 10.31.3.11

Why Prioritise Requirements – How to do it and Why it is Critical to Project Success – BusinessAnalystMentor.com, paragraph 1

Why You Should Prioritize Requirements - ArgonDigital, paragraph 1

What Is Requirements Prioritization? Definition & Examples - airfocus, paragraph 1

Business analysts : How to prioritize requirements - Adaptive US, paragraph 1