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. 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.
Historic Analysis
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities
Impact Analysis - Requirements Coverage - Requirements Allocation
User Story
2. What is the output of the task Confirm Elicitation Results?
The Business Analysis Communication Plan
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
Perform tailoring exercises
To record the conflict in the Requirements Issues Log.
3. Two techniques used in Root Cause Analysis?
Benchmarking - Brainstorming - Business Rules Analysis - Focus Groups - Functional Decomposition - Root Cause Analysis
Fishbone Diagram - Five Whys
Onion Diagram
Evolutionary or Functional Prototype
4. To identify interfaces between solutions and/or solution components and define requirements that describe how they will interact.
Interface Analysis
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Functional Decomposition
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
5. What are the techniques used in the task - Define Business Case?
Metrics & KPIs
Decision Analysis - Estimation - Metrics & KPIs - Risk Analysis - SWOT Analysis - Vendor Assessment
Vertical Prototype
Acceptance - Transfer - Avoidance - Mitigation
6. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time - and to identify ways to improve the solution to better meet objectives.
Evaluation
Structured Walkthrough
Acceptance - Transfer - Avoidance - Mitigation
Stakeholder Lists - Roles & Responsibilities
7. Three key factors when assessing the quality of indicators and their metrics
Requirements (Stated) - Stakeholder Concerns
Reliability - Validity - Timeliness
Business Analysis Plan
All
8. Requires the team to focus on examining the premises - assumptions - observations and expectations of the team members. This type of conflict can have a beneficial effect of strengthening the foundations of the analysis and the solution.
Document Elicitation Results task
Cognitive Conflict
Requirements (Approved)
Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - Testable
9. What is the output of the task Plan Requirements Management Process?
Description - Raised by - Date Identified - Impact - Priority - Need by Date - Owner - Status - Action Needed to be Resolved - Responsible for Action - Completion Date of Action - Outcome
Requirements Analysis
Reporting
Requirements Management Plan
10. Rules that are intended to help determine when something is or is not true - or when things fall into a specific category. They are expressed as rules because they describe categorizations that may change over time.
Decision Analysis - Problem Tacking - Risk Analysis
Implementation Approach
Brainstorming
Structural Rules
11. What are the techniques used in Plan Business Analysis Approach?
Decision Analysis - Process Modeling - Structured Walkthrough
Facilitation
Estimation - Functional Decomposition - Risk Analysis
Assumptions & Constraints
12. What is a STAKEHOLDER requirement - according to the BABOK 2.0?
Business Analysis Communication Plan - Requirements - Requirements Package
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Requirements Structure
A statement of the needs of a particular stakeholder or class of stakeholders
13. Documents terms unique to a domain.
Document Analysis
Risk Analysis
Glossary
Business Case - Business Need - Requirements - Requirements Management Plan - Stakeholder List - Roles & Responsibilities
14. Organizational culture - Stakeholder preference - complexity - organizational maturity and availability of resources are all factors used to do what?
Perform tailoring exercises
Dependencies
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements
SWOT Analysis
15. 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.
Metrics & KPIs
Assess Organization Readiness
Requirements Analysis
Evolutionary or Functional Prototype
16. What are the characteristics of Interaction Skills?
Solution Scope Definition - Implementation Approach - Dependencies
Validate Requirements
Facilitation & Negotiation - Leadership & Influencing - Teamwork
Strengths - Weaknesses
17. What are the elements of the task - Define Solution Scope?
General Purpose Applications & Specialized Applications
Solution Scope Definition - Implementation Approach - Dependencies
Requirements Structure
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
18. Long-term - ongoing and qualitative statements of a state or condition that the organization is seeking to establish and maintain.
Goals
Share - Enhance - Exploit
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
Interviews
19. A means of eliciting requirements by conducting an assessment of the stakeholder's work environment. This technique is appropriate when documenting details about current processes or if the project is intended to enhance or change a current process.
Observation
Business Analysis Plan
Data Dictionary
Cognitive Conflict
20. When a conflict arises between stakeholders on one or more documented requirements - the first thing that needs to take place is what?
To record the conflict in the Requirements Issues Log.
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
Brainstorming
Clear - Relevant - Economical - Adequate - Quantifiable
21. Using this technique the business analyst has collected the deliverables - activities - tasks - and estimates from all the involved stakeholders and rolls them up to get a total for all the activities and tasks.
Non-functional Requirements Analysis
Stakeholder Lists - Roles & Responsibilities
Bottom-up Estimation
Business Need - Enterprise Architecture - Organizational Process Assets
22. The goal of this task is to create a set of views of the requirements for the new business solution that are comprehensive - complete - consistent and understood from all stakeholder perspectives.
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Primary stakeholders in the Organize Requirements task
Expert Judgment
Organize Requirements
23. The goal of this task is validate that the stated requirements expressed by the stakeholder match the stakeholder's understanding of the problem and the stakeholder's needs. Analyst's understanding conforms to the actual desire or intentions of the s
Confirm Elicitation Results
The Sponsor
User Classes - Profiles or Roles; Concepts & Relationships - Events - Processes - Rules
Requirements (Any Except Stated)
24. What are stakeholder requirements?
They describe what a solution must be capable of doing to meet the needs of one or more stakeholder groups
User Story
Business Analysis Communication Plan - Requirements - Requirements Package
Organization Modeling
25. Define the requirements that must be met in order for a solution to be considered acceptable to key stakeholders.
Personal Organization
Organizational Readiness Assessment
Structural Rules
Acceptance & Evaluation Technique
26. What techniques are used in the task Manage Requirements Traceability?
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements
Coverage Matrix - Table or spreadsheet used to manage tracing.
Structured Walkthrough
Organizational Readiness Assessment
27. The BA is a stakeholder in ______ business analysis activities.
All
Focus Group
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Horizontal Prototype
28. Corrective or preventative measures uncovered while performing a Business Analysis Performance Assessment will result in changes to what plan?
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets
Influence on the project - organizational - project health and other stakeholders
Business Analysis Plan
Advantages of a Data Dictionary & Glossary
29. What describes how - when and why the business analyst will work with stakeholders?
The Business Analysis Communication Plan
Term and Fact Model
Business Need
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
30. What are some examples of stakeholder concerns?
Structured Walkthrough
Prepare Requirements Package
Requirements - Requirements Management Plan
Risk - assumptions - constraints - etc.
31. An important tool in defining the scope of work and developing estimates. Decomposes the project scope into smaller and smaller pieces - creating a hierarchy of work.
Work Breakdown Structure (WBS)
Vertical Prototype
Acceptance & Evaluation Criteria Definition - Metrics & KPIs - Prototyping - Risk Analysis - Structured Walkthrough
Fishbone Diagram - Five Whys
32. What are the techniques used in the task - Communicate Requirements?
Business Goals & Objectives - Requirements (Stated)
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Description - Raised by - Date Identified - Impact - Priority - Need by Date - Owner - Status - Action Needed to be Resolved - Responsible for Action - Completion Date of Action - Outcome
Requirements Workshop - Structured Walkthrough
33. What are the attributes of a Data Model?
Business Rules Analysis - Data Flow Diagrams - Process Modeling - Organization Modeling - Data Modeling
Structured Walkthrough
Requirements Management Plan - Solution Scope - Stakeholder List - Roles & Responsibilities - Stakeholder/Solution or Transition Requirements (Communicated or Traced)
Name - Value/Meanings - Description
34. What is the output of the Plan Business Analysis Approach?
Leadership
Business Analysis Approach
Evaluate Solution Performance
Decision Analysis - Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting
35. Uses history as a basis for estimating. It is similar to analogous estimation - but is used not only for the top-down estimate - but for the detailed tasks as well.
Business Analysis Communication Plan - Organizational Process Assets - Requirements - Requirements Structure
Advantages of Document Analysis
Historic Analysis
That they understand them and the current state the requirements are in
36. What are the inputs to the task Manage Requirements Traceability?
Requirements (Stated) - Requirements Structure
Impact Analysis
Requirements - Requirements Management Plan
Business Rules Analysis - Data Flow Diagrams - Process Modeling - Organization Modeling - Data Modeling
37. Models a shallow - and possibly wide view of the system's functionality. It typically does not have any business logic running behind the visualization.
Requirements (Allocated)
Horizontal Prototype
Organizational Process Assets - Requirements (Stated) - Solution Scope
Ethics
38. What is the output of the task - Manage Requirements Traceability?
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
Requirements (Traced)
Solution Scope
39. Understanding of the business architecture of the organization that is being analyzed. Understanding business models (generates profit) - org structure - relationships between business units and the persons who occupy key stakeholder positions.
Define Transitional Requirements
Organizational Knowledge
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
Required Capabilities
40. 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.
Transition Requirements
Acceptance & Evaluation Criteria Definition - Brainstorming - Interviews - Organizational Modeling - Process Modeling - Requirements Workshop - Risk Analysis - Scenarios & Use Cases - User Stories - Scope Modeling - Survey/Questionnaire - RACI Matrix
To record the conflict in the Requirements Issues Log.
Solution Assessment & Validation
41. What are the characteristics of a Problem Record?
Requirements (Traced)
Work Breakdown Structure (WBS)
Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - Testable
Description - Raised by - Date Identified - Impact - Priority - Need by Date - Owner - Status - Action Needed to be Resolved - Responsible for Action - Completion Date of Action - Outcome
42. A package should contain a consistent - cohesive and coherent set of requirements. This describes the ____________.
Problem or Vision Statement
Stakeholder Matrix - Onion Diagram
Acceptance & Evaluation Criteria Definition - Brainstorming - Interviews - Organizational Modeling - Process Modeling - Requirements Workshop - Risk Analysis - Scenarios & Use Cases - User Stories - Scope Modeling - Survey/Questionnaire - RACI Matrix
Requirements Structure
43. Agreement by stakeholders that analysis models effectively and completely describe the domain - identification of related problems or issues from multiple areas in the domain - rapid absorption of new information or new domain.
Learning
Evaluate Solution Performance
Risk - assumptions - constraints - etc.
Data Modeling
44. Means of eliciting information from many people - sometimes anonymously - in a relatively short period of time
Solution Performance Assessment
Parametric Estimation
Survey/Questionnaire
Business Need - Enterprise Architecture - Organizational Process Assets
45. What are the Composite Data Elements?
Business Need - Enterprise Architecture - Organizational Process Assets
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets
Oral Communications - Teaching - Written Communication
Sequences - Repetitions - Optional Elements
46. What are the inputs to the task Conduct Elicitation Activity?
Business Need - Organizational Process Assets - Requirements Management Plan - Scheduled Resources - Solution Scope & Business Case - Supporting Materials
Coverage Matrix - Table or spreadsheet used to manage tracing.
Necessity - Effort - Subset - Cover - Value
Systems Thinking
47. What are the inputs to the task - Define Business Case?
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Business Rules Analysis
General Purpose Applications & Specialized Applications
Trustworthiness
48. Confidence in the problem solving process that a selected solution is correct - new solution options can be evaluated effectively using the problem solving framework - selected solutions meet the defined objectives and solve the underlying problem -
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Glossary
Assess Proposed Solution - Allocate Requirements - Assess Organizational Readiness - Define Transition Requirements - Validate Solution - Evaluate Solution Performance
Problem Solving
49. Prioritizes requirements based on a allocated fixed amount of money.
Budgeting
Reporting
Specific - Measurable - Achievable - Relevant - Time-bound Objectives must be SMART.
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
50. What are the inputs for the task - Define Transitional Requirements?
Facilitation
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Acceptance & Evaluation Criteria - Decision Analysis - Vendor Assessment
Perform tailoring exercises