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 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.
Iteration
Feature
Initiative
Actor(s)
2. A person with specific expertise in an area or domain under investigation.
Decomposition
Domain Subject Matter Expert (SME)
Stakeholder Analysis
System
3. All materials used by groups within an organization to define tailor implement and maintain their processes.
Requirements Validation
Knowledge Area
Data Entity
Organizational Process Asset
4. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Stakeholder
Desired Outcome
Project Charter
Enterprise Architecture
5. The features and functions that characterize a product service or result.
Product Scope
Request For Quote (RFQ)
Monitoring
Verification
6. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Product
Observation
Prioritization
Feasibility Study
7. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Event Response Table
Structural Rule
Sequence Diagram
Quality Attributes
8. The product capabilities or things the product must do for its users.
Functional Requirement(s)
Code
Product Backlog
Organizational Unit
9. The process of examining new business opportunities to improve organizational performance.
Dialog Map
Opportunity Analysis
Requirements Workshop
Decision Tree
10. A type of data model that depicts information groups as classes.
Deliverable
Sequence Diagram
Constraint
Class Model
11. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Return on Investment
Evaluation
Entity-Relationship Diagram
Product
12. 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.
Cost Benefit Analysis
Change-driven Methodology
Requirements Traceability
Organization Modeling
13. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Repository
Business Requirement
Desired Outcome
Quality Attributes
14. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Scope Model
Requirements Management
User Story
Horizontal Prototype
15. The work that must be performed to deliver a product service or result with the specified features and functions.
Project Scope
Business Architecture
Deliverable
Requirements Iteration
16. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Monitoring
Use Case
Data Model
User Requirements Document
17. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Business Analysis Communication Plan
Gap Analysis
Quality Attributes
Business Requirement
18. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Business Domain Model
Scope Model
Code
19. The area covered by a particular activity or topic of interest.
Scope
Decision Analysis
Stakeholder List
Deliverable
20. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Attribute
Request For Quote (RFQ)
Secondary Actor
Risk
21. A non-actionable directive that supports a business goal.
Requirements Risk Mitigation Strategy
Request For Proposal (RFP)
Iteration
Business Policy
22. 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.
Focus Group
Survey
Iteration
Interview
23. Information that is used to understand the context and validity of information recorded in a system.
Exploratory Prototype
Quality
Metadata
Validation
24. Limitations on the design of a solution that derive from the technology used in its implementation.
Entity-Relationship Diagram
Requirements Traceability
Fishbone Diagram
Technical Constraint(s)
25. A temporary endeavor undertaken to create a unique product service or result.
Process Model
Project
Requirements Management
Use Case
26. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Business Rule(s)
Stakeholder Requirement
Lessons Learned Process
Plan-driven Methodology
27. The set of capabilities a solution must deliver in order to meet the business need.
Interface
System
Observation
Solution Scope
28. 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.
Problem Statement
Walkthrough
Structural Rule
Validation
29. Software developed and sold for a particular market.
Commercial-off-the-Shelf Software (COTS)
Product Backlog
Brainstorming
Business Policy
30. The problem area undergoing analysis.
Secondary Actor
Domain
Relationship
Business Domain Model
31. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Non-functional Requirement(s)
Iteration
Requirements Validation
Force Field Analysis
32. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Domain
End User
Project Scope
Structured Walkthrough
33. 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.
Requirements Management Plan
Validation
Glossary
User Acceptance Test
34. 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.
Interview
Developer
Observation
End User
35. A data element with a specified data type that describes information associated with a concept or entity.
Fishbone Diagram
Attribute
Product Backlog
Non-functional Requirement(s)
36. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Process Model
Business Constraint(s)
Structural Rule
Gap Analysis
37. An assessment of the costs and benefits associated with a proposed initiative.
Requirements Management
Change-driven Methodology
Decision Tree
Business Case
38. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Requirements Trace Matrix
User Acceptance Test
Enterprise
Business Requirement
39. The degree to which a set of inherent characteristics fulfills requirements.
Operational Support
Quality
Class Model
Event
40. A stakeholder who uses products or services delivered by an organization.
Customer
Regulator
Requirements Risk Mitigation Strategy
Survey
41. 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.
Implementation Subject Matter Expert (SME)
Change-driven Methodology
Verification
Requirement
42. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Opportunity Analysis
Business Case
Peer Review
Regulator
43. 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.
Event Response Table
Business Goal
Business Analysis Plan
Event
44. A prototype that dives into the details of the interface functionality or both.
Brainstorming
Vertical Prototype
Fishbone Diagram
Structured Walkthrough
45. A solution or component of a solution that is the result of a project.
Validation
Stated Requirements
Technique
Product
46. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Business Analysis
Metric
User Story
Requirements Model
47. 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
Project Charter
Validated Requirements
Request For Proposal (RFP)
Interview
48. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Walkthrough
Requirements Allocation
Requirements Workshop
Constraint
49. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Object Oriented Modeling
Requirements Validation
Optionality
Relationship
50. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Baseline
Process Map
Evaluation
Service