Business Analysis Body of Knowledge (BABOK) MCQs

Business Analysis Body of Knowledge (BABOK) MCQs

These Business Analysis Body of Knowledge (BABOK) multiple-choice questions and their answers will help you strengthen your grip on the subject of Business Analysis Body of Knowledge (BABOK). You can prepare for an upcoming exam or job interview with these 30 Business Analysis Body of Knowledge (BABOK) MCQs.
So scroll down and start answering.

1: A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.

A.   Monitoring

B.   Interface

C.   Included Use Cases

D.   Model(s)

2: An assessment of the costs and benefits associated with a proposed initiative.

A.   Scenario

B.   Feature

C.   Business Case

D.   Subject Matter Expert (SME)

3: A stakeholder person device or system that directly or indirectly accesses a system.

A.   User

B.   Data Flow Diagram (DFD)

C.   Repository

D.   Metadata

4: The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.

A.   Stakeholder Analysis

B.   Relationship Map

C.   Request For Information (RFI)

D.   Requirements Iteration

5: A real or virtual facility where all information on a specific topic is stored and is available for retrieval.

A.   Data Entity

B.   Stakeholder Analysis

C.   Work Breakdown Structure (WBS)

D.   Repository

6: Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various

A.   Optionality

B.   Stakeholder Requirement

C.   System

D.   Business Analysis Communication Plan

7: A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.

A.   Commercial-off-the-Shelf Software (COTS)

B.   Business Case

C.   Vertical Prototype

D.   Relationship Map

8: Any recognized association of people in the context of an organization or enterprise.

A.   Temporal Event

B.   Organizational Unit

C.   Vision Statement (product vision statement)

D.   Swimlane

9: The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.

A.   Vertical Prototype

B.   Prioritization

C.   Class

D.   Swimlane

10: A stakeholder who uses products or services delivered by an organization.

A.   Walkthrough

B.   Analyst

C.   Benchmarking

D.   Customer

11: An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.

A.   Business Analysis Approach

B.   Activity

C.   Requirements Package

D.   Context Diagram

12: A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.

A.   Methodology

B.   Implementation Subject Matter Expert (SME)

C.   Requirements Management Plan

D.   Inspection

13: The number of employees a manger is directly (or indirectly) responsible for.

A.   Requirement

B.   Functional Requirement(s)

C.   Span of Control

D.   Data Model

14: A temporary endeavor undertaken to create a unique product service or result.

A.   Requirements Iteration

B.   Project

C.   Project Charter

D.   Organization Modeling

15: A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.

A.   Business Need(s)

B.   Throw-away Prototype

C.   Methodology

D.   Elicitation

16: A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.

A.   Transition Requirement(s)

B.   Software/Systems Requirements Specification

C.   Organizational Readiness Assessment

D.   Design Constraints

17: A system trigger that is initiated by time.

A.   Event

B.   Business Policy

C.   Temporal Event

D.   Validation

18: A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode

A.   Business Domain Model

B.   Requirements Model

C.   Data Model

D.   Business Architecture

19: The product capabilities or things the product must do for its users.

A.   Project Manager

B.   Validation

C.   Sponsor

D.   Functional Requirement(s)

20: A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.

A.   Actor(s)

B.   Walkthrough

C.   Enterprise Architecture

D.   Business Analysis Communication Plan

21: A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.

A.   Requirements Management Tool

B.   Decision Tables

C.   Requirement

D.   Decomposition

22: A structured examination of an identified problem to understand the underlying causes.

A.   Root Cause Analysis

B.   Technical Constraint(s)

C.   Prototype

D.   Commercial-off-the-Shelf Software (COTS)

23: A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.

A.   Root Cause Analysis

B.   Incremental Delivery

C.   Process Map

D.   Checklist

24: Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.

A.   SWOT Analysis

B.   Solution Scope

C.   Indicator

D.   Evaluation

25: A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.

A.   Metric

B.   Work Breakdown Structure (WBS)

C.   Deliverable

D.   Activity Diagram

26: A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.

A.   Baseline

B.   Problem Statement

C.   Methodology

D.   Root Cause Analysis

27: A partial or preliminary version of the system.

A.   Developer

B.   Structural Rule

C.   Prototype

D.   Activity Diagram

28: A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.

A.   Force Field Analysis

B.   Analyst

C.   Business Need(s)

D.   Verification

29: A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.

A.   Incremental Delivery

B.   Gap Analysis

C.   Swimlane

D.   Solution Requirement

30: A type of diagram defined by UML that captures all actors and use cases involved with a system or product.

A.   Functional Requirement(s)

B.   Use Case Diagram

C.   Peer Review

D.   Business Need(s)