IIBA CCBA Questions Answers

The requirements management and communication knowledge area consists of four tasks: manage solution scope and requirements, manage requirements traceability, maintain requirements for reuse, and prepare requirements package. The outputs of these tasks are:

Traced requirements: These are requirements that are linked to other requirements, design elements, test cases, or other artifacts to ensure alignment and consistency.

Maintained requirements: These are requirements that are updated and stored in a repository for future reference and reuse.

Requirements package: This is a document or a set of documents that contains the requirements and related information for a specific audience, purpose, or point in time.

Communicated requirements: These are requirements that are shared with the relevant stakeholders in an appropriate format and level of detail.

The requirement management plan, on the other hand, is not an output of the requirements management and communication tasks, but an input. The requirement management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, and managed throughout the project. The requirement management plan is created as part of the business analysis planning and monitoring knowledge area.

References: While I cannot reference specific documents, the principles mentioned are in line with the general practices of business analysis as outlined in the Business Analysis Body of Knowledge (BABOK) and other business analysis resources. You can find some relevant web search results for CCBA requirements management and communication outputs below:

Overarching Tasks: Requirements Management and Communication

CERTIFICATION OF CAPABILITY IN BUSINESS ANALYSIS

CCBA Certification | Complete Guide on CCBA Certification - HKR Trainings

CCBA® and CBAP® Certifications Study Guide - Packt Subscription

CCBA Step-by-Step Application Process Guide - IIBA®

Allocating requirements is the process of assigning stakeholder and solution requirements to solution components, releases, and organizational areas. The purpose of this process is to maximize the business value delivered by the solution, by ensuring that each requirement is addressed by the most appropriate component, release, or area. Allocating requirements also helps to manage dependencies, risks, and priorities among requirements. References:

Business Analysis Expert Certification, CCBA® | IIBA®, section “Who can Become a CCBA?”

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, section 6.4 “Allocate Requirements”

When there are relatively few criteria involved in assessing the solution options, it is best to focus on the differences of the solutions, as they are likely to have the most impact on the decision. Focusing on the commonalities, the life cycle costs, or the implementation costs may not provide enough information to distinguish the solutions and select the best one for the business need. References: BABOK Guide v3, section 10.4.3.2; CCBA Handbook, section 5.4.4.3.

According to the IIBA, a data flow diagram is a technique that shows where data comes from, which activities process the data, and if the output results are stored or utilized by another activity or external entity1. A data flow diagram consists of four basic elements2:

Data flow: A data flow is a line that represents the movement of data from one point to another. It can be labeled with the name or description of the data.

External entities: External entities are rectangles that represent the sources or destinations of data outside the system boundary. They can be people, organizations, systems, or devices that interact with the system.

Data process: A data process is a circle that represents a process that transforms data by performing some operation on it. It can be labeled with the name or description of the process.

Data store: A data store is an open-ended rectangle that represents a place where data is stored or retrieved. It can be a database, a file, a queue, or a memory.

Among these elements, the one that represents a process that transforms data by combining it with other data is concatenation. Concatenation is a type of data process that joins two or more data flows into one data flow. For example, a concatenation process can combine the first name and last name data flows into a full name data flow3. References:

1: BABOK Guide, section 10.13 Data Flow Diagrams, page 402

2: CCBA® and CBAP® Certifications Study Guide, section Data flow diagrams, page 1

3: Data Flow Diagram Symbols, Types, and Tips, section Data Flow Diagram Symbols, page 1