Pass the IIBA Certification of Capability in Business Analysis CCBA Questions and answers with ExamsMirror

Dependencies are the relationships between requirements that indicate that one requirement is contingent on another requirement. Dependencies can affect the feasibility, value, and risk of the requirements, and therefore, they should be taken into account when prioritizing the requirements. The business analyst should identify and document the dependencies between the requirements, and analyze how they impact the project scope, schedule, and budget. The business analyst should also communicate the dependencies to the business owner and other stakeholders, and help them to prioritize the requirements based on the dependencies and the business objectives.References: BABOK Guide v3, page 156; CCBA Mock Test, question 7

The requirement viewpoint that will help the BA provide information on how requirements are structured is the business process model. A business process model is a graphical representation of the activities, events, flows, and roles that are involved in a business process. A business process model can help the BA to structure the requirements in terms of inputs, outputs, triggers, and outcomes of a business process.

The other options are incorrect because:

Option A is incorrect because a state model is not a requirement viewpoint that will help the BA provide information on how requirements are structured, but a requirement viewpoint that will help the BA provide information on how an entity or an object changes its state or behavior in response to events or conditions. A state model is a graphical representation of the states, transitions, and actions of an entity or an object within a system or solution.

Option B is incorrect because a business capability analysis is not a requirement viewpoint that will help the BA provide information on how requirements are structured, but a requirement viewpoint that will help the BA provide information on what an organization needs or wants to achieve its goals or outcomes. A business capability analysis is a technique that identifies and evaluates the capabilities or skills that enable an organization to perform its functions or processes.

Option D is incorrect because data streams are not a requirement viewpoint that will help the BA provide information on how requirements are structured, but a requirement viewpoint that will help the BA provide information on how data flows and transforms within a system or solution. Data streams are sequences or patterns of data that are produced or consumed by a system or solution.

References:

BABOK Guide v3, section 10.8: Business Process Modeling

CCBA Exam Questions, question 20

The BA should review the use case scenarios after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Reviewing the use case scenarios means verifying and validating that they are accurate, complete, clear, consistent, and aligned with the stakeholder needs and expectations. Reviewing the use case scenarios can help to ensure the quality and correctness of the requirements.

The other options are incorrect because:

Option A is incorrect because identifying all the roles and responsibilities is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Identifying all the roles and responsibilities means defining and documenting the functions or duties that stakeholders perform within an organization or a project. Identifying all the roles and responsibilities can help to engage and collaborate with the relevant stakeholders.

Option C is incorrect because conducting a requirements workshop is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Conducting a requirements workshop means facilitating a structured session with stakeholders to elicit, analyze, communicate, or validate requirements. Conducting a requirements workshop can help to gather information from multiple stakeholders in an interactive way.

Option D is incorrect because creating acceptance criteria is not an action that the BA takes after eliciting requirements from end users for a new application, and then completing a set of use cases and use case scenarios. Creating acceptance criteria means defining and documenting the conditions or standards that must be met by a solution to be accepted by stakeholders. Creating acceptance criteria can help to evaluate the performance and value of the solution.

References:

BABOK Guide v3, section 10.46: Use Cases

CCBA Exam Questions, question 22

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.

References:

BABOK Guide v3, section 10.16: CRUD Matrix

CCBA Practice Test, question 5

The task that the BA must complete before preparation of the elicitation process can begin is collecting information on the business need. This means that the BA should gather relevant data or facts that describe or justify why a change is required or desired by stakeholders or an organization. Collecting information on the business need can help the BA to understand and define the scope, objectives, and benefits of a project or an initiative.

The other options are incorrect because:

Option A is incorrect because coordinating meeting logistics is not a task that the BA must complete before preparation of the elicitation process can begin, but a task that the BA performs during preparation of the elicitation process. Coordinating meeting logistics means arranging and confirming the details of the meeting such as date, time, location, agenda, participants, etc.

Option B is incorrect because approving anticipated expenses is not a task that the BA must complete before preparation of the elicitation process can begin, but a task that the BA performs after preparation of the elicitation process. Approving anticipated expenses means obtaining authorization or consent for the expected costs or resources required for the elicitation process.

Option C is incorrect because gathering contact information of stakeholders is not a task that the BA must complete before preparation of the elicitation process can begin, but a task that the BA performs during preparation of the elicitation process. Gathering contact information of stakeholders means collecting and documenting the names, roles, communication channels, and availability of the stakeholders who will be involved in the elicitation process.

References:

BABOK Guide v3, section 4.1: Plan Elicitation

CCBA Exam Questions, question 28

Sample size is the number of observations or data points that are used to measure the performance of a solution. Sample size is an important consideration for the BA to obtain reliable and valid information, as it affects the accuracy, precision, and confidence of the results. A larger sample size can reduce the sampling error and increase the representativeness of the population, but it may also increase the cost and time of data collection. A smaller sample size can save resources and time, but it may also introduce bias and uncertainty in the results. Therefore, the BA should determine the appropriate sample size based on the purpose, scope, and quality criteria of the performance measurement12. The other options are not directly related to the data collection process, although they may influence the analysis and interpretation of the data. References:

1: BABOK® Guide v3, Chapter 7: Solution Evaluation, Section 7.3: Analyze Performance Measures

2: Business Analysis Expert Certification, CCBA® | IIBA®

The requirement classification schema that this requirement belongs to is nonfunctional requirements. Nonfunctional requirements are statements of conditions or restrictions on a solution or its components that affect its quality, performance, usability, reliability, security, etc. Nonfunctional requirements specify how well a solution should perform or behave.

The other options are incorrect because:

Option B is incorrect because stakeholder requirements are not a requirement classification schema, but a requirement type. Stakeholder requirements are statements of needs, expectations, preferences, or problems of stakeholders or an organization.

Option C is incorrect because transitional requirements are not a requirement classification schema, but a requirement type. Transitional requirements are statements of capabilities or conditions that enable a solution to transition from its current state to its desired future state.

Option D is incorrect because functional requirements are not a requirement classification schema, but a requirement type. Functional requirements are statements of features, functions, or behaviors of a solution or its components that enable it to provide value to stakeholders.

References:

BABOK Guide v3, section 6.1: Specify and Model Requirements

CCBA Exam Questions, question 35

 The element of stakeholder management that the BA is performing when negotiating and resolving conflict with stakeholders to ensure they participate in required BA activities is gaining agreement on commitments. This means that the BA is establishing consensus or acceptance among stakeholders regarding their roles, responsibilities, expectations, deliverables, and timelines for a project or a solution. The BA is also addressing any differences or disputes among stakeholders that may hinder their participation or collaboration.

The other options are incorrect because:

Option A is incorrect because confirming elicitation results is not an element of stakeholder management, but an element of elicitation. Confirming elicitation results means verifying and validating that the information gathered from stakeholders during elicitation activities is accurate, complete, clear, and consistent.

Option C is incorrect because monitoring stakeholder engagement is not an element of stakeholder management, but an element of stakeholder analysis. Monitoring stakeholder engagement means assessing and tracking the level of involvement, interest, influence, and impact of stakeholders throughout a project or a solution.

Option D is incorrect because planning stakeholder engagement is not an element of stakeholder management, but an element of stakeholder analysis. Planning stakeholder engagement means defining and documenting the strategies, methods, and activities for engaging and communicating with stakeholders.

References:

BABOK Guide v3, section 2.5: Manage Stakeholder Collaboration

CCBA Exam Questions, question 19

The BA and the stakeholders should review the priorities when they receive detailed estimates of time required to develop each report based on business requirements. This means that they should reassess and adjust the relative importance or urgency of each report based on its value, feasibility, risk, and dependency. They should also consider factors such as stakeholder expectations, resource availability, schedule constraints, and quality standards.

The other options are incorrect because:

Option A is incorrect because revising business requirements is not an action that the BA and stakeholders take when they receive detailed estimates of time required to develop each report based on business requirements. Business requirements are high-level statements of goals, objectives, needs, or problems of stakeholders or an organization. Business requirements are not revised based on estimates, but based on changes in stakeholder needs or expectations.

Option B is incorrect because writing functional report specifications is not an action that the BA and stakeholders take when they receive detailed estimates of time required to develop each report based on business requirements. Functional report specifications are detailed descriptions of how each report should look and behave in terms of layout, content, format, functionality, etc. Functional report specifications are written based on business requirements, not based on estimates.

Option D is incorrect because analyzing technical constraints is not an action that the BA and stakeholders take when they receive detailed estimates of time required to develop each report based on business requirements. Technical constraints are limitations or restrictions imposed by the technology, system, or solution that affect its design, development, or implementation. Technical constraints are analyzed based on solution requirements, not based on estimates.

References:

BABOK Guide v3, section 10.43: Prioritization

CCBA Exam Questions, question 12

The business analyst should consider the business relevance of the requirements while tracing them to the business needs, goals, and objectives. This will help the BA to ensure that the requirements are aligned with the business value and provide a clear rationale for their inclusion in the solution scope. By tracing the requirements, the BA can also identify and eliminate any unnecessary or redundant features that do not contribute to the business value.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Requirements Life Cycle Management knowledge area, where tracing requirements is a key task for the BA12. It also relates to the Business Analysis Planning and Monitoring knowledge area, where the BA should define the business analysis approach and the requirements prioritization process

A stakeholder list is an elicitation technique that helps the business analyst (BA) to determine who should be consulted, who should participate, and what roles each should fill in the elicitation activities. A stakeholder list identifies and categorizes the stakeholders who have an interest or influence in the project or solution, and defines their level of involvement, authority, and responsibility1. By using a stakeholder list, the BA can ensure that the relevant stakeholders are engaged and informed throughout the elicitation process, and that their needs and expectations are considered and addressed.

References: The answer is based on the BABOK® Guide, which is a key resource for the CCBA® certification. Specifically, it relates to the Elicitation and Collaboration knowledge area, where stakeholder list is one of the techniques that can be used by the BA23. It also relates to the Business Analysis Planning and Monitoring knowledge area, where the BA should plan stakeholder engagement and identify the business analysis roles and responsibilities24. Additionally, the answer is supported by the web search results from the tool invocation, which provide more information and examples of stakeholder list5.

The quality criteria that must be satisfied when the BA is defining requirements relationships is necessary. This means that the BA should ensure that each requirement has a clear and valid reason or purpose for being included in the solution scope. A necessary requirement is one that supports a business goal or objective, addresses a problem or opportunity, or satisfies a stakeholder need or expectation.

The other options are incorrect because:

Option A is incorrect because priority is not a quality criteria that must be satisfied when the BA is defining requirements relationships, but a factor that the BA should consider when prioritizing requirements. Priority is the relative importance or urgency of a requirement based on its value, feasibility, risk, or dependency.

Option B is incorrect because complexity is not a quality criteria that must be satisfied when the BA is defining requirements relationships, but a factor that the BA should consider when analyzing requirements. Complexity is the degree of difficulty or uncertainty involved in implementing or maintaining a requirement based on its scope, scale, or interdependencies.

Option D is incorrect because source is not a quality criteria that must be satisfied when the BA is defining requirements relationships, but an attribute that the BA should document when managing requirements. Source is the origin or reference of a requirement such as a stakeholder, document, regulation, standard, etc.

References:

BABOK Guide v3, section 6.2: Requirements Analysis and Design Definition

CCBA Exam Questions, question 31

The solution approach is a description of how a need will be addressed by a solution. It includes an analysis of whether to build, buy, or reuse a solution component, or a combination of these options. Developing the project plan, outlining the change control strategy, and validating the requirements are not goals of this analysis. References: BABOK Guide v3, page 30; CCBA Mock Test, question 8

 The BA can help the team member understand why a small change requires looking at different enterprise-level business objectives by explaining that proper analysis from different aspects is required to select the best solution. This is because proper analysis from different aspects is a technique that involves considering various factors that influence a solution selection, such as feasibility, desirability, viability, sustainability, etc. Proper analysis from different aspects can help to ensure that a solution aligns with different enterprise-level business objectives and delivers optimal value to stakeholders. The other options are not as accurate or helpful as explaining proper analysis from different aspects. References:

BABOK Guide, section 10.17: Review Business Objectives

CCBA Practice Test, question 117

Explaining that the models are complementation to each other is a technique that helps to resolve the conflict by showing the benefits and limitations of each model, and how they can be used together to provide a more complete and accurate representation of the requirements1. Explaining that the models are complementation to each other can help the BA to satisfy both stakeholders, who may have different preferences or perspectives on how to describe the requirements. This technique can also enhance the quality and clarity of the requirements, as different models can capture different aspects or levels of detail of the requirements2. The other options are not appropriate techniques that the BA should use to resolve the conflict, as they may create or exacerbate issues, gaps, or inconsistencies in the requirements. Allowing both stakeholders to work on the models independently may result in duplication, contradiction, or misalignment of the requirements. Introducing a third model type may confuse or frustrate the stakeholders, who may not be familiar or comfortable with the new model. Suggesting a fusion model may not be feasible or effective, as different models may have different notations, semantics, or purposes. References:

1: How to Resolve Conflicts Between Stakeholders Over Requirements Models

2: Why Use Multiple Models to Describe Requirements?