SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
CBAP Business Analysis And Planning
Start Test
Study First
Subjects
:
certifications
,
business-skills
Instructions:
Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Familiarity with the range of commercially available solutions or suppliers can assist with the identification of possible alternatives.
Organize Requirements
Solution Knowledge
Leadership
Business Need - Organizational Process Assets - Required Capabilities
2. A brief description of functionality that users need from a solution to meet a business objective. The goal they are trying to accomplish - and any additional information that may be critical to understanding the scope of the story.
Define Transitional Requirements
User Story
Business Need - Expert Judgment - Organizational Process Assets
Problem Tracking - Risk Analysis
3. What are some of the key variables used in determining the priority of a requirement?
Solution Performance Assessment
Solution Approach
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
Requirements - Requirements Management Plan
4. Are used to model the logic of usage scenarios - by showing the information passed between objects in the system through the execution of the scenario. Shows how classes and objects interact during a scenario.
Observation
Sequence Diagrams
Required Capabilities
Root Cause Analysis
5. Defines what must be delivered in order to meet the business need - and the effect of the proposed change initiation on the business and technology operations and infrastructure.
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
Structured Walkthrough
Solution Scope
6. What stakeholder receives noticeable negative impact if information is incorrectly transferred from the old to new solution?
Business Analysis Communication Plan
Document Analysis
Customer
Automate or Simplify Work - Improve Access to Information - Reduce Complexity of Interfaces - Increase Consistency of Behavior - Eliminate Redundancy
7. What techniques are used in the task Prepare for Elicitation?
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Solution Performance Assessment
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Prepare for Elicitation - Conduct Elicitation Activity - Document Elicitation Results - Confirm Elicitation Results
8. When performing root cause analysis as part of the Validate Solution task - what stakeholder may be involved?
Implementation SME
Operative Rules
To record the conflict in the Requirements Issues Log.
Implementation Approach
9. Prioritizes requirements based on a allocated fixed amount of money.
Budgeting
Learning
Transition Requirements
Decision Analysis - Estimation - Metrics & KPIs - Risk Analysis - SWOT Analysis - Vendor Assessment
10. Means of eliciting information from many people - sometimes anonymously - in a relatively short period of time
Requirements (Maintained and Reusable)
Problem or Vision Statement
Survey/Questionnaire
Acceptance Criteria
11. Includes the standard definition of data elements - their meanings and allowable values.
Communicated Requirements
Functions - Markets - Matrix
Business Analysis Communication Plan
Data Dictionary
12. What are the inputs to the task - Assess Proposed Solution?
Data - Ongoing Work - Organizational Change
SWOT Analysis
Impact Analysis - Requirements Coverage - Requirements Allocation
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
13. Creates a conceptual model of the work that needs to be completed to deliver the new business solution.
Requirements (Maintained and Reusable)
Functional Decomposition
Requirements (Prioritized and Approved) - Solution (Designed) - Solution Scope
Brings them to a Communication on understanding
14. What are the classifications used to describe requirements
Decision Analysis
Business Requirements - Stakeholder Requirements - Solution Requirements - Transition Requirements
Elicitation
Requirements Structure
15. What are the techniques used in the task Manage Solution Scope & Requirements?
Data Dictionary & Glossary
Responsible - Accountable - Consulted - Informed
Problem Tracking - Baselining - Signoff
Risk Analysis
16. When a requirement is changed - the BA can easily review all the related requirements and software components in order to understand the impact of the change.
Business Need - Organizational Process Assets - Requirements Management Plan - Scheduled Resources - Solution Scope & Business Case - Supporting Materials
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
Impact Analysis - Requirements Coverage - Requirements Allocation
Impact Analysis
17. What is the output of the task - Prepare Requirements Package?
Requirements Package
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Rolling Wave
Scope Modeling
18. What is the output of the Plan Business Analysis Approach?
Stakeholder Matrix - Onion Diagram
Activity List
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
Business Analysis Approach
19. To identify interfaces between solutions and/or solution components and define requirements that describe how they will interact.
Key Performance Indicator (KPI )
Requirements Structure
Interface Analysis
Define Business Case
20. What are the techniques used in Plan Business Analysis Communication?
Prepare Requirements Package
Benefits - Costs - Risk Assessment - Results Measurement
All
Structured Walkthrough
21. Confidence in the decision analysis process that a decision is correct - new information or alternative that cause a decision to be revisited are new and not simply overlooked - decisions are effective in addressing underlying problem - impact of unc
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
Decision Making
Implementation Approach
Business Goals & Objectives - Requirements (Stated)
22. What is the output of the task Plan Business Analysis Communication?
Business Analysis Communication Plan
Data Dictionary & Glossary - Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshops - Survey/Questionnaire
Business Analysis Performance Assessment - Business Analysis Process Assets - Includes a comparison of planned versus actual performance - understanding the root cause of variances from the plan and other information to help understand the level of
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
23. Describes the effect a new solution will have on an organization and whether the organization is prepared for the organizational change the solution implementation will cause.
Lessons Learned Process
Assess Organization Readiness
Business Analysis Approach
Organizational Process Assets - Requirements (Stated) - Solution Scope
24. A good indicator has 5 characteristics:
Benchmarking
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Organizational Knowledge
Clear - Relevant - Economical - Adequate - Quantifiable
25. What are the inputs to the task - Define Business Need?
Monitoring
Business Analysis Communication Plan - Requirements - Requirements Package
Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - Testable
Business Goals & Objectives - Requirements (Stated)
26. What should be considered when establishing a Change Management process?
Business Policy
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
27. What are the inputs to the task - Verify Requirements?
Problem Tracking - Baselining - Signoff
Name - Aliases - Values/Meanings - Description
Requirements Workshop - Structured Walkthrough
Requirements (Any Except Stated)
28. An organized structure for the requirements and a documented set of relationships between them. Is used so the analyst and stakeholders know where a specific requirement should be found. Should have a clear implicit scope (clear to the stakeholders w
System
Business Need - Organizational Process Assets - Requirements Management Plan - Scheduled Resources - Solution Scope & Business Case - Supporting Materials
Interviews
Requirements Structure
29. How is the Operational Support stakeholder utilized in the Evaluate Solution Performance task?
Requirements Analysis
This person will be involved in monitoring the performance and effectiveness of a solution or its components.
Assess Proposed Solution - Allocate Requirements - Assess Organizational Readiness - Define Transition Requirements - Validate Solution - Evaluate Solution Performance
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
30. What are the techniques used in the task Conduct Elicitation Activity?
System
Data Dictionary & Glossary - Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshops - Survey/Questionnaire
Evaluation
Formal requirements presentation to stakeholders
31. What are the techniques used in the task Manage Business Analysis Performance?
Three-point Estimation
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Validate Requirements
Formal Documentation - Presentation - Model
32. What is the output of the task - Maintain Requirements for Re-use?
Problem Solving
Solution Knowledge
Organizational Process Assets - Requirements
Requirements (Maintained and Reusable)
33. Decisions are made with the interest of all stakeholders considered - reasons for a decision are cleared articulated - prompt and full disclosure of conflicts of interest - honesty regarding one's abilities and the performance of one's work.
Assessment of Proposed Solution
Sequence Diagrams
Requirements (Verified)
Ethics
34. Investigating how a solution is actually used after it is deployed and assessing the effect it has had - both positive and negative.
Decision Making
Stakeholder Lists - Roles & Responsibilities
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities
Evaluate Solution Performance
35. This prototype extends the initial interface requirements into a fully functioning system and requires a specialized prototyping tool or language.
This person will be involved in monitoring the performance and effectiveness of a solution or its components.
Evolutionary or Functional Prototype
Fishbone Diagram - Five Whys
User Story
36. This task describes the work required to decide which formats are appropriate for a particular project and its stakeholders. The requirements must be clear - concise - accurate and at the appropriate level of detail to assure clear understanding by t
Prepare Requirements Package
Implementation SME
Stakeholder Matrix
Requirements - Requirements Management Plan
37. Maps the level of stakeholder influence and interest in a project.
Stakeholder Matrix
Systems Thinking
Organizational Process Assets - Requirements
General Purpose Applications & Specialized Applications
38. What are the inputs for the task - Maintain Requirements for Re-use?
Organizational Process Assets - Requirements
User Classes - Profiles or Roles; Concepts & Relationships - Events - Processes - Rules
Business Rules Analysis - Data Flow Diagrams - Data Modeling - Functional Decomposition - Organizational Modeling - Process Modeling - Scenarios & Use Cases - Scope Modeling - User Stories
Requirements Structure
39. Two techniques used in Root Cause Analysis?
Assumptions & Constraints - Required Capabilities - Solution Approach
Data Dictionary
Fishbone Diagram - Five Whys
That they understand them and the current state the requirements are in
40. What are the techniques used in the task Define Business Need?
Opportunity Cost
Scenarios & Use Cases
Benchmarking - Brainstorming - Business Rules Analysis - Focus Groups - Functional Decomposition - Root Cause Analysis
Facilitation
41. Two types of conflict.
Emotional and Cognitive
Advantages of Document Analysis
Stakeholder Matrix - Onion Diagram
Requirements Workshop
42. Communicated Requirements mean what to stakeholders?
Compliance with regulatory or other standards
Requirements (Stated) - Requirements Structure
Historic Analysis
That they understand them and the current state the requirements are in
43. This knowledge area describes the tasks that are performed in order to ensure that solutions meet the business need and to facilitate successful implementation.
Glossary
Stakeholder Matrix
Solution Assessment & Validation
Requirements Structure
44. What are the inputs to the task - Define Assumption & Constraints?
Cognitive Conflict
Business Rule
Organizational Readiness Assessment
Stakeholder Concerns
45. According to the BABOK 2.0 - what type of analysis generates STAKEHOLDER requirements?
Solution Scope Definition - Implementation Approach - Dependencies
Problem Tracking - Risk Analysis
Requirements Analysis
MoSCoW Analysis
46. List 3 possible forms of a requirements packages.
Elimination
Formal Documentation - Presentation - Model
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
Verify Requirements
47. What is the output of the task - Validate Requirements?
Systems Thinking
Evaluation Criteria
Scenarios & Use Cases
Requirements (Validated)
48. What are the inputs for the task - Evaluate Solution Performance?
Estimation - Functional Decomposition - Risk Analysis
Elicitation Results
Business Requirements - Identified Defects - Solution Performance Metrics - Solution (Deployed)
Transition Requirements
49. This knowledge area describes how the BA assesses proposed solutions and determines which solution best fits the business need - identifies gaps and shortcomings to solutions and determines necessary workarounds or changes to the solution.
Elimination
Requirements (Any Except Stated)
Key Performance Indicator (KPI )
Solution Assessment & Validation
50. This describes how the chosen solution will deliver the solution scope - may break delivery down into releases or provide a roadmap that indicates the timeframe in which a capability is expected.
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Implementation Approach
Vertical Prototype
Functional Decomposition - Interface Analysis - Scope Modeling - User Stories - Problem or Vision Statement