Test your basic knowledge |

CBAP Business Analysis And Planning

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. Characteristics that are common to all organizations with a similar purpose and structure - whether or not the are in the same industry.
Fishbone Diagram - Five Whys
Business Principals
Solution Knowledge
Name - Value/Meanings - Description

2. What is the output of the task Prepare for Elicitation?
Scheduled Resources - Supporting Materials
Requirements - Requirements Management Plan
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability
Stakeholder Concerns

3. What are the tasks in the knowledge area - Solution Assessment & Validation?
Three-point Estimation
Assess Proposed Solution - Allocate Requirements - Assess Organizational Readiness - Define Transition Requirements - Validate Solution - Evaluate Solution Performance
Requirements (Any Except Stated)
Vertical Prototype

4. The skill of moderating discussions among a group or enable all participants to effectively articulate their views on a topic under discussion and to further ensure that participants in the discussion are able to recognize and appreciate the differin
Structural Rules
Ongoing Cost versus Initial Investment - Opportunity Costs - Necessity - Sunk Costs
Facilitation
Prepare Requirements Package

5. What does RACI stand for?
Assess Organization Readiness
Acceptance & Evaluation Criteria - Business Rules Analysis - Decision Analysis - Functional Decomposition - Process Modeling - Scenarios & Use Cases
Responsible - Accountable - Consulted - Informed
Prototyping

6. 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.
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
Lessons Learned Process
Formal requirements presentation to stakeholders
Historic Analysis

7. Knowing the dependencies and relationships between requirements helps when determining the sequence in which requirements are to be addressed. Common relations are:
Assessment of Proposed Solution
The Business Analysis Communication Plan
Necessity - Effort - Subset - Cover - Value
Reliability - Performance Efficiency - Operability - Security - Compatibility - Maintainability - Transferability

8. What are the techniques used in Plan Business Analysis Approach?
Creative Thinking - Decision Making - Learning - Problem Solving - Systems Thinking
Decision Analysis - Process Modeling - Structured Walkthrough
Solution Approach
Scheduled Resources - Supporting Materials

9. This prototype extends the initial interface requirements into a fully functioning system and requires a specialized prototyping tool or language.
Requirements Management Plan - Solution Scope - Stakeholder List - Roles & Responsibilities - Stakeholder/Solution or Transition Requirements (Communicated or Traced)
Evolutionary or Functional Prototype
Business Rules Analysis - Data Flow Diagrams - Process Modeling - Organization Modeling - Data Modeling
Solution (Constructed) - Requirements (Prioritized and Validated)

10. What are the tasks for the knowledge area - Requirements Management & Communication?
Enterprise Analysis
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
That they understand them and the current state the requirements are in
Goals

11. What are the inputs to the task - Assess Organizational Readiness?
Communicated Requirements
Three-point Estimation
Enterprise Architecture - Solution Scope - Solution (Designed) - Stakeholder Concerns
Decision Analysis - Process Modeling - Structured Walkthrough

12. What is the output of the task - Maintain Requirements for Re-use?
Survey/Questionnaire
Implementation SME
Requirements (Maintained and Reusable)
Sequence Diagrams

13. What are the techniques used in the task Conduct Stakeholder Analysis?
Business Analysis Approach
Problem Solving
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
To record the conflict in the Requirements Issues Log.

14. This knowledge area describes the tasks that are performed in order to ensure that solutions meet the business need and to facilitate successful implementation.
Solution Assessment & Validation
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Coverage Matrix - Table or spreadsheet used to manage tracing.

15. What are the techniques used in the task - Validate Solution?
Solution Knowledge
Requirements (Stated - Confirmed) - Stakeholder Concerns (Confirmed)
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
Decision Analysis

16. States the business need - identifies key stakeholders and briefly describes the positive impact that meeting the business need will have on those stakeholders.
Problem or Vision Statement
Operative Rules
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
Requirements (Stated) - Requirements Structure

17. What is the output of the task - Define Transition Requirements?
Transition Requirements
Cognitive Conflict
Visual Learner - Auditory Learner - Kinesthetic Learner
Validate Solution

18. What is a STAKEHOLDER requirement - according to the BABOK 2.0?
A statement of the needs of a particular stakeholder or class of stakeholders
SWOT Analysis
Vendor Assessment
Requirements Management Plan

19. What are the inputs to the task Conduct Stakeholder Analysis?
Prototyping
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
Business Need - Enterprise Architecture - Organizational Process Assets
Business Need - Solution Scope & Business Case - Stakeholder List - Roles & Responsibilities

20. 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.
Ethics
Business Rule
Work Breakdown Structure (WBS)
Assumptions & Constraints - Required Capabilities - Solution Approach

21. 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.
Tracing Requirements
Business Case; Stakeholder - Solution or Transition Requirements (Verified)
Acceptance & Evaluation Criteria - Problem Tracking - Root Cause Analysis
User Story

22. Name the 2 types of Software categories that assist in BA productivity.
BABOK
General Purpose Applications & Specialized Applications
Acceptance & Evaluation Technique
Unique Number - Activity Description - Assumptions - Dependencies - Milestones

23. This task describes the work required to decide which formats are appropriate for a particular project and its stakeholders. The requirements must be clear - concise - accurate and at the appropriate level of detail to assure clear understanding by t
Delphi Estimation
Prepare Requirements Package
Advantages of a Data Dictionary & Glossary
Interface Analysis

24. The decomposition of activities and tasks creates?
Activity List
Data Flow Diagrams
Prepare for Elicitation - Conduct Elicitation Activity - Document Elicitation Results - Confirm Elicitation Results
Scheduled Resources - Supporting Materials

25. What are the tasks in the knowledge area - Requirements Analysis?
Requirements Workshop - Structured Walkthrough
Oral Communications - Teaching - Written Communication
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
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements

26. What are the inputs to the task - Determine Solution Approach?
Business Analysis Plan
Analogous Estimation
Business Case; Stakeholder - Solution or Transition Requirements (Verified)
Business Need - Organizational Process Assets - Required Capabilities

27. Use of parameters - multiplied by the number of hours. (COCOMO II - Function Point Counting - Use Case Points - and Story Points)
Scenario
Parametric Estimation
Observation
Implementation Approach

28. What are the techniques for the task - Verify Requirements?
Structural Rules
Acceptance & Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough - Checklists
Required Capabilities
Requirements Package

29. What are the 3 elements in the Assess Organizational Readiness?
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Organizational Process Assets - Requirements (Stated) - Solution Scope
Impact Analysis
A statement of the needs of a particular stakeholder or class of stakeholders

30. What is the output of the task Document Elicitation Results?
The Business Analysis Communication Plan
Requirements (Stated) - Stakeholder Concerns
Organizational Process Assets - Requirements
Prototyping

31. What is the output of the task Plan Business Analysis Activities?
Discounted Cash Flow - Net Present Value - Internal Rate of Return - Average Rate of Return - Pay Back Period - Cost-Benefit Analysis
Business Analysis Plan
Cultural Assessment - Operational or Technical Assessment - Stakeholder Impact Analysis
Name - Aliases - Values/Meanings - Description

32. 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
Problem Tracking
Risk - assumptions - constraints - etc.
Share - Enhance - Exploit
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire

33. What are the techniques used in the task Manage Solution Scope & Requirements?
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshop - Survey/Questionnaire
Problem Tracking - Baselining - Signoff
Ethics - Trustworthiness - Personal Organization
Systems Thinking

34. Prioritizes requirements based on a allocated fixed amount of money.
Risk Analysis
Clear - Relevant - Economical - Adequate - Quantifiable
Organizational Readiness Assessment - Requirements (Stated) - Solution (Deployed) - Solution (Designed)
Budgeting

35. What are the inputs to the task - Allocate Resources?
Requirements (Prioritized and Approved) - Solution (Designed) - Solution Scope
Organizational Knowledge
Business Analysis Plan
Survey/Questionnaire

36. 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
Horizontal Prototype
Formal Documentation - Presentation - Model
Requirements Structure
Requirements Documentation - Requirements for Vendor Selection

37. What are the elements of the area - Analytical Thinking and Problem Solving - Successful generation of new ideas - application of new ideas to resolve existing problems - willingness of stakeholders to accept new approaches.
Business Policy
Prototyping
Creative Thinking - Decision Making - Learning - Problem Solving - Systems Thinking
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)

38. What is the output of the task - Manage Requirements Traceability?
Vendor Assessment
Decision Making
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
Requirements (Traced)

39. 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. -
Survey/Questionnaire
Document Analysis
Facilitation
User Story

40. What are the Cultural diversity issues that should be taken into account when planning communication?
Solution Approach
Relationship to Time - Relationship to Task Completion - Relationship to Contracts - Relationships to Formal and Informal Authority
Estimation
Business Rules Analysis

41. This technique represents the types of peoples - places - things and concepts that are important to the business - attributes associated with them and the significant business relationships among them.
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
Risk - assumptions - constraints - etc.
Solution Knowledge
Data Modeling

42. Two effective trade-off methods.
Coverage Matrix - Table or spreadsheet used to manage tracing.
They describe what a solution must be capable of doing to meet the needs of one or more stakeholder groups
Elimination of Dominated Alternative - Ranking Objects on a Similar Scale
Business Analysis Performance Metrics - Business Analysis Plan - Organization Performance Standards - Requirements Management Plan

43. Business rules require a defined glossary of terms and an understanding of the relationships between them - this is known as:
This person will be involved in monitoring the performance and effectiveness of a solution or its components.
Ethics - Trustworthiness - Personal Organization
Term and Fact Model
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change

44. What is the output of the task Conduct Stakeholder Analysis?
Stakeholder Lists - Roles & Responsibilities
Strengths - Weaknesses
Structural Rules
Compliance with regulatory or other standards

45. What are the techniques used in the task - Organize Requirements?
Business Rules Analysis - Data Flow Diagrams - Process Modeling - Organization Modeling - Data Modeling
Business Rules Analysis - Data Flow Diagrams - Data Modeling - Functional Decomposition - Organizational Modeling - Process Modeling - Scenarios & Use Cases - Scope Modeling - User Stories
Coverage Matrix - Table or spreadsheet used to manage tracing.
Business Analysis Plan

46. A good indicator has 5 characteristics:
Acceptance & Evaluation Criteria - Data Flow Diagrams - Process Models - Focus Groups - Interviews - Survey/Questionnaire - Organizational Modeling - Problem Tracking - Risk Analysis - SWOT Analysis - Force Field Analysis
Decision Analysis - Problem Tacking - Risk Analysis
Clear - Relevant - Economical - Adequate - Quantifiable
Trustworthiness

47. Elements of a Requirements Management Plan include?
Relationships - Impact Analysis - Configuration Management System
That they understand them and the current state the requirements are in
Decision Analysis - Problem Tacking - Risk Analysis
Solution (Constructed) - Requirements (Prioritized and Validated)

48. What are the inputs to the Plan Business Analysis Approach?
Metrics & KPIs
Requirements (Allocated)
Formal requirements presentation to stakeholders
Business Need - Expert Judgment - Organizational Process Assets

49. The purpose is to measure the performance of solutions - solution components - and other matters of interest to stakeholders.
Functions - Markets - Matrix
Observation
Metrics & KPIs
Organization Modeling

50. Divides requirements into 4 categories - Must - Should - Could - Won't
Absolute Reference - Author - Complexity - Ownership - Priority - Risks - Source - Stability - Status - Urgency
MoSCoW Analysis
Organizational Process Assets - Requirements (Stated) - Solution Scope
Dependencies