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 shared boundary between any two persons and/or systems through which information is communicated.
Exploratory Prototype
Interface
Indicator
Association
2. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Risk
Constraint
Event Response Table
Metadata
3. 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.
Data Flow Diagram (DFD)
Plan-driven Methodology
Subject Matter Expert (SME)
Requirements Risk Mitigation Strategy
4. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Glossary
Project Manager
Assumption
Operational Support
5. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Quality Attributes
Regulator
Timebox
Requirements Package
6. An informal solicitation of proposals from vendors.
Stakeholder List
Operative Rule(s)
Model(s)
Request For Quote (RFQ)
7. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Implementation Subject Matter Expert (SME)
Constraint
Optionality
Decomposition
8. An analysis model that illustrates the architecture of the system's user interface.
Dialog Map
Regulator
Requirement(s) Attribute
Stakeholder
9. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Attribute
Business Requirements Document
Supplier
Data Flow Diagram (DFD)
10. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Prioritization
Association
Request For Information (RFI)
Organizational Readiness Assessment
11. 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.
Regulator
Metadata
Domain Subject Matter Expert (SME)
End User
12. A system of programming statements symbols and rules used to represent instructions to a computer.
Code
Requirements Management
Organizational Process Asset
Attribute
13. 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.
Data Entity
Exploratory Prototype
Stakeholder List
Quality Attributes
14. A partial or preliminary version of the system.
Business Requirement
Requirements Signoff
Root Cause Analysis
Prototype
15. 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.
Business Analysis
Timebox
Optionality
Knowledge Area
16. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Scenario
Structural Rule
Impact Analysis
Requirements Iteration
17. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Functional Requirement(s)
Lessons Learned Process
Solution
Stakeholder Requirement
18. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Unified Modeling Language (UML)
Temporal Event
Plan-driven Methodology
19. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Organization Modeling
Feature
Functional Requirement(s)
20. 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.
Requirements Trace Matrix
Business Event
Change-driven Methodology
Evolutionary Prototype
21. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Service
Defect
Developer
Product Scope
22. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Root Cause Analysis
Business Goal
Desired Outcome
Business Process
23. A stakeholder person device or system that directly or indirectly accesses a system.
Business Architecture
Structural Rule
Evaluation
User
24. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Project Scope
User Story
Verification
25. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme
Focus Group
User Story
Domain Subject Matter Expert (SME)
Work Product
26. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Business Need(s)
Data Entity
Class Model
Product Backlog
27. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Attribute
Sequence Diagram
Use Case Diagram
28. The human and nonhuman roles that interact with the system.
Actor(s)
Business Analysis
Prioritization
Vision Statement (product vision statement)
29. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Requirements Trace Matrix
Quality Attributes
Interoperability
Code
30. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Unified Modeling Language (UML)
Domain Subject Matter Expert (SME)
Business Case
31. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
Relationship
Cardinality
Process Map
User Acceptance Test
32. A group or person who has interests that may be affected by an initiative or influence over it.
Span of Control
Data Model
Stakeholder
Change Control Board (CCB)
33. A unit of work performed as part of an initiative or process.
Solution Requirement
Requirements Risk Mitigation Strategy
Activity
Customer
34. 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
Attribute
Business Architecture
Feature
Solution Requirement
35. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Vision Statement (product vision statement)
Plan-driven Methodology
Stakeholder List
Stakeholder Analysis
36. An analysis model showing the life cycle of a data entity or class.
Event Response Table
Benchmarking
Brainstorming
State Diagram
37. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Risk
SWOT Analysis
Organization Modeling
Data Entity
38. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Baseline
Business Case
Metadata
39. Ability of systems to communicate by exchanging data or services.
Interoperability
Knowledge Area
Stakeholder Requirement
Walkthrough
40. An analysis model that shows user interface dialogs arranged as hierarchies.
Optionality
Validated Requirements
Organizational Process Asset
Dialog Hierarchy
41. Information that is used to understand the context and validity of information recorded in a system.
Requirements Signoff
Variance Analysis
Monitoring
Metadata
42. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Stakeholder
Capability
Business Goal
Use Case Diagram
43. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Dialog Map
Decision Tables
Repository
Stakeholder Requirement
44. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Validated Requirements
Evolutionary Prototype
Vertical Prototype
SWOT Analysis
45. 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
Process Model
Operative Rule(s)
Cost Benefit Analysis
46. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Analysis Approach
Model(s)
Design Constraints
Technical Constraint(s)
47. Software developed and sold for a particular market.
Validation
Prioritization
Project Scope
Commercial-off-the-Shelf Software (COTS)
48. 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
Model(s)
Organization
Operative Rule(s)
Unified Modeling Language (UML)
49. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Tester
Requirement(s) Defect
Prioritization
Process Model
50. A stakeholder who uses products or services delivered by an organization.
Baseline
Customer
Event Response Table
Verified Requirements