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 business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Organizational Unit
Capability
Relationship Map
Dialog Hierarchy
2. 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.
Subject Matter Expert (SME)
Plan-driven Methodology
Developer
Context Diagram
3. 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
Methodology
Class Model
Quality
4. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Constraint
Change-driven Methodology
Quality
5. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Feature
Business Analysis Plan
Objective
Design Constraints
6. 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.
Requirements Allocation
Fishbone Diagram
Requirement
Business Analysis Plan
7. A description of the requirements management process.
Scope Model
Benchmarking
Requirements Management Plan
Defect
8. A system trigger that is initiated by humans.
Swimlane
Business Event
Initiative
Decision Analysis
9. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Black Box Tests
Product Backlog
Business Analysis
Project Manager
10. 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
Cardinality
Code
Object Oriented Modeling
Requirements Management Tool
11. A system trigger that is initiated by time.
Inspection
Requirements Workshop
Temporal Event
Monitoring
12. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Business Analysis
Constraint
Business Requirements Document
Code
13. The work that must be performed to deliver a product service or result with the specified features and functions.
Observation
Project Scope
Monitoring
Black Box Tests
14. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Initiative
Unified Modeling Language (UML)
Business Policy
Elicitation
15. Information that is used to understand the context and validity of information recorded in a system.
Data Model
Use Case Diagram
Metadata
Request For Information (RFI)
16. A practitioner of business analysis.
Request For Information (RFI)
Optionality
Work Product
Business Analyst
17. 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.
Requirements Management Tool
Requirements Traceability
Cost Benefit Analysis
Work Breakdown Structure (WBS)
18. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Feature
Objective
Business Requirement
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 Need(s)
Business Domain Model
Cost Benefit Analysis
User Requirements Document
20. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Product Backlog
End User
Supplier
Prioritization
21. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Validated Requirements
Focus Group
Scope Model
Business Requirements Document
22. 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.
Project Scope
Knowledge Area
Change-driven Methodology
Requirements Trace Matrix
23. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Association
Brainstorming
Lessons Learned Process
Technique
24. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Opportunity Analysis
Methodology
Requirement
Technical Constraint(s)
25. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Methodology
Evolutionary Prototype
Indicator
Event
26. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Organization Modeling
Glossary
Stakeholder Analysis
Non-functional Requirement(s)
27. Any recognized association of people in the context of an organization or enterprise.
Stakeholder Requirement
Organization Modeling
Work Product
Organizational Unit
28. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
Requirements Risk Mitigation Strategy
Object Oriented Modeling
Opportunity Analysis
Requirements Iteration
29. The area covered by a particular activity or topic of interest.
Scope
Stakeholder
SWOT Analysis
Business Analysis
30. The product capabilities or things the product must do for its users.
Metadata
Functional Requirement(s)
Context Diagram
Organizational Readiness Assessment
31. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Business Analysis Communication Plan
Vision Statement (product vision statement)
Decision Tables
Gap Analysis
32. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Requirements Model
Requirement(s) Defect
Project Scope
Glossary
33. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Timebox
Incremental Delivery
Project Scope
Baseline
34. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Design Constraints
Change Control Board (CCB)
Business Analysis
Context Diagram
35. Something that occurs to which an organizational unit system or process must respond.
Project Scope
Business Analysis Approach
Class
Event
36. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Interoperability
Lessons Learned Process
Regulator
Solution
37. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Iteration
Requirements Iteration
Business Process
Requirements Traceability
38. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Business Analyst
Root Cause Analysis
Competitive Analysis
Activity
39. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Desired Outcome
Indicator
Methodology
Request For Proposal (RFP)
40. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Change-driven Methodology
Capability
Organization Modeling
Decision Tree
41. 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.
Actor(s)
Context Diagram
Inspection
Peer Review
42. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Business Analyst
Horizontal Prototype
Class
Evaluation
43. A stakeholder who provides products or services to an organization.
Business Architecture
Organizational Unit
Supplier
Competitive Analysis
44. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Activity Diagram
Business Case
Metadata
Problem Statement
45. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Requirements Workshop
Black Box Tests
Enterprise Architecture
Class
46. 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
Project
Verified Requirements
Technique
Request For Proposal (RFP)
47. Ability of systems to communicate by exchanging data or services.
Desired Outcome
Solution Requirement
Operational Support
Interoperability
48. A system of programming statements symbols and rules used to represent instructions to a computer.
Cardinality
Transition Requirement(s)
Code
Fishbone Diagram
49. Any unique and verifiable work product or service that a party has agreed to deliver.
Change Control Board (CCB)
Business Analysis
Deliverable
Metric
50. 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.
Assumption
Enterprise Architecture
Business Analysis
Operational Support