CCBA Exam Dumps : Certification of Capability in Business Analysis (CCBA)

A model is a representation of a concept or system that is used to help people understand, change, or simulate the concept or system. A model can be used to categorize and create hierarchies of items, define boundaries for business domains, and show business logic, among other purposes. However, a model cannot define the risk and reward for the requirements, as this is a function of the business analysis approach and the risk management process. References:

BABOK Guide v3, Section 10.1: Models and Modelling, p. 381-382

CCBA Handbook, Section 4.5: Exam Blueprint, p. 6-7

CCBA Competencies, Section 10.1: Models and Modelling, p. 23-24

Risk-averse means having a low tolerance for risk and preferring to avoid uncertainty or potential losses. This describes the company’s attitude toward risk, as they do not want to experiment with new flavors that might affect their sales. Risk-neutral means being indifferent to risk and basing decisions on expected outcomes. Risk-optimizing means having a high tolerance for risk and seeking opportunities for reward. Risk-soaking means being willing to accept losses or negative consequences of risk. References: BABOK Guide v3, page 12; CCBA Mock Test, question 10

Linked is not a valid relationship type among requirements. Requirements can have different types of relationships, such as derivation, satisfaction, verification, refinement, traceability, dependency, conflict, or overlap1. These relationships can help to analyze the impact, consistency, completeness, and quality of the requirements2. However, linked is not a specific or meaningful term to describe how requirements are related.

The other options are valid relationship types among requirements:

Necessity is a relationship type that indicates that a requirement is essential for achieving a goal or satisfying a need3.

Cover is a relationship type that indicates that a requirement addresses or fulfills a stakeholder need or expectation4.

Subset is a relationship type that indicates that a requirement is a more detailed or specific version of another requirement5.

References:

Relationship Analysis in Requirements Engineering, section “Relationship Types”

A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), version 3, chapter 6, section 6.1.4.1

Necessity, section “Description of Change”

Cover, section “Description of Change”

Subset, section “Description of Change”