SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
BABOK
Start Test
Study First
Subjects
:
certifications
,
it-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. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Operative Rule(s)
Class
Requirements Management Tool
Included Use Cases
2. A structured examination of an identified problem to understand the underlying causes.
Interface
Root Cause Analysis
Subject Matter Expert (SME)
System
3. The product capabilities or things the product must do for its users.
Knowledge Area
Peer Review
Functional Requirement(s)
Use Case
4. Software requirements that limit the options available to the system designer.
Design Constraints
Dialog Map
Model(s)
Inspection
5. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Survey
Stakeholder Analysis
Business Analysis Communication Plan
6. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Feature
Constraint
Structural Rule
Analyst
7. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Project
Structured Walkthrough
Gap Analysis
Repository
8. A group or person who has interests that may be affected by an initiative or influence over it.
Root Cause Analysis
Operative Rule(s)
Stakeholder
Cost Benefit Analysis
9. An actor who participates in but does not initiate a use case.
Temporal Event
Peer Review
Secondary Actor
Process Map
10. A measure of the profitability of a project or investment.
Scope Model
Return on Investment
Cardinality
Work Breakdown Structure (WBS)
11. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine
Activity Diagram
Technique
Business Architecture
Regulator
12. A fixed period of time to accomplish a desired outcome.
Timebox
Solution
Regulator
Requirements Iteration
13. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Requirements Trace Matrix
Request For Proposal (RFP)
Impact Analysis
Requirement
14. A state or condition the business must satisfy to reach its vision.
Unified Modeling Language (UML)
Model(s)
Business Rule(s)
Business Goal
15. A type of data model that depicts information groups as classes.
Incremental Delivery
Prototype
Class Model
Requirements Trace Matrix
16. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Span of Control
Black Box Tests
Business Need(s)
Model(s)
17. Ability of systems to communicate by exchanging data or services.
Peer Review
Work Breakdown Structure (WBS)
Solution Scope
Interoperability
18. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
Subject Matter Expert (SME)
Class
Enterprise
Business Constraint(s)
19. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Sequence Diagram
Capability
Domain Subject Matter Expert (SME)
Data Model
20. A non-actionable directive that supports a business goal.
Business Policy
Structural Rule
Scope Model
Work Product
21. Software developed and sold for a particular market.
Commercial-off-the-Shelf Software (COTS)
Brainstorming
Decision Analysis
Data Dictionary
22. Creating working software in multiple releases so the entire product is delivered in portions over time.
Observation
Interface
Product Backlog
Incremental Delivery
23. Something that occurs to which an organizational unit system or process must respond.
SWOT Analysis
Feasibility Study
Event
Sponsor
24. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Business Analysis
Swimlane
Requirements Trace Matrix
Business Need(s)
25. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Technical Constraint(s)
Work Product
Impact Analysis
26. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Prioritization
Return on Investment
Problem Statement
27. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Organization
Business Analysis Approach
Data Entity
Change-driven Methodology
28. The features and functions that characterize a product service or result.
Return on Investment
Baseline
Analyst
Product Scope
29. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Non-functional Requirement(s)
Decision Analysis
Monitoring
Implementation Subject Matter Expert (SME)
30. 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. See also metric indicator and monitoring.
Horizontal Prototype
Fishbone Diagram
Evaluation
Interface
31. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a
Iteration
Walkthrough
Object Oriented Modeling
Risk
32. A data element with a specified data type that describes information associated with a concept or entity.
Stated Requirements
Code
Attribute
Structural Rule
33. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
User Story
Feature
Indicator
Requirements Management Tool
34. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Iteration
Process Model
Quality Attributes
Product Scope
35. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Requirements Validation
Verification
Solution
External Interfaces
36. A shared boundary between any two persons and/or systems through which information is communicated.
Relationship
User
Interface
Deliverable
37. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Work Breakdown Structure (WBS)
Data Dictionary
Interview
Impact Analysis
38. A group of related tasks that support a key function of business analysis.
Requirements Risk Mitigation Strategy
User Requirements Document
Included Use Cases
Knowledge Area
39. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Survey
Actor(s)
Business Requirement
Secondary Actor
40. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Plan-driven Methodology
Business Analyst
Customer
Stakeholder Requirement
41. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Class
Transition Requirement(s)
Assumption
Attribute
42. A prototype that dives into the details of the interface functionality or both.
Product
Temporal Event
Vertical Prototype
Capability
43. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Temporal Event
Business Analysis
Dialog Map
Model(s)
44. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Competitive Analysis
Change-driven Methodology
Sponsor
Business Analysis
45. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti
Stakeholder
Interoperability
Data Flow Diagram (DFD)
Class
46. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Requirement(s) Defect
Use Case Diagram
Secondary Actor
Regulator
47. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Brainstorming
Quality
Objective
Document Analysis
48. A function of an organization that enables it to achieve a business goal or objective.
Temporal Event
Quality Attributes
Capability
Product
49. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Use Case
Defect
Requirements Package
Developer
50. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Survey
Business Domain Model
Feature
Dialog Hierarchy