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. 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
Stakeholder Requirement
Project Manager
Business Event
Metadata
2. 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.
User Acceptance Test
Business Constraint(s)
Opportunity Analysis
Business Goal
3. An analysis model describing the data structures and attributes needed by the system.
Evolutionary Prototype
Non-functional Requirement(s)
Black Box Tests
Data Dictionary
4. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Survey
Dialog Map
Sequence Diagram
5. 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.
Metadata
Business Analysis
Decision Tables
Use Case
6. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Stakeholder List
Lessons Learned Process
Elicitation
Code
7. The product capabilities or things the product must do for its users.
Quality
Business Goal
Functional Requirement(s)
Class Model
8. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Return on Investment
User Requirements Document
Requirements Verification
Requirements Management
9. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Domain Subject Matter Expert (SME)
Variance Analysis
Brainstorming
Work Product
10. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Class
Swimlane
Requirements Traceability
Business Constraint(s)
11. All materials used by groups within an organization to define tailor implement and maintain their processes.
Elicitation
Domain Subject Matter Expert (SME)
Organizational Process Asset
Request For Information (RFI)
12. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Stakeholder Requirement
Quality
Problem Statement
Organizational Readiness Assessment
13. Software developed and sold for a particular market.
Class Model
Commercial-off-the-Shelf Software (COTS)
State Diagram
Defect
14. Limitations on the design of a solution that derive from the technology used in its implementation.
Initiative
Vertical Prototype
Technical Constraint(s)
Scope
15. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Walkthrough
Methodology
Requirements Iteration
Document Analysis
16. 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.
Capability
Cost Benefit Analysis
Stakeholder List
Iteration
17. A shared boundary between any two persons and/or systems through which information is communicated.
Methodology
Product Scope
Event
Interface
18. 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
Product Backlog
Supplier
User
19. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Vision Statement (product vision statement)
Requirements Workshop
Tester
20. 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
Business Event
Organization
Requirements Allocation
Incremental Delivery
21. Information that is used to understand the context and validity of information recorded in a system.
Business Analysis Communication Plan
Non-functional Requirement(s)
Change-driven Methodology
Metadata
22. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Peer Review
Requirement(s) Defect
Scenario
Association
23. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Interview
Structural Rule
Plan-driven Methodology
Code
24. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Business Case
User Requirements Document
Objective
25. A group of related tasks that support a key function of business analysis.
Event Response Table
Solution
Tester
Knowledge Area
26. 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
Opportunity Analysis
Swimlane
Class
Business Constraint(s)
27. The human and nonhuman roles that interact with the system.
Process Map
Actor(s)
Business Process
Quality Attributes
28. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Feature
Organization Modeling
Force Field Analysis
Commercial-off-the-Shelf Software (COTS)
29. A model that defines the boundaries of a business domain or solution.
Organization Modeling
Scope Model
Return on Investment
Requirement
30. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Cost Benefit Analysis
Scope Model
Focus Group
Sequence Diagram
31. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Elicitation
Class
Temporal Event
Business Requirements Document
32. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Relationship
Data Dictionary
Swimlane
Iteration
33. Any recognized association of people in the context of an organization or enterprise.
Walkthrough
Initiative
Organizational Unit
Checklist
34. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Subject Matter Expert (SME)
Design Constraints
Decision Analysis
35. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Walkthrough
Stakeholder Analysis
Requirements Package
Sequence Diagram
36. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Walkthrough
Incremental Delivery
Relationship
Validated Requirements
37. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Metric
Quality Assurance
Domain
Decomposition
38. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
Span of Control
Request For Information (RFI)
Implementation Subject Matter Expert (SME)
Solution Scope
39. A system of programming statements symbols and rules used to represent instructions to a computer.
Code
Functional Requirement(s)
Timebox
User Story
40. Metadata related to a requirement used to assist with requirements development and management.
Customer
Context Diagram
Enterprise Architecture
Requirement(s) Attribute
41. Any effort undertaken with a defined goal or objective.
Initiative
Cardinality
Business Event
Data Dictionary
42. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Black Box Tests
Data Model
Product
Requirements Allocation
43. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Supplier
Indicator
Product
Change Control Board (CCB)
44. An analysis model that shows user interface dialogs arranged as hierarchies.
Request For Proposal (RFP)
Timebox
Dialog Hierarchy
Initiative
45. A data element with a specified data type that describes information associated with a concept or entity.
Structured Walkthrough
Temporal Event
User
Attribute
46. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Optionality
Requirements Model
Decision Analysis
Organizational Readiness Assessment
47. A state or condition the business must satisfy to reach its vision.
Customer
Business Goal
Business Analyst
Interview
48. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
User Acceptance Test
External Interfaces
Defect
Scope
49. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Use Case
Product Backlog
Constraint
Tester
50. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.
Supplier
Lessons Learned Process
Event Response Table
Feasibility Study