Certified Business Analysis Professional CBAP Book

 Data flow diagramming is a technique that shows how data moves through a system, from external entities, through processes, to data stores. Data flow diagrams can be used to model the current state or the desired state of a system, and to identify gaps or redundancies in data processing. Data flow diagrams can also be decomposed to lower levels of detail to show the sub-processes and data elements involved in each function. Functional decomposition, work decomposition, and organization modeling are different techniques that can be used to break down a system, a project, or an organization into smaller components, but they do not focus on the data movement. References:

• BABOK® Guide, p. 10, 98-99
• CBAP / CCBA Certified Business Analysis Study Guide, p. 240-241
• Certified Business Analysis Professional™ (CBAP®) | Coursera, Course 2, Week 2, Video: “Data Flow Diagrams”

Risky requirements are those that have a high probability of causing problems or failures in the project. By addressing them early in the prioritization, the project team can identify and resolve any issues before they affect the rest of the requirements or the projectdeliverables. This way, the project can avoid rework, delays, and cost overruns that may result from risky requirements. References: CBAP / CCBA Certified Business Analysis Study Guide, Chapter 6: Requirements Analysis, page 203. Certified Business Analysis Professional (CBAP®) Handbook, page 6.

A class model is a technique to represent the structure and behavior of the entities within a solution domain. It shows the attributes, operations, and relationships of the classes that define the entities. A class is a category or type of entity that has common characteristics and can perform certain functions. A class model helps to identify the entities, their properties, their behaviors, and their interactions for a solution. Entity Relationship is a technique to represent the data and information requirements of a solution. It shows the entities, attributes, and relationships of the data and information. An entity is a thing or object of interest that can be uniquely identified and has attributes that describe its properties. An entity relationship model helps to identify the data and information, their characteristics, their associations, and their constraints for a solution. Data dictionary is a technique to define and document the data and information elements of a solution. It provides a detailed description of each data and information element, such as its name, definition, format, type, source, owner, and usage. A data dictionary helps to standardize and clarify the data and information, their meaning, their structure, and their quality for a solution. CRUD matrix is a technique to analyze the alignment of the data and information elements with the business processes or functions of a solution. It shows the data and information elements and the business processes or functions that create, read, update, or delete them. A CRUD matrix helps to identify the data and information, their lifecycle, their dependencies, and their gaps for a solution. References: Class Model - iiba.org, Entity Relationship - iiba.org, Data Dictionary - iiba.org, CRUD Matrix - iiba.org

 According to the BABOK® Guide, one of the tasks of defining the business need is to review the requirements stated documentation and ensure that it reflects the actual business requirements, not a description of the solutions. This is important because the business need should be based on the underlying problem or opportunity, not on a predetermined solution. The other options are not relevant to this task. References: BABOK® Guide, v3, p. 30; CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, p. 36.