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. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Quality Attributes
Structural Rule
Product Backlog
Requirement
2. The product capabilities or things the product must do for its users.
Evaluation
User Acceptance Test
Functional Requirement(s)
Work Product
3. A prototype that dives into the details of the interface functionality or both.
Code
Repository
Vertical Prototype
Temporal Event
4. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Stakeholder
Swimlane
User
Focus Group
5. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Fishbone Diagram
Cardinality
Sequence Diagram
Organizational Process Asset
6. The features and functions that characterize a product service or result.
Business Goal
Requirements Traceability
Product Scope
Glossary
7. Ability of systems to communicate by exchanging data or services.
Work Product
Interoperability
Business Analysis Communication Plan
Requirements Allocation
8. An analysis model that shows user interface dialogs arranged as hierarchies.
Decision Analysis
Dialog Hierarchy
Business Analyst
Solution Scope
9. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Evaluation
Objective
Requirements Management
Inspection
10. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Data Model
Observation
External Interfaces
11. A model that defines the boundaries of a business domain or solution.
Deliverable
Scope Model
Structured Walkthrough
Validated Requirements
12. 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.
Iteration
Feasibility Study
Tester
Requirements Allocation
13. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
System
Indicator
Use Case Diagram
User Requirements Document
14. An assessment of the costs and benefits associated with a proposed initiative.
Business Case
Document Analysis
Benchmarking
Business Policy
15. A non-actionable directive that supports a business goal.
Prioritization
Requirements Traceability
Business Policy
Focus Group
16. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Business Analyst
Organizational Process Asset
User
Indicator
17. A system trigger that is initiated by humans.
Temporal Event
Requirement(s) Defect
Business Event
Customer
18. 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
Technical Constraint(s)
Business Process
Subject Matter Expert (SME)
Stakeholder Requirement
19. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Technique
Decomposition
Association
Requirement
20. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Lessons Learned Process
Requirements Verification
Request For Information (RFI)
Scenario
21. A link between two elements or objects in a diagram.
Quality Attributes
Requirements Signoff
Association
Request For Proposal (RFP)
22. An informal solicitation of proposals from vendors.
Domain Subject Matter Expert (SME)
Problem Statement
Request For Quote (RFQ)
Impact Analysis
23. A unit of work performed as part of an initiative or process.
Activity
Observation
Organizational Readiness Assessment
Defect
24. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Business Need(s)
Organizational Unit
Business Analysis Plan
25. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
System
Business Analyst
Model(s)
Opportunity Analysis
26. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Requirements Trace Matrix
Quality Assurance
Requirement
Variance Analysis
27. The set of capabilities a solution must deliver in order to meet the business need.
Solution Scope
Gap Analysis
Impact Analysis
Checklist
28. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti
Inspection
Class
Business Need(s)
Domain Subject Matter Expert (SME)
29. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Data Model
Change-driven Methodology
Repository
30. A temporary endeavor undertaken to create a unique product service or result.
Business Requirement
Project
Structural Rule
Swimlane
31. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Stakeholder List
Requirements Management Tool
Functional Requirement(s)
Activity Diagram
32. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Cost Benefit Analysis
Requirement(s) Defect
Event Response Table
Risk
33. 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
Business Constraint(s)
Business Process
Process Map
Iteration
34. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Dialog Map
Validated Requirements
Class
35. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Operational Support
Work Breakdown Structure (WBS)
Glossary
User Acceptance Test
36. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Knowledge Area
Design Constraints
Sponsor
Data Entity
37. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Use Case Diagram
Assumption
Structured Walkthrough
End User
38. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Developer
Business Analyst
Walkthrough
Decision Tree
39. 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.
Horizontal Prototype
Data Flow Diagram (DFD)
Checklist
Metric
40. 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
Temporal Event
Requirement(s) Defect
User Story
Peer Review
41. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Evolutionary Prototype
Requirement(s) Attribute
External Interfaces
Model(s)
42. 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.
Incremental Delivery
Interview
Requirement(s) Attribute
Stakeholder List
43. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Black Box Tests
Prioritization
Entity-Relationship Diagram
Business Process
44. Limitations on the design of a solution that derive from the technology used in its implementation.
Stakeholder List
Enterprise Architecture
Technical Constraint(s)
Requirements Trace Matrix
45. 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.
Business Case
Context Diagram
Stakeholder Requirement
Business Analysis
46. The process of examining new business opportunities to improve organizational performance.
Data Model
Sequence Diagram
Business Analysis Plan
Opportunity Analysis
47. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Baseline
Organizational Process Asset
Desired Outcome
Scenario
48. 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.
Attribute
Commercial-off-the-Shelf Software (COTS)
Process Model
Requirements Workshop
49. Creating working software in multiple releases so the entire product is delivered in portions over time.
Verification
User Story
Incremental Delivery
Deliverable
50. An actor who participates in but does not initiate a use case.
Quality
Service
Secondary Actor
Data Flow Diagram (DFD)