🧪 Business Analyst MCQ Quiz Hub

1. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Functional Requirement(s)
Use Case Diagram
Peer Review
Business Need(s)

2. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Monitoring
Interface
Included Use Cases
Model(s)

3. An assessment of the costs and benefits associated with a proposed initiative.
Scenario
Feature
Business Case
Subject Matter Expert (SME)

4. A stakeholder person device or system that directly or indirectly accesses a system.
User
Data Flow Diagram (DFD)
Repository
Metadata

5. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Relationship Map
Request For Information (RFI)
Requirements Iteration

6. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Data Entity
Stakeholder Analysis
Work Breakdown Structure (WBS)
Repository

7. 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
Optionality
Stakeholder Requirement
System
Business Analysis Communication Plan

8. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Commercial-off-the-Shelf Software (COTS)
Business Case
Vertical Prototype
Relationship Map

9. Any recognized association of people in the context of an organization or enterprise.
Temporal Event
Organizational Unit
Vision Statement (product vision statement)
Swimlane

10. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Vertical Prototype
Prioritization
Class
Swimlane

11. A stakeholder who uses products or services delivered by an organization.
Walkthrough
Analyst
Benchmarking
Customer

12. 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.
Business Analysis Approach
Activity
Requirements Package
Context Diagram

13. 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.
Methodology
Implementation Subject Matter Expert (SME)
Requirements Management Plan
Inspection

14. The number of employees a manger is directly (or indirectly) responsible for.
Requirement
Functional Requirement(s)
Span of Control
Data Model

15. A temporary endeavor undertaken to create a unique product service or result.
Requirements Iteration
Project✔
Project Charter
Organization Modeling

16. 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.
Business Need(s)
Throw-away Prototype
Methodology
Elicitation

17. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Transition Requirement(s)
Software/Systems Requirements Specification
Organizational Readiness Assessment
Design Constraints

18. A system trigger that is initiated by time.
Event
Business Policy
Temporal Event
Validation

19. 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
Business Domain Model
Requirements Model
Data Model
Business Architecture

20. The product capabilities or things the product must do for its users.
Project Manager
Validation
Sponsor
Functional Requirement(s)

21. 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.
Actor(s)
Actor(s)
Enterprise Architecture
Business Analysis Communication Plan

22. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Requirements Management Tool
Decision Tables
Requirement
Decomposition

23. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
Technical Constraint(s)
Prototype
Commercial-off-the-Shelf Software (COTS)

24. 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.
Root Cause Analysis
Incremental Delivery
Process Map
Checklist

25. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Solution Scope
Indicator
Evaluation

26. 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.
Metric
Work Breakdown Structure (WBS)
Deliverable
Activity Diagram

27. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Baseline
Problem Statement
Methodology
Root Cause Analysis

28. A partial or preliminary version of the system.
Developer
Structural Rule
Prototype
Activity Diagram

29. 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.
Force Field Analysis
Analyst
Business Need(s)
Verification

30. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Incremental Delivery
Gap Analysis
Swimlane
Solution Requirement