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 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
Activity
Data Flow Diagram (DFD)
Relationship
User Story
2. 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
Solution Requirement
Request For Proposal (RFP)
Incremental Delivery
Stakeholder
3. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Change Control Board (CCB)
Sponsor
Requirements Management Tool
Organizational Unit
4. 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.
Competitive Analysis
Requirement(s) Defect
Implementation Subject Matter Expert (SME)
Product Backlog
5. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Assumption
Feasibility Study
Data Entity
Use Case Diagram
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.
Relationship
Elicitation
Iteration
Business Need(s)
7. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Exploratory Prototype
Structural Rule
Decomposition
8. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Organizational Unit
Requirements Allocation
Survey
Business Architecture
9. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Business Analysis Communication Plan
Optionality
Walkthrough
Structured Walkthrough
10. 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.
Evaluation
Glossary
Problem Statement
Customer
11. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Domain
Model(s)
Gap Analysis
Enterprise
12. A link between two elements or objects in a diagram.
Supplier
Requirements Validation
Association
Request For Information (RFI)
13. The features and functions that characterize a product service or result.
Event
Throw-away Prototype
Product Scope
Work Product
14. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Decomposition
Process Map
Analyst
Baseline
15. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Requirements Signoff
Business Analysis Approach
Defect
16. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Change Control Board (CCB)
Technical Constraint(s)
Cardinality
Swimlane
17. An analysis model showing the life cycle of a data entity or class.
Product Backlog
Validated Requirements
Scenario
State Diagram
18. 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
Feature
Cardinality
Regulator
19. A partial or preliminary version of the system.
Capability
Prototype
Change Control Board (CCB)
Benchmarking
20. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Association
Work Breakdown Structure (WBS)
Stakeholder List
Decomposition
21. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Data Entity
Validated Requirements
Analyst
Class
22. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Scope
Data Flow Diagram (DFD)
Secondary Actor
Operational Support
23. The quality attributes design and implementation constraints and external interfaces that the product must have.
Business Analysis
Relationship Map
Subject Matter Expert (SME)
Non-functional Requirement(s)
24. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
External Interfaces
Event
Fishbone Diagram
25. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Walkthrough
Risk
Validated Requirements
26. A group of related tasks that support a key function of business analysis.
Requirements Traceability
Checklist
Knowledge Area
Organization Modeling
27. 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.
Return on Investment
Walkthrough
Force Field Analysis
Black Box Tests
28. Information that is used to understand the context and validity of information recorded in a system.
Product
Unified Modeling Language (UML)
Transition Requirement(s)
Metadata
29. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Checklist
Scenario
Metric
User Requirements Document
30. 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
Business Constraint(s)
Requirements Management
User
Business Architecture
31. The product capabilities or things the product must do for its users.
Implementation Subject Matter Expert (SME)
Technique
Functional Requirement(s)
Force Field Analysis
32. A model that defines the boundaries of a business domain or solution.
Span of Control
Metric
Scope Model
Focus Group
33. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Impact Analysis
Organization
Optionality
Problem Statement
34. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Analyst
Vision Statement (product vision statement)
Project Scope
Data Model
35. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Problem Statement
State Diagram
Feasibility Study
User Story
36. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
System
Variance Analysis
Initiative
37. Metadata related to a requirement used to assist with requirements development and management.
Timebox
Product
Business Need(s)
Requirement(s) Attribute
38. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
SWOT Analysis
Project Manager
Use Case
Model(s)
39. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Defect
Desired Outcome
Validated Requirements
Stakeholder Analysis
40. 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
Object Oriented Modeling
Product Scope
Risk
Organizational Readiness Assessment
41. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Prioritization
Timebox
Product Backlog
Assumption
42. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
User Story
Implementation Subject Matter Expert (SME)
Quality Attributes
Requirements Risk Mitigation Strategy
43. 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.
Business Analysis
Object Oriented Modeling
Sequence Diagram
Activity Diagram
44. 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.
Data Dictionary
Enterprise
Interface
Sequence Diagram
45. An informal solicitation of proposals from vendors.
Repository
Request For Quote (RFQ)
Horizontal Prototype
Business Analyst
46. 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.
End User
Business Requirement
Operative Rule(s)
Association
47. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Activity
Enterprise
Organization Modeling
Requirement(s) Defect
48. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Data Model
Quality
Service
Requirements Iteration
49. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Throw-away Prototype
Domain
Unified Modeling Language (UML)
Supplier
50. 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.
Competitive Analysis
Technical Constraint(s)
Data Dictionary
Evolutionary Prototype