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 stakeholder with legal or governance authority over the solution or the process used to develop it.
Variance Analysis
Requirements Verification
Timebox
Regulator
2. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
Objective
Technical Constraint(s)
Interoperability
3. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Project Charter
Data Model
Developer
Operational Support
4. A shared boundary between any two persons and/or systems through which information is communicated.
Checklist
Interface
Commercial-off-the-Shelf Software (COTS)
Supplier
5. A data element with a specified data type that describes information associated with a concept or entity.
Decision Tree
Attribute
Solution
Technique
6. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Requirements Risk Mitigation Strategy
Activity Diagram
Inspection
System
7. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Data Model
Request For Proposal (RFP)
Regulator
Decomposition
8. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Use Case
Data Entity
Enterprise Architecture
Requirements Allocation
9. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.
Gap Analysis
Verification
Secondary Actor
Data Flow Diagram (DFD)
10. An analysis model that shows user interface dialogs arranged as hierarchies.
Commercial-off-the-Shelf Software (COTS)
Baseline
Dialog Hierarchy
Business Architecture
11. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Flow Diagram (DFD)
Requirement(s) Defect
Objective
Business Constraint(s)
12. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Class Model
Dialog Map
Association
13. 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.
Request For Quote (RFQ)
Decision Tree
Business Goal
Event Response Table
14. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Data Entity
Requirement
Vision Statement (product vision statement)
Context Diagram
15. A description of the requirements management process.
Project Scope
Timebox
Domain
Requirements Management Plan
16. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Business Analysis
Solution
End User
Organizational Unit
17. A solution or component of a solution that is the result of a project.
Structural Rule
Implementation Subject Matter Expert (SME)
Product
Verified Requirements
18. 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.
Context Diagram
Business Policy
Quality
Organization Modeling
19. Work carried out or on behalf of others.
Throw-away Prototype
Decision Analysis
Data Model
Service
20. 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
Requirements Traceability
Deliverable
Relationship Map
21. 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.
Quality Assurance
Defect
Domain
Feature
22. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Relationship Map
State Diagram
Data Model
Secondary Actor
23. 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 Domain Model
Data Dictionary
User Acceptance Test
Implementation Subject Matter Expert (SME)
24. Any recognized association of people in the context of an organization or enterprise.
Enterprise
Customer
Organizational Unit
Requirements Management
25. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Horizontal Prototype
Business Need(s)
Business Analysis Approach
Temporal Event
26. A structured examination of an identified problem to understand the underlying causes.
Requirements Iteration
Business Architecture
Root Cause Analysis
Risk
27. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Brainstorming
User Requirements Document
Data Entity
Relationship Map
28. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Work Product
Event
Requirement
Incremental Delivery
29. 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
Black Box Tests
Data Dictionary
User Story
Requirements Package
30. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Process Map
Data Dictionary
Scope
31. The quality attributes design and implementation constraints and external interfaces that the product must have.
Constraint
Business Analysis
Non-functional Requirement(s)
Requirements Management
32. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Quality
Model(s)
Requirements Signoff
Design Constraints
33. A system of programming statements symbols and rules used to represent instructions to a computer.
Business Rule(s)
Code
Dialog Map
Product Backlog
34. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Baseline
Technique
Interoperability
Problem Statement
35. 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
Design Constraints
Change Control Board (CCB)
Opportunity Analysis
36. Metadata related to a requirement used to assist with requirements development and management.
Indicator
Request For Proposal (RFP)
Developer
Requirement(s) Attribute
37. An informal solicitation of proposals from vendors.
Requirement(s) Defect
Validated Requirements
End User
Request For Quote (RFQ)
38. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Span of Control
Requirements Package
Operative Rule(s)
Lessons Learned Process
39. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Requirement
SWOT Analysis
Organizational Readiness Assessment
Prototype
40. Software requirements that limit the options available to the system designer.
Regulator
Requirements Iteration
Span of Control
Design Constraints
41. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
Business Event
Organization Modeling
Scope Model
Requirements Workshop
42. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Subject Matter Expert (SME)
Decision Tree
Lessons Learned Process
Deliverable
43. An analysis model that illustrates the architecture of the system's user interface.
Deliverable
Assumption
Organizational Unit
Dialog Map
44. A model that defines the boundaries of a business domain or solution.
Scope Model
Quality Assurance
Defect
End User
45. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Event
Project Charter
Indicator
Cost Benefit Analysis
46. An analysis model showing the life cycle of a data entity or class.
Business Policy
Scenario
Impact Analysis
State Diagram
47. 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
Business Case
Relationship Map
Exploratory Prototype
Transition Requirement(s)
48. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.
Stated Requirements
Business Requirements Document
Stakeholder Requirement
Requirements Management Plan
49. 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
Business Requirement
Request For Proposal (RFP)
End User
Request For Information (RFI)
50. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Feasibility Study
Process Model
Decision Tree
Business Analysis Plan