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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Software/Systems Requirements Specification
Iteration
Requirements Allocation
External Interfaces
2. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Scope Model
Enterprise Architecture
Monitoring
User Acceptance Test
3. A person with specific expertise in an area or domain under investigation.
Incremental Delivery
Domain Subject Matter Expert (SME)
Variance Analysis
Constraint
4. Creating working software in multiple releases so the entire product is delivered in portions over time.
Class Model
Incremental Delivery
Business Event
Transition Requirement(s)
5. 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.
Tester
Horizontal Prototype
Requirements Risk Mitigation Strategy
Interface
6. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Focus Group
Data Dictionary
Indicator
Requirements Verification
7. A stakeholder person device or system that directly or indirectly accesses a system.
Organization
Implementation Subject Matter Expert (SME)
User
Benchmarking
8. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Metric
Assumption
Interview
Opportunity Analysis
9. Formal approval of a set of requirements by a sponsor or other decision maker.
Structural Rule
Entity-Relationship Diagram
Knowledge Area
Requirements Signoff
10. A stakeholder who uses products or services delivered by an organization.
Developer
Relationship Map
Operational Support
Customer
11. 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
Prioritization
Service
Class Model
Business Process
12. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Business Need(s)
Requirements Package
Incremental Delivery
Cardinality
13. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Requirement
Prioritization
User Story
Structural Rule
14. The set of capabilities a solution must deliver in order to meet the business need.
Use Case Diagram
Verified Requirements
Analyst
Solution Scope
15. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Attribute
State Diagram
Document Analysis
External Interfaces
16. The degree to which a set of inherent characteristics fulfills requirements.
Business Analysis Plan
Product Scope
Business Analysis Communication Plan
Quality
17. The human and nonhuman roles that interact with the system.
Validated Requirements
Event Response Table
Actor(s)
Stakeholder Requirement
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
Inspection
Entity-Relationship Diagram
Business Architecture
Product Backlog
19. The product capabilities or things the product must do for its users.
Attribute
Functional Requirement(s)
Cost Benefit Analysis
Feature
20. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Attribute
Business Need(s)
Assumption
Business Requirements Document
21. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Validation
Organization Modeling
Monitoring
Data Model
22. A use case composed of a common set of steps used by multiple use cases.
Requirement
Actor(s)
Included Use Cases
Throw-away Prototype
23. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Competitive Analysis
Cost Benefit Analysis
Deliverable
Analyst
24. A description of the requirements management process.
Requirements Management Plan
Evolutionary Prototype
Model(s)
Organizational Process Asset
25. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Request For Information (RFI)
Subject Matter Expert (SME)
System
Deliverable
26. 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.
Class Model
Project Charter
User Acceptance Test
Repository
27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Requirements Package
Risk
Domain Subject Matter Expert (SME)
Project Manager
28. A group of related tasks that support a key function of business analysis.
Organizational Process Asset
Product Scope
Vision Statement (product vision statement)
Knowledge Area
29. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Organizational Readiness Assessment
Data Entity
Feasibility Study
Span of Control
30. 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.
Fishbone Diagram
Monitoring
Iteration
Implementation Subject Matter Expert (SME)
31. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Business Analyst
Organization
Decision Analysis
Enterprise
32. 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.
Requirements Traceability
Iteration
Brainstorming
Activity Diagram
33. 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.
User
Organization Modeling
Feature
Attribute
34. An analysis model that illustrates the architecture of the system's user interface.
Project
Data Dictionary
Requirements Workshop
Dialog Map
35. An assessment of the costs and benefits associated with a proposed initiative.
Subject Matter Expert (SME)
Operational Support
Use Case
Business Case
36. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Customer
Class Model
Project
Variance Analysis
37. A prototype developed to explore or verify requirements.
Decision Analysis
Exploratory Prototype
Change-driven Methodology
Problem Statement
38. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Operational Support
Return on Investment
Technique
Requirements Traceability
39. 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
Solution Scope
Horizontal Prototype
End User
Requirements Iteration
40. A fixed period of time to accomplish a desired outcome.
Risk
Requirements Validation
Timebox
Operative Rule(s)
41. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Change-driven Methodology
Business Policy
Black Box Tests
Structured Walkthrough
42. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
Assumption
Temporal Event
Cost Benefit Analysis
43. A solution or component of a solution that is the result of a project.
Relationship Map
Product
Sequence Diagram
Peer Review
44. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Business Requirements Document
Methodology
Requirements Traceability
Assumption
45. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Observation
Initiative
Unified Modeling Language (UML)
46. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Opportunity Analysis
Requirement(s) Defect
Data Flow Diagram (DFD)
Gap Analysis
47. 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 Traceability
Requirement
Context Diagram
Unified Modeling Language (UML)
48. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Scope
Root Cause Analysis
Evaluation
Change Control Board (CCB)
49. 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.
Throw-away Prototype
Structured Walkthrough
Root Cause Analysis
Cost Benefit Analysis
50. A link between two elements or objects in a diagram.
Stakeholder List
Initiative
Association
Interview