Comprehensive and Detailed Since the project hasstrict regulatory requirements and an

unchangeable deadline, aPredictive Development Processis the best approach. TheBABOK® Guide

(Chapter 3.1 - Plan Business Analysis Approach)states that apredictive approach (Waterfall) is used

for projects with well-defined scope, regulatory compliance needs, and fixed deadlines. This ensures

that the project is deliveredon time and within regulatory constraints.

Comprehensive and Detailed The best approach is toanalyze the current business process to identify

inefficiencies and control failuresbefore considering new solutions. TheBABOK® Guide (Chapter 10.5

- Process Modeling)states that business process analysis helps in diagnosingroot causes of

inefficiencies, ensuring thatautomation or system changes address the real issue.

Comprehensive and Detailed ABusiness Process Modelis the most appropriate viewpoint to walk

stakeholders through the structure of requirements. It visually represents business processes, the

sequence of activities, and how various components interact. This allows stakeholders to

understandhow requirements are structuredand relate to business operations. TheBABOK® Guide

(Chapter 10.5 - Process Modeling)highlights that business process models help in analyzing process

improvements and ensuring stakeholders comprehend the workflows.

Comprehensive and Detailed TheGovernance Approachdefinesdecision-making authorities,

escalation paths, and approval responsibilities. TheBABOK® Guide (Chapter 3.4 - Plan Business

Analysis Governance)states that governance ensuresstructured management of changes, ensuring

that compliance-related requirements receive proper approval.

The deliverable that will facilitate understanding between IT and the business stakeholders is a data

dictionary. This is because a data dictionary is a document that defines and describes the data

elements, attributes, properties, formats, relationships, rules, etc. of a data-centric solution. A data

dictionary can help to facilitate understanding between IT and the business stakeholders by providing

a common language and reference for the data requirements and specifications. The other options

are not as effective or suitable as a data dictionary. Reference:

BABOK Guide, section 10.9: Data Dictionary

CCBA Practice Test,

According to the BABOK® Guide, one of the principles of effective communication is to use a

common language that is understood by all stakeholders. Technical jargon and models can create

confusion and misunderstanding among stakeholders who are not familiar with them. Therefore, the

business analyst (BA) should represent design models using common terminology that is clear and

unambiguous for all stakeholders. This will improve the understanding and verification of

requirements on the project. Reference: BABOK® Guide, Version 3, Chapter 10: Techniques, Section

10.1: Acceptance and Evaluation Criteria Definition, Page 372; Chapter 3: Business Analysis Planning

and Monitoring, Section 3.4: Plan Business Analysis Communication, Page 38.

The BA should select CRUD (Create, Read, Update, and Delete) matrix as the technique that would

be appropriate for determining how and who uses data across the identified processes. CRUD matrix

is a table that shows the actions that different roles or stakeholders can perform on data entities or

objects within a system or solution. CRUD matrix can help to define the data access rights and

permissions for each role or stakeholder, as well as the data dependencies and interactions among

processes.

The other options are incorrect because:

Option A is incorrect because stakeholder list, map, or personas are not techniques for determining

how and who uses data, but techniques for identifying and analyzing stakeholders. Stakeholder list,

map, or personas are tools that provide information about the characteristics, needs, expectations,

and influences of stakeholders. Stakeholders are individuals or groups who have an interest or stake

in a change or solution.

Option B is incorrect because data dictionary is not a technique for determining how and who uses

data, but a technique for defining and describing data. Data dictionary is a repository that contains

the definitions, attributes, formats, and relationships of data elements or objects within a system or

solution. Data dictionary can help to standardize and document the data requirements and

specifications for a solution.

Option D is incorrect because decision model is not a technique for determining how and who uses

data, but a technique for modeling and analyzing decisions. Decision model is agraphical

representation of the logic, rules, criteria, and outcomes of decisions within a system or solution.

Decision model can help to simplify and clarify the decision-making process and its impact on the

solution.

Reference:

BABOK Guide v3, section 10.16: CRUD Matrix

CCBA Practice Test,

Quantitative performance measure is being practiced by the software development company that

evaluates solutions against the number of defects reported in the testing phase. Quantitative

performance measures are those that use numerical values or statistics to assess the performance of

a solution or an organization. They can help to measure aspects such as quality, efficiency,

productivity, profitability, customer satisfaction, etc. The number of defects is a quantitative measure

of quality that indicates how well a solution meets its specifications and

expectations. Reference: : Quantitative Performance Measures

Baseline requirements are the set of requirements that have been formally reviewed and agreed upon by the stakeholders. They serve as a reference point for the development and testing of the solution, as well as for the evaluation of the benefits and value delivered by the solution. Baseline requirements are not final or fixed; they can be changed if there is a valid reason and a proper approval process. Any changes to the baseline requirements must be documented and communicated to the relevant stakeholders, and they must follow a change control system that defines the roles, responsibilities, procedures, and tools for managing changes. Reference: The information is aligned with the competencies and knowledge areas defined in the Business Analysis Body of Knowledge® (BABOK® Guide) and the Certification of Capability in Business Analysis™ (CCBA®) as provided by the International Institute of Business Analysis (IIBA®). For detailed

, please consult the CCBA® guide1 and the BABOK® Guide2 available through the

IIBA® website and bookstore3. You can also find some useful resources and sample questions from

other sources45.

In the context of project risks, particularly for the implementation of a new web portal, the potential

inadequacy of the current infrastructure to support increased performance is a significant concern.

This is because if the infrastructure is not capable of handling the enhanced demands of the new

system, it could lead to performance issues, system downtime, or even failure, which would

negatively impact the project’s success.

Reference: The CCBA® certification emphasizes the importance of identifying and evaluating

opportunities for better business outcomes, which includes assessing risks that could hinder these

outcomes123. The IIBA’s BABOK® Guide is a key resource for understanding the tasks and techniques

associated with business analysis, including risk assessment4.