IIBA CBAP Exam Dumps

An entity relationship diagram (ERD) is a graphical representation of how entities and relationships are organized in a database or a system. An ERD consists of three main components: entities, attributes, and relationships. Entities are the objects or concepts that store data, such as customers, products, or orders. Attributes are the properties or characteristics of entities, such as name, price, or quantity. Relationships are the associations or connections between entities, such as one-to-one, one-to-many, or many-to-many. Forks are not a component of an ERD, but rather a symbol used to represent a relationship type. A fork indicates that a relationship is either one-to-many or many-to-many, depending on the direction of the fork. For example, a fork pointing from an entity A to an entity B means that one instance of A can be related to many instances of B, while a fork pointing from an entity B to an entity A means that many instances of B can be related to one instance of A.Reference:

ER Diagram (ERD) - Definition & Overview | Lucidchart, paragraph 1-2

A Guide to the Entity Relationship Diagram (ERD) - Database Star, paragraph 1-2

ERD Templates | ER Diagram Examples | Moqups, paragraph 1

What is an Entity Relationship (ER) Diagram - Creately, paragraph 1

Components of an ER Diagram - TAE - Tutorial And Example, paragraph 1-2

An activity network diagram is a method of displaying the timelines of all the various subtasks that are involved in any project. It shows the sequence and dependencies of the subtasks, as well as their durations and start and finish times. An activity network diagram can help to identify the critical path, which is the longest path of subtasks that determines the minimum time required to complete the project. An activity network diagram can also help to monitor and control the project progress, identify and manage risks, and optimize the use of resources.Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, page 47

Critical Path Mapping with Activity Network Diagrams

How To Create a Project Timeline in 8 Easy Steps, under Step 4: Choose a project timeline format

The BA should provide process models as artifacts that can be used organization wide for the long-term. Process models are graphical representations of the activities, inputs, outputs, and interactions of a business process. They can help to document, analyze, improve, and communicate the current and future states of a process. They can also serve as a basis for developing other artifacts, such as requirements, test cases, user manuals, and training materials. Process models can be useful for various stakeholders, such as business users, managers, developers, testers, and trainers, to understand and optimize the business process.Reference:

CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Chapter 6: Requirements Analysis and Design Definition, Section 6.4: Model and Validate Requirements, p. 263-264

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. 159-160

A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 3, Chapter 9: Solution Evaluation, Section 9.5: Assess Organizational Readiness, p. 261-262

In the context of risk assessment, the impact of a risk is often calculated by multiplying the Probability of Occurrence (POC) with the Cost of Impact. For each risk in this scenario:

Natural disasters: 0.2 * 15,000 = 3,000

Power surges: 0.5 * 20,000 = 10,000

Human errors: 0.9 * 3,000 = 2,700

System security: 0.4 *16,000 =6,400

Power surges have the highest negative impact to value at $10,000.

MoSCoW is an acronym for Must-have, Should-have, Could-have, and Won't-have this time. It is a prioritization technique that many organizations use in project management, software development, business analysis, etc., to categorize and prioritize requirements or tasks based on their importance and urgency.The method provides a simple and effective way to prioritize work items by assigning them to one of the four categories12:

Must-have: These are the critical and non-negotiable requirements or tasks that must be completed for the project or product to be successful. Without them, the project or product will fail or become useless. For example, compliance with legal or security standards, or core functionality of the product.

Should-have: These are the important but not essential requirements or tasks that should be completed for the project or product to be satisfactory. They add significant value or benefit, but they are not as time-sensitive or critical as the must-haves. They can be postponed or omitted without compromising the project or product. For example, performance improvements, minor bug fixes, or nice-to-have features.

Could-have: These are the desirable but not necessary requirements or tasks that could be completed for the project or product to be enhanced. They improve the user experience or customer satisfaction, but they have a low impact or benefit. They can be included if time and resources permit, or they can be left out without affecting the project or product. For example, aesthetic changes, extra functionality, or user feedback.

Won't-have: These are the least important or relevant requirements or tasks that won't be completed for the project or product at the current time. They have a low or negative impact or benefit, or they are not appropriate or feasible at the moment. They can be excluded, deferred, or reconsidered for future projects or products. For example, out-of-scope requests, low-priority issues, or unrealistic expectations.

MoSCoW prioritization helps to manage the expectations and needs of the stakeholders, and to focus on the most valuable and urgent work items. It also helps to deal with changing requirements, scope creep, and resource constraints.MoSCoW prioritization is often used with timeboxing, which is a technique that sets a fixed deadline for the completion of a project or product34.Reference:

What is MoSCoW Prioritization? | Overview of the MoSCoW Method

MoSCoW method - Wikipedia

Simplify Requirement Prioritization With the MoSCoW Method - Geekflare

MoSCoW: Framework for Effective Prioritization | craft.io

Topic 2, Exam Pool B