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 inputs to the task - Prioritize Requirements?
Systems Thinking
Risk Analysis
Business Case - Business Need - Requirements - Requirements Management Plan - Stakeholder List - Roles & Responsibilities
Functional Decomposition
2. What is the output of the Manage Business Analysis Performance task?
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
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Use Case
Prepare Requirements Package
3. What are the Primitive Data Elements?
Data Modeling
Share - Enhance - Exploit
Name - Aliases - Values/Meanings - Description
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
4. A specific - actionable - testable directive that is under the control of an organization and supports a business policy.
Compliance with regulatory or other standards
Systems Thinking
Clear - Relevant - Economical - Adequate - Quantifiable
Business Rule
5. What are the internal factors in a SWOT Analysis?
Business Principles & Practices
Document Analysis
Allocate Requirements
Strengths - Weaknesses
6. What is the output of the task - Prepare Requirements Package?
Estimation
Requirements Package
Glossary
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
7. A continuous process of collecting data to determine how well a solution has been implemented compared to expected results.
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Requirements Analysis
Monitoring
8. According to the BABOK 2.0 - what type of analysis generates STAKEHOLDER requirements?
Tracing Requirements
Solution Scope
Requirements Analysis
Requirements Structure
9. What are some of the commonly used requirement attributes?
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
Requirements Analysis
Sequence Diagrams
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
10. The people involved - the interactions between them - the external forces affecting their behavior and all other relevant elements and factors.
System
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Allocate Requirements
Term and Fact Model
11. Documents terms unique to a domain.
Conduct Elicitation Activity
Glossary
Advantages of Document Analysis
Business Case; Stakeholder - Solution or Transition Requirements (Verified)
12. 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.
Organize Requirements
Solution Knowledge
Plan Business Analysis Approach - Conduct Stakeholder Analysis - Plan Business Analysis Activities - Plan Business Analysis Communication - Plan Requirements Management Process - Manage BA Performance
Work Breakdown Structure (WBS)
13. What are some of the key variables used in determining the priority of a requirement?
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
Requirements (Maintained and Reusable)
Solution Assessment & Validation
Business Need - Enterprise Architecture - Organizational Process Assets
14. A systematic approach designed to elicit information from a person or group of people in an informal or formal setting by talking to an interviewee - asking relevant questions and documenting the responses.
Interviews
Acceptance & Evaluation Criteria Definition - Metrics & KPIs - Prototyping - Risk Analysis - Structured Walkthrough
Solution Knowledge
Reliability - Validity - Timeliness
15. To define the rules that govern decisions in an organization and that define - constrain or enable organization operations.
Business Rules Analysis
Share - Enhance - Exploit
Formal Documentation - Presentation - Model
Organizational Knowledge
16. What are the techniques used in the task - Allocate Resources?
Data Dictionary & Glossary
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Business Policy
Requirements Management Plan
17. How is the Operational Support stakeholder utilized in the Evaluate Solution Performance task?
Business Analysis Approach
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
This person will be involved in monitoring the performance and effectiveness of a solution or its components.
To record the conflict in the Requirements Issues Log.
18. Three types of organizational structures
Glossary
Functions - Markets - Matrix
Benefits - Costs - Risk Assessment - Results Measurement
Structured Walkthrough
19. A package should contain a consistent - cohesive and coherent set of requirements. This describes the ____________.
Requirements Structure
Discounted Cash Flow - Net Present Value - Internal Rate of Return - Average Rate of Return - Pay Back Period - Cost-Benefit Analysis
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Opportunity Cost
20. What are the inputs to the task - Specify & Model Requirements?
SWOT Analysis
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
Requirements (Stated) - Requirements Structure
To record the conflict in the Requirements Issues Log.
21. Are written to describe how an actor interacts with a solution to accomplish one or more of that actor's goals - or to respond to an event.
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
Scenarios & Use Cases
Data Dictionary & Glossary
Requirements Documentation - Requirements for Vendor Selection
22. 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.
User Story
Automate or Simplify Work - Improve Access to Information - Reduce Complexity of Interfaces - Increase Consistency of Behavior - Eliminate Redundancy
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
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
23. What is the output of the task - Prioritize Requirements?
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
Interface Analysis
Requirements (Prioritized)
24. What are the techniques used in the task Manage Solution Scope & Requirements?
Risk - assumptions - constraints - etc.
Underlying Competencies
Required Capabilities
Problem Tracking - Baselining - Signoff
25. What is the output of the task Plan Requirements Management Process?
Requirements Management Plan - Solution Scope - Stakeholder List - Roles & Responsibilities - Stakeholder/Solution or Transition Requirements (Communicated or Traced)
Requirements Management Plan
Stakeholder Lists - Roles & Responsibilities
Brings them to a Communication on understanding
26. Knowing the dependencies and relationships between requirements helps when determining the sequence in which requirements are to be addressed. Common relations are:
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
Coverage Matrix - Table or spreadsheet used to manage tracing.
Necessity - Effort - Subset - Cover - Value
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
27. 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.
Bottom-up Estimation
Analytical Thinking & Problem Solving
Share - Enhance - Exploit
That they understand them and the current state the requirements are in
28. The purpose is to describe the required qualities of a system - such as its usability and performance characteristics.
Non-functional Requirements Analysis
Elicitation Results
Assumptions & Constraints
Enterprise Analysis - often the starting point for initiating a new project
29. Measures progress towards a strategic goal or objective.
Requirements Analysis
Activity List
Historic Analysis
Key Performance Indicator (KPI )
30. What are the underlying competencies a BA should possess?
Sequence Diagrams
Facilitation & Negotiation - Leadership & Influencing - Teamwork
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
Elicitation Results
31. Define the requirements that must be met in order for a solution to be considered acceptable to key stakeholders.
Acceptance & Evaluation Technique
Problem or Vision Statement
Conduct Elicitation Activity
This person will be involved in monitoring the performance and effectiveness of a solution or its components.
32. What is the output of the task - Assess Proposed Solution?
Assessment of Proposed Solution
Glossary
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
33. 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.
Expert Judgment
Document Analysis - SWOT Analysis
Decision Analysis - Process Modeling - Structured Walkthrough
Business Need
34. Elements identified for each activity and task.
Unique Number - Activity Description - Assumptions - Dependencies - Milestones
Document Analysis - SWOT Analysis
Monitoring
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
35. Familiarity with the range of commercially available solutions or suppliers can assist with the identification of possible alternatives.
Solution Knowledge
Requirements Analysis
Requirements (Analyzed)
Problem or Vision Statement
36. 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.
Structured Walkthrough
Decision Analysis
Requirements Analysis
Influence on the project - organizational - project health and other stakeholders
37. Means of eliciting information from many people - sometimes anonymously - in a relatively short period of time
Customer
Survey/Questionnaire
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements
Perform tailoring exercises
38. Defines the key terms and data relevant to a business domain.
Business Analysis Communication Plan
Benefits - Costs - Risk Assessment - Results Measurement
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
Data Dictionary & Glossary
39. What are the output(s) of the task - Validate Solution?
Identified Defects - Mitigating Actions - Solution Validation Assessment
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities
SWOT Analysis
Systems Thinking
40. Forecast the cost and effort involved in pursuing a course of action. Used to develop a better understanding of the possible range of costs and effort associated with any initiative
Requirements (Stated) - Stakeholder Concerns
Relationships - Impact Analysis - Configuration Management System
Business Need - Enterprise Architecture - Solution Performance Assessment
Estimation
41. What are the inputs to the task Plan Requirements Management Process?
Assumptions & Constraints - Business Need - Solution Scope - Stakeholder Concerns
Decision Analysis - Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting
Focus Group
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets
42. What are the inputs for the task - Define Solution Scope?
Assumptions & Constraints - Required Capabilities - Solution Approach
Elicitation
Solution Knowledge
Vendor Assessment
43. Checklist of characteristics to consider when considering non-functional requirements.
Validate Requirements
Data Modeling
State Diagrams
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
44. 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
Throw-away Prototype
Goals
Document Elicitation Results task
Business Requirements - Stakeholder Requirements - Solution Requirements - Transition Requirements
45. 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.
Brings them to a Communication on understanding
Facilitation
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Solution Scope
46. Organizational culture - Stakeholder preference - complexity - organizational maturity and availability of resources are all factors used to do what?
Perform tailoring exercises
Root Cause Analysis
Advantages of a Data Dictionary & Glossary
Elimination
47. 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.
Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - Testable
Formal requirements presentation to stakeholders
Organizational Process Assets - Requirements (Stated) - Solution Scope
Cognitive Conflict
48. Allocate stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alternatives generated by the design team.
Activity List
Allocate Requirements
Operative Rules
Requirements Workshop - Structured Walkthrough
49. What are the inputs for the task Prepare for Elicitation?
Requirements (Prioritized)
Enterprise Analysis - often the starting point for initiating a new project
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities
Organizational Knowledge
50. Techniques used in the task Plan Requirements Management Process.
Decision Analysis - Problem Tacking - Risk Analysis
Structured Walkthrough
Delphi Estimation
Oral Communications - Teaching - Written Communication