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 model that defines the boundaries of a business domain or solution.
Metric
Scope Model
Requirements Model
Stakeholder Requirement
2. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
System
Solution Requirement
Baseline
End User
3. An analysis model describing the data structures and attributes needed by the system.
Metadata
Walkthrough
Data Dictionary
Survey
4. A link between two elements or objects in a diagram.
Entity-Relationship Diagram
Model(s)
Context Diagram
Association
5. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Span of Control
Swimlane
Work Product
Plan-driven Methodology
6. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Request For Information (RFI)
Walkthrough
Timebox
Structural Rule
7. 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
Business Architecture
Domain
Developer
Scope
8. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Plan-driven Methodology
Peer Review
Technique
Organizational Unit
9. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Implementation Subject Matter Expert (SME)
Subject Matter Expert (SME)
Peer Review
Requirement(s) Defect
10. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Requirement(s) Attribute
Code
Swimlane
Validated Requirements
11. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Data Model
Validation
Requirements Validation
Business Rule(s)
12. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Defect
Use Case Diagram
Span of Control
13. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User Requirements Document
Change Control Board (CCB)
Scope Model
Customer
14. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Tester
Business Analyst
Document Analysis
Service
15. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Requirements Allocation
Requirements Package
Design Constraints
16. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Supplier
Verification
Benchmarking
Work Product
17. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Timebox
Baseline
Assumption
Metric
18. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Swimlane
Organization Modeling
Quality
Commercial-off-the-Shelf Software (COTS)
19. An analysis model showing the life cycle of a data entity or class.
State Diagram
Dialog Hierarchy
Request For Quote (RFQ)
Checklist
20. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Requirements Package
Initiative
Force Field Analysis
External Interfaces
21. A system trigger that is initiated by time.
Temporal Event
Organizational Process Asset
Business Process
Metric
22. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Prioritization
Requirements Package
Change Control Board (CCB)
23. A solution or component of a solution that is the result of a project.
Product
Knowledge Area
Commercial-off-the-Shelf Software (COTS)
Observation
24. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Business Constraint(s)
Requirements Management Plan
Decision Tree
Decision Analysis
25. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.
Business Analysis Communication Plan
Risk
Swimlane
Business Analyst
26. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Data Flow Diagram (DFD)
Problem Statement
Cost Benefit Analysis
27. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Elicitation
Checklist
Event
Data Flow Diagram (DFD)
28. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Repository
Evolutionary Prototype
Incremental Delivery
Cost Benefit Analysis
29. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Requirements Iteration
External Interfaces
Product Backlog
Competitive Analysis
30. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
Requirements Allocation
Force Field Analysis
End User
Checklist
31. A prototype that dives into the details of the interface functionality or both.
Change Control Board (CCB)
Product
Vertical Prototype
Monitoring
32. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Stakeholder List
External Interfaces
Glossary
33. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Rule(s)
Business Analysis Approach
Vertical Prototype
Event Response Table
34. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Business Analysis Plan
End User
Requirements Trace Matrix
Prioritization
35. A specific actionable testable directive that is under the control of the business and supports a business policy.
Survey
Business Analyst
Change-driven Methodology
Business Rule(s)
36. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Stakeholder List
Metric
Variance Analysis
Knowledge Area
37. 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
Transition Requirement(s)
Business Analysis Approach
Tester
Throw-away Prototype
38. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Business Analysis
Solution
Gap Analysis
Business Requirements Document
39. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.
SWOT Analysis
Defect
Requirement
Force Field Analysis
40. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Timebox
Brainstorming
Analyst
Optionality
41. Any recognized association of people in the context of an organization or enterprise.
Black Box Tests
Organizational Unit
Metadata
Cardinality
42. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Stakeholder Analysis
Feature
Gap Analysis
Requirement
43. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
User Acceptance Test
Cardinality
Fishbone Diagram
Stakeholder
44. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Project Scope
Organization
Solution Requirement
Force Field Analysis
45. The human and nonhuman roles that interact with the system.
Desired Outcome
Peer Review
Actor(s)
Tester
46. The work that must be performed to deliver a product service or result with the specified features and functions.
Verified Requirements
Swimlane
Project Scope
Interface
47. A system of programming statements symbols and rules used to represent instructions to a computer.
Requirement
Code
Enterprise
Business Analysis Plan
48. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Interoperability
Model(s)
Prioritization
Work Breakdown Structure (WBS)
49. 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.
Solution Scope
Exploratory Prototype
Walkthrough
Indicator
50. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
End User
Business Constraint(s)
Prototype
Opportunity Analysis