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. 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
Functional Decomposition
Requirements Structure
Learning
Estimation - Functional Decomposition - Risk Analysis

2. This task ensures that requirement specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work. Requirements have been defined correctly.
Business Need - Enterprise Architecture - Solution Performance Assessment
Identified Defects - Mitigating Actions - Solution Validation Assessment
Verify Requirements
Unique Number - Activity Description - Assumptions - Dependencies - Milestones

3. When a conflict arises between stakeholders on one or more documented requirements - the first thing that needs to take place is what?
Use Case
General Purpose Applications & Specialized Applications
To record the conflict in the Requirements Issues Log.
Business Need - Organizational Process Assets - Requirements Management Plan - Scheduled Resources - Solution Scope & Business Case - Supporting Materials

4. 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.
Requirements (Stated) - Requirements Structure
Requirements Analysis
Enterprise Analysis - often the starting point for initiating a new project
Relationships - Impact Analysis - Configuration Management System

5. What is the output of the task - Define Transition Requirements?
Use Case
Business Case
Throw-away Prototype
Transition Requirements

6. What are the techniques used in the task - Organize Requirements?
Requirements (Allocated)
Business Rules Analysis - Data Flow Diagrams - Data Modeling - Functional Decomposition - Organizational Modeling - Process Modeling - Scenarios & Use Cases - Scope Modeling - User Stories
Data - Ongoing Work - Organizational Change
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements

7. What are the tasks in Business Analysis Planning & Monitoring?
Plan Business Analysis Approach - Conduct Stakeholder Analysis - Plan Business Analysis Activities - Plan Business Analysis Communication - Plan Requirements Management Process - Manage BA Performance
Business Requirements - Identified Defects - Solution Performance Metrics - Solution (Deployed)
Business Rules Analysis
Interface Analysis

8. Elements of a Requirements Management Plan include?
Three-point Estimation
Relationships - Impact Analysis - Configuration Management System
Requirements Structure
Decision Analysis

9. This knowledge area describes the tasks that are performed in order to ensure that solutions meet the business need and to facilitate successful implementation.
Requirements Structure
Validate Requirements
Solution Assessment & Validation
Personal Organization

10. What is the output of the task Conduct Stakeholder Analysis?
Requirements Analysis
Acceptance - Transfer - Avoidance - Mitigation
Stakeholder Lists - Roles & Responsibilities
Analytical Thinking & Problem Solving

11. Elicitation Results are the inputs for the ____________
Verify Requirements
Data - Ongoing Work - Organizational Change
Business Need - Enterprise Architecture - Organizational Process Assets
Document Elicitation Results task

12. What are the techniques used in the task Manage Solution Scope & Requirements?
Assessment of Proposed Solution
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
Problem Tracking - Baselining - Signoff
Evaluation

13. This technique shows how information is input - processed - stored and output from a system in a visual representation.
Personal Organization
Business Need - Enterprise Architecture - Solution Performance Assessment
Business Rule
Data Flow Diagrams

14. To define the rules that govern decisions in an organization and that define - constrain or enable organization operations.
Business Rules Analysis
Business Analysis Plan
Business Principals
Advantages of Document Analysis

15. An excellent way to foster creative thinking about a problem. The goal is to produce numerous new ideas and to derive themes for further analysis. - Ability to elicit many ideas in a short time period. - - Non-judgmental environment enables creative
Learning
Dependencies
Cognitive Conflict
Brainstorming

16. What are the elements of Communication Skills?
Automate or Simplify Work - Improve Access to Information - Reduce Complexity of Interfaces - Increase Consistency of Behavior - Eliminate Redundancy
Solution Performance Assessment
Oral Communications - Teaching - Written Communication
Glossary

17. Use of a similar project as the basis for developing estimates for the current project. Also known as "top-down" estimating. This is usually done at the beginning of the project or project phase and more detailed estimates follow as more is known.
Three-point Estimation
Problem Tracking - Risk Analysis
Analogous Estimation
Requirements Structure

18. 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.
Scenarios & Use Cases
Tracing Requirements
Define Business Need - Access Capability Gaps - Determine Solution Approach - Define Solution Scope - Define Business Case
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements

19. To identify and manage areas of uncertainty that can impact an initiative - solution - or organization.
Elimination
Document Analysis
Prepare for Elicitation - Conduct Elicitation Activity - Document Elicitation Results - Confirm Elicitation Results
Risk Analysis

20. 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
Elimination
Stakeholder Concerns
Decision Making
Business Need

21. States the business need - identifies key stakeholders and briefly describes the positive impact that meeting the business need will have on those stakeholders.
Expert Judgment
Oral Communications - Teaching - Written Communication
Requirements Package
Problem or Vision Statement

22. What are the inputs for the task - Define Solution Scope?
Assumptions & Constraints - Required Capabilities - Solution Approach
Functional Decomposition - Interface Analysis - Scope Modeling - User Stories - Problem or Vision Statement
Relationship to Time - Relationship to Task Completion - Relationship to Contracts - Relationships to Formal and Informal Authority
Elimination

23. What is the output of the Manage Business Analysis Performance task?
Ongoing Cost versus Initial Investment - Opportunity Costs - Necessity - Sunk Costs
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 - Requirements Management Plan
Structured Walkthrough

24. 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.
Primary stakeholders in the Organize Requirements task
Prepare for Elicitation - Conduct Elicitation Activity - Document Elicitation Results - Confirm Elicitation Results
Assess Proposed Solution - Allocate Requirements - Assess Organizational Readiness - Define Transition Requirements - Validate Solution - Evaluate Solution Performance
Requirements Workshop

25. Benefits that could have been achieved with an alternative investment rather than this one.
Systems Thinking
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)
Opportunity Cost
Business Analysis Plan

26. What are the elements to the task - Define Business Case?
User Story
Structural Rules
Primary stakeholders in the Organize Requirements task
Benefits - Costs - Risk Assessment - Results Measurement

27. What are the techniques used in the task - Validate Requirements?
Data Dictionary & Glossary
Acceptance & Evaluation Criteria Definition - Metrics & KPIs - Prototyping - Risk Analysis - Structured Walkthrough
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Define Business Case

28. 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.
Formal requirements presentation to stakeholders
Assumptions & Constraints - Requirements (Prioritized and Approved) - Solution Options
Organizational Process Assets - Requirements
Interviews

29. What are the factors of influence by stakeholders on a project?
Compliance with regulatory or other standards
Solution Approach
Elimination
Influence on the project - organizational - project health and other stakeholders

30. A formal written specification with possible walk-thru - an informal one is possibly verbal or email Communication
System
Reporting
Prepare for Elicitation - Conduct Elicitation Activity - Document Elicitation Results - Confirm Elicitation Results
Formal requirements presentation to stakeholders

31. A good indicator has 5 characteristics:
Throw-away Prototype
Benchmarking - Brainstorming - Business Rules Analysis - Focus Groups - Functional Decomposition - Root Cause Analysis
Clear - Relevant - Economical - Adequate - Quantifiable
Analytical Thinking & Problem Solving

32. What are the tasks in the knowledge area - Enterprise Analysis?
Repository - Traceability - Requirement Attributes - Prioritization Process - Change Management - Tailoring the Requirements Management Process
All
Trustworthiness
Define Business Need - Access Capability Gaps - Determine Solution Approach - Define Solution Scope - Define Business Case

33. 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.
Evaluation
Throw-away Prototype
Requirements Structure
Brainstorming

34. What are the attributes of a Data Model?
Solution (Constructed) - Requirements (Prioritized and Validated)
Name - Value/Meanings - Description
Requirements Package
Business Rules Analysis - Data Flow Diagrams - Process Modeling - Organization Modeling - Data Modeling

35. What are the inputs for the task Confirm Elicitation Results?
Advantages of a Data Dictionary & Glossary
Requirements (Stated - Unconfirmed) - Stakeholder Concerns (Unconfirmed)
Estimation - Functional Decomposition - Risk Analysis
Requirements (Any Except Stated)

36. Who is the primary stakeholder in the Define Business Case task?
Prepare Requirements Package
Business Rule
The Sponsor
Lessons Learned Process

37. What are the inputs to the task - Allocate Resources?
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
System
Stakeholder Matrix - Onion Diagram

38. What are the Behavioral Characteristics a BA should exhibit?
Historic Analysis
Opportunity Cost
Ethics - Trustworthiness - Personal Organization
Parametric Estimation

39. 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.
Business Need
Work Breakdown Structure (WBS)
Acceptance & Evaluation Criteria - Decision Analysis - Vendor Assessment
Business Analysis Plan

40. Models a deep - and usually narrow slice of the entire system's functionality.
Vertical Prototype
Stakeholder Matrix - Onion Diagram
Business Goals & Objectives - Requirements (Stated)
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements

41. Understanding of the competitive forces that shape an industry - understand the various customer segments that the industry services and the demographic or other characteristics common to that segment.
Stakeholder Lists - Roles & Responsibilities
Solution Assessment & Validation
Structural Rules
Industry Knowledge

42. 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
Ethics
Prepare Requirements Package
Manage Solution Scope & Requirements - Manage Requirements Traceability - Maintain Requirements for Re-use - Prepare Requirements Package - Communicate Requirements
Acceptance & Evaluation Criteria - Decision Analysis - Vendor Assessment

43. What are the techniques used in the task - Determine Solution Approach?
Evolutionary or Functional Prototype
Define Business Need - Access Capability Gaps - Determine Solution Approach - Define Solution Scope - Define Business Case
Decision Analysis - Focus Groups - Observation - Survey/Questionnaire
Benchmarking - Brainstorming - Decision Analysis - Estimation - SWOT Analysis - Feasibility Analysis

44. Three types of organizational structures
Business Need - Organizational Process Assets - Requirements Management Plan - Scheduled Resources - Solution Scope & Business Case - Supporting Materials
Functions - Markets - Matrix
Decision Analysis
Business Domain - Corporate Culture & Environment - Skills of the Analyst - Requirement Deliverable

45. A continuous process of collecting data to determine how well a solution has been implemented compared to expected results.
Data Modeling
Operative Rules
Evaluation Criteria
Monitoring

46. Three key factors when assessing the quality of indicators and their metrics
Relationships - Impact Analysis - Configuration Management System
Reliability - Validity - Timeliness
Assumptions & Constraints - Required Capabilities - Solution Approach
To record the conflict in the Requirements Issues Log.

47. What are the characteristics of a Problem Record?
Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Problem Tracking - Prototyping - Requirements Workshop - Survey/Questionnaire
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
Share - Enhance - Exploit
Influence on the project - organizational - project health and other stakeholders

48. What are the techniques used in the task - Define Business Case?
Evaluate Solution Performance
Decision Analysis - Estimation - Metrics & KPIs - Risk Analysis - SWOT Analysis - Vendor Assessment
Data Dictionary & Glossary - Brainstorming - Document Analysis - Focus Groups - Interface Analysis - Interviews - Observation - Prototyping - Requirements Workshops - Survey/Questionnaire
Prioritize Requirements - Organize Requirements - Specify & Model Requirements - Define Assumptions & Constraints - Verify Requirements - Validate Requirements

49. Describes all the possible outcomes of an attempt to accomplish a particular goal that the solution will support.
Use Case
Prepare Requirements Package
Risk - assumptions - constraints - etc.
Ethics

50. 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 Analysis
Requirements (Prioritized)
Prototyping
Determine the Process - Who will Authorize Changes - Impact Analysis - Wording of the Request - Coordinate Prioritization of Change