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. Provides an organized approach to tracking - management - and resolution of defects - issues - problems - and risks throughout business analysis activities. Management of issues is important so that they can be resolved in a timely manner to ensure s
Solution Scope Definition - Implementation Approach - Dependencies
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Problem Tracking
2. What is the output of the task - Prioritize Requirements?
Ethics - Trustworthiness - Personal Organization
Business Analysis Approach - BA Performance Assessment - Organizational Process Assets - Stakeholder List - Roles & Responsibilities
Reliability - Validity - Timeliness
Requirements (Prioritized)
3. The knowledge area that covers how BAs determine which activities are necessary in order to complete a business analysis effort.
Business Analysis Planning & Monitoring
Relationships - Impact Analysis - Configuration Management System
Define Business Case
Requirements (Stated) - Stakeholder Concerns
4. What is the output of the task - Assess Proposed Solution?
Discounted Cash Flow - Net Present Value - Internal Rate of Return - Average Rate of Return - Pay Back Period - Cost-Benefit Analysis
Customer
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
Assessment of Proposed Solution
5. Ensure that the solution meets the business need and determine the most appropriate response to identified defects.
Functional Decomposition - Interface Analysis - Scope Modeling - User Stories - Problem or Vision Statement
Problem Tracking - Baselining - Signoff
Validate Solution
Vertical Prototype
6. This prototype seeks to quickly uncover and clarify interface requirements using simple tools - sometimes just paper and pencil. The focus is on functionality that is not easily elicited by other techniques - has conflicting viewpoints - or is diffic
Primary stakeholders in the Organize Requirements task
Throw-away Prototype
Creative Thinking - Decision Making - Learning - Problem Solving - Systems Thinking
Organization Modeling
7. What techniques are used in the task Manage Requirements Traceability?
Parametric Estimation
Bottom-up Estimation
User Classes - Profiles or Roles; Concepts & Relationships - Events - Processes - Rules
Coverage Matrix - Table or spreadsheet used to manage tracing.
8. Two effective trade-off methods.
Metrics & KPIs
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
Reliability - Validity - Timeliness
Personal Organization
9. What are the classifications used to describe requirements
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
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)
Business Requirements - Stakeholder Requirements - Solution Requirements - Transition Requirements
Oral Communications - Teaching - Written Communication
10. What are the inputs to the task - Allocate Resources?
Business Principles & Practices
User Story
Requirements (Prioritized and Approved) - Solution (Designed) - Solution Scope
Requirements (Approved)
11. What is the output of the task Plan Business Analysis Activities?
Learning
Business Analysis Plan
Key Performance Indicator (KPI )
Requirements Analysis
12. 7 knowledge areas of ________ : Business Analysis Planning & Monitoring - Elicitation - Requirements Management & Communication - Enterprise Analysis - Requirements Analysis - Solution Assessment & Validation - Underlying Competencies
Opportunity Cost
BABOK
Data Dictionary & Glossary
Historic Analysis
13. What is the output of the task - Define Business Need?
Validate Requirements
Business Need
Requirements Analysis
That they understand them and the current state the requirements are in
14. What are the inputs to the task - Assess Organizational Readiness?
Evaluation
Implementation SME
Data - Ongoing Work - Organizational Change
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
15. Details user interface requirements and integrates them with other requirements such as use cases - scenarios - data and business rules. Stakeholders often find this to be a concrete means of identifying - describing and validating their interface ne
Requirements Structure
Define Business Case
Prototyping
Cognitive Conflict
16. A means to elicit requirements by studying available documentation on existing and comparable solutions and identifying relevant information. - Not starting from a blank page.- Leveraging existing materials to discover and/or confirm requirements. -
Business Analysis Performance Metrics - Business Analysis Plan - Organization Performance Standards - Requirements Management Plan
Business Requirements - Identified Defects - Solution Performance Metrics - Solution (Deployed)
Document Analysis
Requirements (Allocated)
17. The purpose is to describe the required qualities of a system - such as its usability and performance characteristics.
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)
Business Need - Organizational Process Assets - Required Capabilities
Non-functional Requirements Analysis
Requirements (Analyzed)
18. What are the techniques used in the task - Validate Requirements?
Acceptance & Evaluation Criteria Definition - Metrics & KPIs - Prototyping - Risk Analysis - Structured Walkthrough
Solution Approach
Decision Analysis - Process Modeling - Structured Walkthrough
Sequences - Repetitions - Optional Elements
19. What are the techniques used in the task Conduct Stakeholder Analysis?
Requirements Workshop
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
Discounted Cash Flow - Net Present Value - Internal Rate of Return - Average Rate of Return - Pay Back Period - Cost-Benefit Analysis
Brings them to a Communication on understanding
20. What are some examples of stakeholder concerns?
Business Rules Analysis - Data Flow Diagrams - Process Modeling - Organization Modeling - Data Modeling
Decision Analysis - Problem Tacking - Risk Analysis
Historic Analysis
Risk - assumptions - constraints - etc.
21. What are the elements of the task - Define Solution Scope?
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
Solution Scope Definition - Implementation Approach - Dependencies
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
Requirements Workshop
22. Checklist of characteristics to consider when considering non-functional requirements.
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Functional Decomposition
Necessity - Effort - Subset - Cover - Value
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
23. What are the techniques used in the task - Define Business Case?
Decision Analysis - Estimation - Metrics & KPIs - Risk Analysis - SWOT Analysis - Vendor Assessment
Scenario
Organizational Process Assets - Requirements
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
24. This knowledge area involves analyzing stakeholder needs to define solutions that meet those needs - assessing the current state of the business to identify and recommend improvements and the verification and validation of the resulting requirements.
Interface Analysis
Name - Value/Meanings - Description
Interviews - Observation
Requirements Analysis
25. 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
Advantages of a Data Dictionary & Glossary
Rolling Wave
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Requirements (Allocated)
26. What are the techniques used in the task - Assess Organizational Readiness?
Acceptance & Evaluation Criteria - Data Flow Diagrams - Process Models - Focus Groups - Interviews - Survey/Questionnaire - Organizational Modeling - Problem Tracking - Risk Analysis - SWOT Analysis - Force Field Analysis
Emotional and Cognitive
Requirements Analysis
Required Capabilities
27. What are the inputs to the task Manage Solution Scope & Requirements?
Acceptance & Evaluation Technique
Requirements Management Plan - Solution Scope - Stakeholder List - Roles & Responsibilities - Stakeholder/Solution or Transition Requirements (Communicated or Traced)
Analogous Estimation
Reliability - Validity - Timeliness
28. 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.
Data Dictionary & Glossary - Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshops - Survey/Questionnaire
Scenarios & Use Cases
Primary stakeholders in the Organize Requirements task
Data Modeling
29. Maps the level of stakeholder influence and interest in a project.
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Impact Analysis
Stakeholder Matrix
30. What techniques are used in the task - Define Solution Scope?
Organize Requirements
Functional Decomposition - Interface Analysis - Scope Modeling - User Stories - Problem or Vision Statement
Data - Ongoing Work - Organizational Change
Business Need - Expert Judgment - Organizational Process Assets
31. The objective of this technique is to determine how companies achieve their superior performance levels and use that information to design projects to improve operations of the enterprise.
Requirements (Traced)
Sequences - Repetitions - Optional Elements
Benchmarking - Brainstorming - Business Rules Analysis - Focus Groups - Functional Decomposition - Root Cause Analysis
Benchmarking
32. The purpose is to measure the performance of solutions - solution components - and other matters of interest to stakeholders.
Perform tailoring exercises
Metrics & KPIs
Requirements Analysis
Learning
33. A means to elicit ideas and attitudes about a specific product - service or opportunity in an interactive group environment. The participants share their impressions - preferences and needs - guided by a moderator. - Effective for learning people's a
Focus Group
SWOT Analysis
Specific - Measurable - Achievable - Relevant - Time-bound Objectives must be SMART.
Monitoring
34. Strengths - Weaknesses - Opportunities - Threats - A valuable tool to quickly analyze various aspects of the current state of the business process undergoing change.
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
Decision Analysis - Process Modeling - Structured Walkthrough
SWOT Analysis
Functions - Markets - Matrix
35. What are some of the commonly used requirement attributes?
Document Analysis - SWOT Analysis
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - Testable
Data - Ongoing Work - Organizational Change
36. What is the output of the task - Assess Organizational Readiness?
Stakeholder Matrix
Organizational Readiness Assessment
Business Need - Expert Judgment - Organizational Process Assets
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
37. Familiarity with the range of commercially available solutions or suppliers can assist with the identification of possible alternatives.
System
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Delphi Estimation
Solution Knowledge
38. What should be considered when establishing a Change Management process?
Decision Analysis - Process Modeling - Structured Walkthrough
Evaluate Solution Performance
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
Requirements (Traced)
39. What are the inputs to the task - Specify & Model Requirements?
Business Need - Organizational Process Assets - Required Capabilities
Requirements (Stated) - Requirements Structure
Oral Communications - Teaching - Written Communication
Data Dictionary
40. Involved motivating people to act in ways that enable them to work together to achieve shared goals and objectives.
Evaluate Solution Performance
Advantages of a Data Dictionary & Glossary
Leadership
Personal Organization
41. What does RACI stand for?
Evaluate Solution Performance
Requirements (Analyzed)
Responsible - Accountable - Consulted - Informed
Reliability - Validity - Timeliness
42. Models a shallow - and possibly wide view of the system's functionality. It typically does not have any business logic running behind the visualization.
Horizontal Prototype
Primary stakeholders in the Organize Requirements task
Evaluate Solution Performance
Responsible - Accountable - Consulted - Informed
43. Is generally understood to describe just one way that an actor can accomplish a particular goal
Structural Rules
Acceptance & Evaluation Criteria - Data Flow Diagrams - Process Models - Focus Groups - Interviews - Survey/Questionnaire - Organizational Modeling - Problem Tracking - Risk Analysis - SWOT Analysis - Force Field Analysis
Risk - assumptions - constraints - etc.
Scenario
44. 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.
Solution Scope
Oral Communications - Teaching - Written Communication
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
Scenarios & Use Cases
45. What are the inputs for the task Confirm Elicitation Results?
Share - Enhance - Exploit
Business Analysis Plan
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)
Influence on the project - organizational - project health and other stakeholders
46. What are the techniques used in the task - Validate Solution?
Learning
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
Scenario
Stakeholder Concerns
47. Characteristics that are common to all organizations with a similar purpose and structure - whether or not the are in the same industry.
Assessment of Proposed Solution
Business Principals
Vertical Prototype
Share - Enhance - Exploit
48. Divides requirements into 4 categories - Must - Should - Could - Won't
MoSCoW Analysis
They describe what a solution must be capable of doing to meet the needs of one or more stakeholder groups
Solution Performance Assessment
Throw-away Prototype
49. Use of parameters - multiplied by the number of hours. (COCOMO II - Function Point Counting - Use Case Points - and Story Points)
Parametric Estimation
Problem Tracking - Baselining - Signoff
Business Analysis Communication Plan - Requirements - Requirements Package
Business Principals
50. A package should contain a consistent - cohesive and coherent set of requirements. This describes the ____________.
Scope Modeling
Requirements Structure
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists