CCBA Exam Dumps - IIBA Certification of Capability in Business Analysis Questions and Answers

According to the BABOK Guide, a user interactions viewpoint focuses on how stakeholders interact with a solution or a product to achieve their goals1. This viewpoint can help the BA structure the requirements to ensure realization of the desired customer experience, as it describes the features, functions, and interfaces that enable users to perform their tasks effectively and efficiently2. Therefore, the correct answer is A. References: BABOK Guide, CCBA Exam Questions

 The BA must create merged viewpoints of the requirements to address the concerns of the CEO. This is because a merged viewpoint is a way of combining the perspectives of different stakeholders into a coherent and consistent set of requirements. A merged viewpoint can help to resolve conflicts, identify gaps, and ensure alignment among the stakeholders. Creating merged viewpoints can also help to integrate and service the two client bases in the newly formed company after a merger. The other options are not sufficient or relevant to address the CEO’s concerns. References:

BABOK Guide, section 4.3.2: Validate Requirements

CCBA Practice Test, question 100

 The type of requirements organization that Ben is doing in this scenario is functional decomposition. This is a technique for breaking down a complex system or process into its constituent parts and describing their functions and interactions12. By taking the laser printer apart and identifying each component’s purpose, Ben is applying functional decomposition to understand the structure and behavior of the system. The other options are not types of requirements organization, but rather techniques for modeling different aspects of the system or process, such as the flow of activities (B), the boundaries and deliverables ©, or the data elements and relationships (D)3. References: Certification of Capability in Business Analysis™ (CCBA®), CBAP / CCBA Certified Business Analysis Study Guide, 2nd Edition, Business Analysis Expert Certification, CCBA® | IIBA®

 A business capability analysis is a technique that identifies and evaluates the capabilities of an organization that are required to achieve its strategic objectives. A business capability is a combination of people, processes, information, and technology that enables the organization to perform a specific function. A business capability analysis helps to understand the current state and the desired future state of the organization, and to identify the gaps and opportunities for improvement. A business capability analysis can be represented by a matrix that maps the capabilities to the strategic goals, the value streams, the stakeholders, and the requirements.References:

BABOK Guide v3, section 2.2: Conduct Stakeholder Analysis

CCBA Exam Questions, question 24

Item tracking methods are techniques to monitor and control the status of items such as issues, defects, changes, or action items. They help to manage and resolve the outstanding issues that have been logged in an issues register. Requirements documentation, requirements analysis, and metrics and KPIs are not techniques for managing and resolving issues. References: BABOK Guide v3, page 387; CCBA Mock Test, question 13

 The correct answer is D. The BA will be ensuring that the performance measures align with other measures within the broader context of the solution. This means that the performance measures are consistent with the business goals, objectives, and strategies of the organization and the stakeholders. The performance measures should also be aligned with the expected benefits and outcomes of the solution. This will help to evaluate the effectiveness and efficiency of the solution and its impact on the business value.

The other options are incorrect because:

Option A is incorrect because performance measures can be both qualitative and quantitative, depending on the nature and scope of the solution and the stakeholder needs. Qualitative measures are based on subjective judgments, opinions, or perceptions, while quantitative measures are based on numerical data, statistics, or calculations.

Option B is incorrect because aligning performance measures to industry benchmarks is not a validation technique, but a comparison technique. Industry benchmarks are standards or best practices that can be used to compare or evaluate the performance of a solution against similar solutions in the same domain or sector. However, industry benchmarks may not reflect the specific needs and expectations of the stakeholders or the organization.

Option C is incorrect because writing performance measures in the correct format, using the agreed standards and terminology, is not a validation technique, but a documentation technique. The format and language of performance measures should be clear, concise, and consistent, but they do not guarantee that the performance measures are relevant, feasible, or reliable.

References:

BABOK Guide v3, section 7.6: Validate Requirements

CCBA Practice Test, question 9

A. Supporting training activities and knowledge management: This is a correct objective of specifying and modeling requirements, as it helps to document and share the knowledge and information that are needed to understand, implement, and use the solution. Specifying and modeling requirements also helps to create training materials and guides for the end-users and other stakeholders who will interact with the solution.

B. Facilitating communication among stakeholders: This is a correct objective of specifying and modeling requirements, as it helps to convey the needs, expectations, and preferences of the stakeholders in a clear, consistent, and unambiguous way. Specifying and modeling requirements also helps to resolve conflicts, negotiate trade-offs, and reach agreements among the stakeholders who have different perspectives and interests.

C. Compliance with contracts and regulations: This is a correct objective of specifying and modeling requirements, as it helps to ensure that the solution meets the legal, ethical, and contractual obligations and standards that are applicable to the project and the organization. Specifying and modeling requirements also helps to identify and mitigate the risks and issues that may arise from non-compliance or violation of the contracts and regulations.

D. Increasing revenue and/or reducing costs within an organization: This is an incorrect objective of specifying and modeling requirements, as it is not directly related to the business analysis tasks, but to the business objectives and benefits of the solution. Specifying and modeling requirements helps to define the scope, features, and quality of the solution that will address the business problem or opportunity, but it does not guarantee that the solution will increase the revenue or reduce the costs within the organization. The actual impact of the solution on the organization’s performance and profitability depends on many other factors, such as the market demand, the customer satisfaction, the operational efficiency, the competitive advantage, etc.

The BA should consider the number of systems being affected by the requirement when performing an impact analysis of this change. This is because an impact analysis is a technique that involves assessing the potential effects of a change on the existing or proposed solution, business processes, stakeholders, or organization. The number of systems being affected by the requirement is an important factor that can influence the feasibility, cost, risk, and complexity of implementing the change. The other options are not as relevant or significant as considering the number of systems being affected by the requirement. References:

BABOK Guide, section 10.16: Impact Analysis

CCBA Practice Test, question 104

To answer this question, you need to compare the total cost of ownership (TCO) of the two solutions over time. The TCO is the sum of the initial cost and the recurring cost multiplied by the number of months. You can set up an equation to find the break-even point where the TCO of the two solutions are equal:

286,000 + 2,400x = 239,000 + 2,850x

Solving for x, you get x = 64. This means that after 64 months, the TCO of the two solutions will be the same. Therefore, you need to use your in-house solution for more than 64 months to be more cost effective than the vendor’s solution.

References:

Business Analysis Expert Certification, CCBA® | IIBA®, section “Business Analysis Planning and Monitoring”, subsection “Plan Business Analysis Approach”.

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

Survey or QUESTION NO:naire presents a set of Questions to stakeholders and subject matter experts (SMEs), whose responses are then collected and analyzed in order to formulate knowledge about the subject matter of interest. The Questions can be submitted in written form or can be administered in person, over the telephone, or using technology that can record responses.

According to the BABOK® Guide, non-functional requirements analysis is a technique that is used to examine and group requirements that describe the quality attributes of a solution, such as efficiency, capacity, security, and scalability. Non-functional requirements analysis helps to ensure that the solution meets the expected standards of performance, reliability, usability, and maintainability. Non-functional requirements analysis also helps to identify trade-offs and dependencies among different quality attributes. References: BABOK® Guide, Version 3, Chapter 10, Section 10.32; Business Analysis Expert Certification, CCBA® | IIBA®, Section “What Should I know to be CCBA Certified?”

According to the Capability in Business Analysis™ (CCBA®) guidelines, a derive traceability relationship is one where a requirement is derived from another requirement, typically from a higher level to a lower level12. A functional requirement to provide a user login screen is an example of a derived requirement, as it is derived from a stakeholder requirement for an online system. A derived requirement is not explicitly stated by the stakeholder, but is necessary to satisfy the stakeholder requirement.

References: The CCBA® learning documents, which can be found on the IIBA website12, describe the various types of traceability relationships that a business analyst can use to understand and manage the requirements, including the derive relationship. Additionally, the IIBA Bookstore offers resources that provide further insights into the objectives and best practices for business analysis, including the use of traceability matrix345.

This is because a process model is a visual representation of the activities, inputs, outputs, and roles involved in a business process. Swimlanes are horizontal or vertical partitions that show the responsibilities of different actors or units in the process. By using a process model with swimlanes, the BA can compare the stakeholder’s inputs against each other and identify any gaps, overlaps, or inconsistencies in the process flow. Scheduling a follow-up workshop (A) is not a technique, but a possible action that may or may not help to resolve the issue. Creating a use case scenario (B) is not a suitable technique, as it describes the interactions between a user and a system, not a business process. Creating a logical data model (D) is not a relevant technique, as it shows the relationships and attributes of the data entities, not the business process. References: CCBA Practice Test, CCBA Mock Test

According to the BABOK Guide, elicitation scope is the set of information that needs to be discovered or confirmed through elicitation activities3. Understanding the elicitation scope can assist the BA with the elicitation activity by determining when elicitation is complete4. This means that the BA can stop eliciting information when he or she has obtained enough information to meet the elicitation scope. This can help avoid over-elicitation or under-elicitation of information. References: BABOK Guide, CCBA Practice Test

Use cases and scenarios are techniques that allow the BA to model the requirements based on the user roles, functionality, and interaction with the solution. Use cases describe the goals, actions, and outcomes of the users in relation to the solution, while scenarios provide examples of how the use cases can be executed in specific situations. Use cases and scenarios help to illustrate the behavior and functionality of the solution from the user’s perspective, as well as the potential variations and exceptions.

References: The answer and explanation are consistent with the CCBA® Handbook and the IIBA® website, which provide the details and best practices for the use cases and scenarios techniques as part of the business analysis process12. The CCBA® resources also describe the types and formats of models that can be used to specify and model requirements, such as use case models and scenario models