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. Creates a conceptual model of the work that needs to be completed to deliver the new business solution.
Functional Decomposition
Requirements Management Plan
Relationships - Impact Analysis - Configuration Management System
Requirements (Verified)
2. 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.
Perform tailoring exercises
Structural Rules
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Sequences - Repetitions - Optional Elements
3. What are the techniques used in Plan Business Analysis Communication?
Tracing Requirements
Solution (Constructed) - Requirements (Prioritized and Validated)
Impact Analysis
Structured Walkthrough
4. What is the output of the task - Maintain Requirements for Re-use?
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
Business Rules Analysis
Requirements (Maintained and Reusable)
Primary stakeholders in the Organize Requirements task
5. Knowing the dependencies and relationships between requirements helps when determining the sequence in which requirements are to be addressed. Common relations are:
Ethics - Trustworthiness - Personal Organization
Necessity - Effort - Subset - Cover - Value
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Enterprise Analysis - often the starting point for initiating a new project
6. Techniques used in the task Plan Requirements Management Process.
Decision Analysis - Problem Tacking - Risk Analysis
Underlying Competencies
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets - Stakeholder Lists - Roles & Responsibilities
Goals
7. Communicated Requirements mean what to stakeholders?
Perform tailoring exercises
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
That they understand them and the current state the requirements are in
Business Principles & Practices
8. What are the characteristics of a Problem Record?
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
Survey/Questionnaire
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
Decision Analysis - Problem Tacking - Risk Analysis
9. What should be considered when establishing a Change Management process?
Analytical Thinking & Problem Solving
Business Analysis Planning & Monitoring
Activity List
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 - Prepare Requirements Package?
Requirements Package
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Scheduled Resources - Supporting Materials
Solution Assessment & Validation
11. What are the underlying competencies a BA should possess?
Elimination
Scenarios & Use Cases
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
Cognitive Conflict
12. What are the elements of the task Plan Requirements Management Process?
Functional Decomposition - Interface Analysis - Scope Modeling - User Stories - Problem or Vision Statement
Lessons Learned Process
A statement of the needs of a particular stakeholder or class of stakeholders
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
13. 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
Prototyping
Decision Analysis - Estimation - Metrics & KPIs - Risk Analysis - SWOT Analysis - Vendor Assessment
All
Business Rule
14. What are the Primitive Data Elements?
Name - Aliases - Values/Meanings - Description
Risk - assumptions - constraints - etc.
Brainstorming
Business Analysis Performance Metrics - Business Analysis Plan - Organization Performance Standards - Requirements Management Plan
15. Shows how the behavior of a concept - entity or object changes in response to events during its lifetime - and defines which events cause a transition between those states.
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
State Diagrams
Organizational Process Assets - Requirements (Stated) - Solution Scope
16. 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
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Decision Analysis
Decision Making
17. What are the inputs to the task - Define Business Need?
Business Goals & Objectives - Requirements (Stated)
Requirements (Traced)
Business Analysis Approach - BA Performance Assessment - Organizational Process Assets - Stakeholder List - Roles & Responsibilities
Parametric Estimation
18. What are the Behavioral Characteristics a BA should exhibit?
Ethics - Trustworthiness - Personal Organization
Confirm Elicitation Results
Scenario
Business Rules Analysis - Data Flow Diagrams - Process Modeling - Organization Modeling - Data Modeling
19. What are some of the commonly used requirement attributes?
Evolutionary or Functional Prototype
Requirements Structure
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
20. What are some of the ways a BA can help to improve the operations of a business? Acceptance and Evaluation Criteria Definition - Business Rules Analysis - Data Dictionary and Glossary - Data Flow Diagrams - Data Modeling - Functional Decomposition -
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
Automate or Simplify Work - Improve Access to Information - Reduce Complexity of Interfaces - Increase Consistency of Behavior - Eliminate Redundancy
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
Requirements (Stated) - Stakeholder Concerns
21. What is the output of the task Confirm Elicitation Results?
Data - Ongoing Work - Organizational Change
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
Business Policy
Root Cause Analysis
22. What are some of the key variables used in determining the priority of a requirement?
Opportunity Cost
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
Business Analysis Communication Plan
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
23. 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.
To record the conflict in the Requirements Issues Log.
Validate Requirements
Cognitive Conflict
Evolutionary or Functional Prototype
24. What are the likely sources of transition requirements?
Formal requirements presentation to stakeholders
Data - Ongoing Work - Organizational Change
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)
Visual Learner - Auditory Learner - Kinesthetic Learner
25. The goal of tracing is to ensure that requirements are linked back to a business objective. Creation of this relationship helps in what other traceability activities?
Impact Analysis - Requirements Coverage - Requirements Allocation
Responsible - Accountable - Consulted - Informed
Brainstorming
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
26. What is the output of the task Manage Solution Scope & Requirements?
MoSCoW Analysis
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
Requirements (Approved)
27. A continuous process of collecting data to determine how well a solution has been implemented compared to expected results.
Business Principles & Practices
Ongoing Cost versus Initial Investment - Opportunity Costs - Necessity - Sunk Costs
Monitoring
Implementation Approach
28. What are the techniques used in the task - Assess Proposed Solution?
Functions - Markets - Matrix
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets
Relationship to Time - Relationship to Task Completion - Relationship to Contracts - Relationships to Formal and Informal Authority
Acceptance & Evaluation Criteria - Decision Analysis - Vendor Assessment
29. What are the internal factors in a SWOT Analysis?
Timeboxing
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Vendor Assessment
Strengths - Weaknesses
30. The process of informing stakeholders of metrics of indicators in specified formats at specified intervals.
Solution (Constructed) - Requirements (Prioritized and Validated)
Reporting
Horizontal Prototype
Requirements (Verified)
31. What does RACI stand for?
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Business Domain - Corporate Culture & Environment - Skills of the Analyst - Requirement Deliverable
Glossary
Responsible - Accountable - Consulted - Informed
32. Two types of conflict.
Primary stakeholders in the Organize Requirements task
Structural Rules
Emotional and Cognitive
Ethics
33. What are the techniques used in the task - Allocate Resources?
Monitoring
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
State Diagrams
34. 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.
Requirements (Maintained and Reusable)
Business Analysis Plan
Organize Requirements
Impact Analysis
35. What are the general modeling concepts that are relevant to business analysis?
Ethics - Trustworthiness - Personal Organization
Enterprise Analysis - often the starting point for initiating a new project
Sequence Diagrams
User Classes - Profiles or Roles; Concepts & Relationships - Events - Processes - Rules
36. What are the tasks in the knowledge area - Enterprise Analysis?
Prepare Requirements Package
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)
Define Business Need - Access Capability Gaps - Determine Solution Approach - Define Solution Scope - Define Business Case
Rolling Wave
37. While eliciting requirements it is important to guard against scope creep - This activity will ensure that the requirements should be included since they meet the business goal/objectives.
Requirements Analysis
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
Organizational Process Assets - Requirements
Tracing Requirements
38. What are the techniques used in the task Confirm Elicitation Results?
Requirements Management Plan
Ethics
Enterprise Analysis
Interviews - Observation
39. Two techniques used in Root Cause Analysis?
Fishbone Diagram - Five Whys
Influence on the project - organizational - project health and other stakeholders
Activity List
Term and Fact Model
40. 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 Case; Stakeholder - Solution or Transition Requirements (Verified)
Share - Enhance - Exploit
Requirements (Stated) - Stakeholder Concerns
Document Analysis
41. What are the techniques used in the task Document Elicitation Results?
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Business Case
Dependencies
42. What is the output of the task - Manage Requirements Traceability?
Relationships - Impact Analysis - Configuration Management System
Requirements (Traced)
Acceptance - Transfer - Avoidance - Mitigation
Decision Analysis - Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting
43. What is the output of the task - Define Business Case?
Customer
This person will be involved in monitoring the performance and effectiveness of a solution or its components.
Business Case
Solution Approach
44. 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.
Glossary
Evaluation
Business Policy
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities
45. Combination of expert judgment and history. Individual estimates - sharing the estimates with experts - and having several rounds until consensus is reached. An average of the three estimates is used
Decision Analysis - Problem Tacking - Risk Analysis
Delphi Estimation
Ethics
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
46. Organizational culture - Stakeholder preference - complexity - organizational maturity and availability of resources are all factors used to do what?
Elimination
Reliability - Validity - Timeliness
Perform tailoring exercises
Decision Analysis - Problem Tacking - Risk Analysis
47. Two effective trade-off methods.
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
Brainstorming
Primary stakeholders in the Organize Requirements task
48. What are the inputs for the task Prepare for Elicitation?
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets - Stakeholder Lists - Roles & Responsibilities
Problem Tracking - Baselining - Signoff
Tracing Requirements
49. Models a shallow - and possibly wide view of the system's functionality. It typically does not have any business logic running behind the visualization.
Business Requirements - Identified Defects - Solution Performance Metrics - Solution (Deployed)
Horizontal Prototype
Business Analysis Approach
Business Goals & Objectives - Requirements (Stated)
50. Estimating relies on the expertise of those who have performed the work in the past. These experts can be internal or external to the project team or to the organization.
Business Requirements - Identified Defects - Solution Performance Metrics - Solution (Deployed)
Expert Judgment
MoSCoW Analysis
Scheduled Resources - Supporting Materials