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. What are the techniques used in Plan Business Analysis Communication?
Organizational Knowledge
Stakeholder Concerns
Business Need - Organizational Process Assets - Requirements Management Plan - Scheduled Resources - Solution Scope & Business Case - Supporting Materials
Structured Walkthrough
2. 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.
Brainstorming
State Diagrams
Observation
Delphi Estimation
3. What are the inputs for the task - Prepare Requirements Package?
Scope Modeling
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
Necessity - Effort - Subset - Cover - Value
Business Analysis Communication Plan - Organizational Process Assets - Requirements - Requirements Structure
4. To assess the ability of a potential vendor to meet commitments regarding a product or service
Vendor Assessment
Rolling Wave
Requirements (Allocated)
Work Breakdown Structure (WBS)
5. What are the inputs to the task Manage Requirements Traceability?
Document Elicitation Results task
Primary stakeholders in the Organize Requirements task
Requirements - Requirements Management Plan
Evaluation Criteria
6. The goal of this task is to ensure that all requirements support the delivery of value to the business - fulfill its goal and objectives and meet a stakeholder need.
Stakeholder Matrix - Onion Diagram
Reporting
Validate Requirements
Clear - Relevant - Economical - Adequate - Quantifiable
7. The knowledge area that covers how BAs determine which activities are necessary in order to complete a business analysis effort.
Business Analysis Planning & Monitoring
Acceptance & Evaluation Criteria - Data Flow Diagrams - Process Models - Focus Groups - Interviews - Survey/Questionnaire - Organizational Modeling - Problem Tracking - Risk Analysis - SWOT Analysis - Force Field Analysis
Requirements (Validated)
Solution Scope Definition - Implementation Approach - Dependencies
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.
Share - Enhance - Exploit
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
Cognitive Conflict
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
9. What is the output of the task - Prioritize Requirements?
Delphi Estimation
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Requirements (Prioritized)
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
10. What is the output of the task - Define Business Case?
Advantages of a Data Dictionary & Glossary
Business Case
User Classes - Profiles or Roles; Concepts & Relationships - Events - Processes - Rules
Benchmarking
11. What is a STAKEHOLDER requirement - according to the BABOK 2.0?
User Story
A statement of the needs of a particular stakeholder or class of stakeholders
Estimation
Estimation - Functional Decomposition - Risk Analysis
12. 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 Requirements - Identified Defects - Solution Performance Metrics - Solution (Deployed)
Historic Analysis
Solution Performance Assessment
User Classes - Profiles or Roles; Concepts & Relationships - Events - Processes - Rules
13. What is the output of the task Manage Solution Scope & Requirements?
Requirements (Approved)
Requirements Workshop - Structured Walkthrough
Evaluation Criteria
Requirements (Stated) - Stakeholder Concerns
14. What are the underlying competencies a BA should possess?
Observation
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
Facilitation
Opportunity Cost
15. Technique involving refinement of estimates. Estimate the details for activities in the current iteration or increment and provide an analogous estimate for the entire scope of work. As the end of the iteration approaches - estimates for the next ite
Rolling Wave
Data Dictionary & Glossary - Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshops - Survey/Questionnaire
Learning
That they understand them and the current state the requirements are in
16. Who is the primary stakeholder in the Define Business Case task?
State Diagrams
Stakeholder Matrix
The Sponsor
Analogous Estimation
17. Understanding of how a change to a component affects the system as a whole - identification of reinforcing and compensating feedback loops - understanding of how systems adapt to external pressures and changes - A system as a whole will have properti
Systems Thinking
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
Term and Fact Model
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
18. This will impose constraints to the effort to deploy the solution - including relationships that may exist between solution components.
Functions - Markets - Matrix
Requirements (Stated) - Stakeholder Concerns
Vertical Prototype
Dependencies
19. This task ensures that requirement specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work. Requirements have been defined correctly.
Requirements (Prioritized and Approved) - Solution (Designed) - Solution Scope
Verify Requirements
Rolling Wave
Discounted Cash Flow - Net Present Value - Internal Rate of Return - Average Rate of Return - Pay Back Period - Cost-Benefit Analysis
20. 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
That they understand them and the current state the requirements are in
Requirements Structure
Implementation Approach
Expert Judgment
21. What are the techniques used in the task - Allocate Resources?
Requirements Management & Communication
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Business Case; Stakeholder - Solution or Transition Requirements (Verified)
Requirements - Requirements Management Plan
22. What are the techniques used in the task Confirm Elicitation Results?
Customer
Business Case - Business Need - Requirements - Requirements Management Plan - Stakeholder List - Roles & Responsibilities
Interviews - Observation
Problem Solving
23. What are some of the key variables used in determining the priority of a requirement?
Cognitive Conflict
Solution Knowledge
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
Acceptance & Evaluation Criteria Definition - Metrics & KPIs - Prototyping - Risk Analysis - Structured Walkthrough
24. What are the techniques used in the task - Communicate Requirements?
Requirements Workshop - Structured Walkthrough
Onion Diagram
Business Rules Analysis - Data Flow Diagrams - Data Modeling - Functional Decomposition - Organizational Modeling - Process Modeling - Scenarios & Use Cases - Scope Modeling - User Stories
Dependencies
25. What are the inputs to the task - Assess Capability Gaps?
Requirements Workshop
Business Need - Enterprise Architecture - Solution Performance Assessment
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
Budgeting
26. Three key factors when assessing the quality of indicators and their metrics
Learning
Necessity - Effort - Subset - Cover - Value
Enterprise Analysis
Reliability - Validity - Timeliness
27. 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
Customer
Brings them to a Communication on understanding
Business Requirements - Identified Defects - Solution Performance Metrics - Solution (Deployed)
28. 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.
Interface Analysis
Business Need - Expert Judgment - Organizational Process Assets
User Story
Learning
29. 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.
MoSCoW Analysis
Work Breakdown Structure (WBS)
Personal Organization
Structured Walkthrough
30. What are the inputs to the task Manage Solution Scope & Requirements?
The Sponsor
Facilitation & Negotiation - Leadership & Influencing - Teamwork
Requirements Management Plan - Solution Scope - Stakeholder List - Roles & Responsibilities - Stakeholder/Solution or Transition Requirements (Communicated or Traced)
Advantages of a Data Dictionary & Glossary
31. 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.
Impact Analysis
Sequence Diagrams
Acceptance & Evaluation Criteria - Decision Analysis - Vendor Assessment
Business Analysis Planning & Monitoring
32. A continuous process of collecting data to determine how well a solution has been implemented compared to expected results.
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Elicitation Results
Business Analysis Communication Plan
Monitoring
33. Name the 2 types of Stakeholder maps.
Ethics - Trustworthiness - Personal Organization
Benchmarking - Brainstorming - Business Rules Analysis - Focus Groups - Functional Decomposition - Root Cause Analysis
Cognitive Conflict
Stakeholder Matrix - Onion Diagram
34. What are the techniques used in the task - Determine Solution Approach?
Requirements Workshop
Interface Analysis
Benchmarking - Brainstorming - Decision Analysis - Estimation - SWOT Analysis - Feasibility Analysis
Non-functional Requirements Analysis
35. What are the techniques used in the task - Validate Solution?
Requirements (Verified)
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
Activity List
36. Use of parameters - multiplied by the number of hours. (COCOMO II - Function Point Counting - Use Case Points - and Story Points)
Vertical Prototype
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
Problem Tracking - Baselining - Signoff
Parametric Estimation
37. Ability to find information - on-time completion of tasks - efficiency in the completion of work - ability to easily identify all outstanding work and the status of each work item.
Personal Organization
Scenarios & Use Cases
Organize Requirements
Problem Tracking - Risk Analysis
38. What are the inputs to the task - Define Assumption & Constraints?
Stakeholder Concerns
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
Customer
Solution Scope
39. Approach to decision making that examines and models the possible consequences of different decisions. Make an optimal decision under conditions of uncertainty.
Decision Analysis
Business Case
Facilitation
Ethics
40. Strengths - Weaknesses - Opportunities - Threats - A valuable tool to quickly analyze various aspects of the current state of the business process undergoing change.
Evaluation Criteria
SWOT Analysis
Verify Requirements
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
41. This technique shows how information is input - processed - stored and output from a system in a visual representation.
Document Analysis
General Purpose Applications & Specialized Applications
Interviews
Data Flow Diagrams
42. What are the techniques used in the task - Evaluate Solution Performance?
Decision Analysis
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
Opportunity Cost
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
43. What are the techniques used in the task - Define Business Case?
Onion Diagram
Validate Requirements
Decision Analysis - Estimation - Metrics & KPIs - Risk Analysis - SWOT Analysis - Vendor Assessment
Business Analysis Communication Plan
44. What are the inputs to the task - Validate Requirements?
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Business Case; Stakeholder - Solution or Transition Requirements (Verified)
Systems Thinking
Analytical Thinking & Problem Solving
45. According to the BABOK 2.0 - what type of analysis generates STAKEHOLDER requirements?
Requirements Analysis
System
User Story
Scenarios & Use Cases
46. Stakeholders involved the BA in decision making - acceptance of the BA's recommendations - willingness to discuss difficult or controversial topics with the BA - stakeholders willing to support or defend the BA when problems occur.
Identified Defects - Mitigating Actions - Solution Validation Assessment
Business Case; Stakeholder - Solution or Transition Requirements (Verified)
Trustworthiness
Estimation - Functional Decomposition - Risk Analysis
47. What are the classifications used to describe requirements
Assumptions & Constraints - Required Capabilities - Solution Approach
Structural Rules
Requirements (Stated) - Requirements Structure
Business Requirements - Stakeholder Requirements - Solution Requirements - Transition Requirements
48. Communicated Requirements mean what to stakeholders?
Implementation Approach
That they understand them and the current state the requirements are in
Creative Thinking - Decision Making - Learning - Problem Solving - Systems Thinking
Lessons Learned Process
49. What are the techniques used in the task - Define Assumptions & Constraints?
Horizontal Prototype
Problem Tracking - Risk Analysis
Evaluation
Sequences - Repetitions - Optional Elements
50. Domain SME - End User - Implementation SME - and Sponsor: They Affected by analysis techniques used to organize requirements since they need to verify and validate the requirements.
Primary stakeholders in the Organize Requirements task
Organization Modeling
Allocate Requirements
Reporting