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 the task Document Elicitation Results?
Business Analysis Approach - BA Performance Assessment - Organizational Process Assets - Stakeholder List - Roles & Responsibilities
Elicitation Results
Fishbone Diagram - Five Whys
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
2. 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 - Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting
Requirements Analysis
Data Dictionary & Glossary
3. What are the Behavioral Characteristics a BA should exhibit?
Required Capabilities
Ethics - Trustworthiness - Personal Organization
Acceptance Criteria
Validate Requirements
4. 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.
Tracing Requirements
Primary stakeholders in the Organize Requirements task
Business Case; Stakeholder - Solution or Transition Requirements (Verified)
Strengths - Weaknesses
5. The goal of this task is to meet with stakeholder(s) to gather information regarding their needs.
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Conduct Elicitation Activity
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Validate Solution
6. What are the 3 elements in the Assess Organizational Readiness?
Business Principals
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Rolling Wave
Non-functional Requirements Analysis
7. What are the techniques used in the task Conduct Elicitation Activity?
Brainstorming
Data Dictionary & Glossary - Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshops - Survey/Questionnaire
Allocate Requirements
Organizational Process Assets - Requirements (Stated) - Solution Scope
8. 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.
Assumptions & Constraints - Required Capabilities - Solution Approach
Reporting
Bottom-up Estimation
Acceptance Criteria
9. 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
Business Analysis Approach
Data Dictionary
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
Rolling Wave
10. This prototype extends the initial interface requirements into a fully functioning system and requires a specialized prototyping tool or language.
Define Business Need - Access Capability Gaps - Determine Solution Approach - Define Solution Scope - Define Business Case
Requirements - Requirements Management Plan
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
Evolutionary or Functional Prototype
11. 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.
Organize Requirements
Stakeholder Matrix - Onion Diagram
Structural Rules
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
12. Use of parameters - multiplied by the number of hours. (COCOMO II - Function Point Counting - Use Case Points - and Story Points)
Decision Analysis - Process Modeling - Structured Walkthrough
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
Assumptions & Constraints - Required Capabilities - Solution Approach
Parametric Estimation
13. 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 -
Problem Solving
Functional Decomposition
Requirements (Traced)
Relationship to Time - Relationship to Task Completion - Relationship to Contracts - Relationships to Formal and Informal Authority
14. What is the output of the task - Prepare Requirements Package?
Tracing Requirements
Requirements Package
Reliability - Validity - Timeliness
Necessity - Effort - Subset - Cover - Value
15. A formal written specification with possible walk-thru - an informal one is possibly verbal or email Communication
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities
Estimation
Formal requirements presentation to stakeholders
Leadership
16. What are the tasks in the knowledge area - Solution Assessment & Validation?
Onion Diagram
Bottom-up Estimation
Requirements (Prioritized and Approved) - Solution (Designed) - Solution Scope
Assess Proposed Solution - Allocate Requirements - Assess Organizational Readiness - Define Transition Requirements - Validate Solution - Evaluate Solution Performance
17. Most optimistic estimate; most pessimistic estimate; most likely estimate
Three-point Estimation
All
Data Dictionary & Glossary - Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshops - Survey/Questionnaire
Requirements Management Plan - Solution Scope - Stakeholder List - Roles & Responsibilities - Stakeholder/Solution or Transition Requirements (Communicated or Traced)
18. What is the output of the task - Define Transition Requirements?
Transition Requirements
Vendor Assessment
Validate Requirements
Document Analysis
19. What are the techniques used in the task - Communicate Requirements?
Confirm Elicitation Results
Requirements Workshop - Structured Walkthrough
Tracing Requirements
Decision Making
20. What are the inputs to the task - Prioritize Requirements?
A statement of the needs of a particular stakeholder or class of stakeholders
Coverage Matrix - Table or spreadsheet used to manage tracing.
Business Case - Business Need - Requirements - Requirements Management Plan - Stakeholder List - Roles & Responsibilities
Elimination
21. What are the likely sources of transition requirements?
Assess Organization Readiness
Data - Ongoing Work - Organizational Change
Business Analysis Approach
Estimation - Functional Decomposition - Risk Analysis
22. 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
Acceptance & Evaluation Criteria Definition - Metrics & KPIs - Prototyping - Risk Analysis - Structured Walkthrough
Business Analysis Approach - Business Analysis Plan - Organizational Process Assets
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
23. 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?
Requirements Structure
Activity List
Business Need - Organizational Process Assets - Required Capabilities
Impact Analysis - Requirements Coverage - Requirements Allocation
24. What is the output of the task Conduct Elicitation Activity?
Requirements (Approved)
Oral Communications - Teaching - Written Communication
Elicitation Results
Business Analysis Planning & Monitoring
25. Business value can be delivered through requirements that support _______________ - alignment with internal standards or policies of the organization - or increased satisfaction for stakeholders - even if those things do not have a direct measurable
Business Case
Compliance with regulatory or other standards
Decision Analysis - Process Modeling - Structured Walkthrough
Relationships - Impact Analysis - Configuration Management System
26. The decomposition of activities and tasks creates?
A statement of the needs of a particular stakeholder or class of stakeholders
Share - Enhance - Exploit
Leadership
Activity List
27. Measures progress towards a strategic goal or objective.
Trustworthiness
Key Performance Indicator (KPI )
Business Rule
Evolutionary or Functional Prototype
28. Describes all the possible outcomes of an attempt to accomplish a particular goal that the solution will support.
Reporting
Business Policy
Use Case
Three-point Estimation
29. Gathering information relevant to a decision - breaking down the information relevant to a decision - making comparisons and tradeoffs between similar and dissimilar options and identifying the option that is most desirable.
Functional Decomposition - Interface Analysis - Scope Modeling - User Stories - Problem or Vision Statement
Decision Analysis
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change
30. Two techniques used in Root Cause Analysis?
Parametric Estimation
Assess Organization Readiness
Fishbone Diagram - Five Whys
Requirements (Maintained and Reusable)
31. 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
Requirements (Stated) - Requirements Structure
Organizational Process Assets - Requirements (Stated) - Solution Scope
Impact Analysis
32. 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.
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Ethics - Trustworthiness - Personal Organization
Allocate Requirements
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
33. What are the techniques used in the task Manage Business Analysis Performance?
Stakeholder Lists - Roles & Responsibilities
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
Interviews - Lessons Learned Process - Metrics and KPIs - Problem Tracking - Process Modeling - Root Cause Analysis - Survey/Questionnaire - Variance Analysis
Activity List
34. Decisions are made with the interest of all stakeholders considered - reasons for a decision are cleared articulated - prompt and full disclosure of conflicts of interest - honesty regarding one's abilities and the performance of one's work.
A statement of the needs of a particular stakeholder or class of stakeholders
Requirements (Verified)
Sequences - Repetitions - Optional Elements
Ethics
35. 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.
Decision Analysis - Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting
Benchmarking
Requirements Analysis
Perform tailoring exercises
36. What are the underlying competencies a BA should possess?
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements
Dependencies
Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
37. 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.
Historic Analysis
Requirements (Traced)
Requirements (Validated)
Document Analysis - SWOT Analysis
38. The minimum set of requirements that must be met in order for a particular solution to be worth implementing.
Key Performance Indicator (KPI )
Requirements Structure
Vertical Prototype
Acceptance Criteria
39. A package should contain a consistent - cohesive and coherent set of requirements. This describes the ____________.
Leadership
Assumptions & Constraints - Required Capabilities - Solution Approach
Stakeholder Matrix - Onion Diagram
Requirements Structure
40. What are the inputs to the task Manage Solution Scope & Requirements?
Requirements Management Plan - Solution Scope - Stakeholder List - Roles & Responsibilities - Stakeholder/Solution or Transition Requirements (Communicated or Traced)
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Trustworthiness
Horizontal Prototype
41. What is the output of the task - Determine Solution Approach?
State Diagrams
Structural Rules
Solution Approach
Discounted Cash Flow - Net Present Value - Internal Rate of Return - Average Rate of Return - Pay Back Period - Cost-Benefit Analysis
42. What are the inputs to the task - Assess Organizational Readiness?
Bottom-up Estimation
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
Metrics & KPIs
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
43. 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
Validate Requirements
Business Need - Enterprise Architecture - Solution Performance Assessment
Requirements Structure
44. Approach to decision making that examines and models the possible consequences of different decisions. Make an optimal decision under conditions of uncertainty.
Requirements (Analyzed)
Solution Scope Definition - Implementation Approach - Dependencies
Three-point Estimation
Decision Analysis
45. Checklist of characteristics to consider when considering non-functional requirements.
Benchmarking
Lessons Learned Process
Requirements Package
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
46. What is the output of the Plan Business Analysis Approach?
Share - Enhance - Exploit
Decision Analysis - Estimation - Metrics & KPIs - Risk Analysis - SWOT Analysis - Vendor Assessment
Business Analysis Approach
Business Analysis Communication Plan - Requirements - Requirements Package
47. A structured way to capture requirements. May be used to scope - discover - define - prioritize and reach closure on requirements for the target system. Considered one of the most effective ways to deliver high quality requirements quickly.
Analytical Thinking & Problem Solving - Behavioral Characteristics - Business Knowledge - Communication Skills - Interaction Skills - Software Application
Requirements Workshop
Organizational Process Assets - Requirements (Stated) - Solution Scope
Sequences - Repetitions - Optional Elements
48. What are the inputs to the task - Specify & Model Requirements?
Advantages of a Data Dictionary & Glossary
Requirements (Stated) - Requirements Structure
Business Goals & Objectives - Requirements (Stated)
Evaluation Criteria
49. What are the inputs to the task - Define Business Need?
Ethics
Structural Rules
Business Goals & Objectives - Requirements (Stated)
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
50. What are the techniques used in the task - Assess Capability Gaps?
Decision Analysis
Document Analysis - SWOT Analysis
This person will be involved in monitoring the performance and effectiveness of a solution or its components.
Requirements (Prioritized and Approved) - Solution (Designed) - Solution Scope