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. 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.
Model(s)
Dialog Hierarchy
Plan-driven Methodology
Requirements Signoff
2. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Knowledge Area
Enterprise Architecture
Requirements Management Plan
Change-driven Methodology
3. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Validation
Functional Requirement(s)
Exploratory Prototype
Survey
4. 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
Product Backlog
Business Constraint(s)
Glossary
Design Constraints
5. A non-actionable directive that supports a business goal.
Business Policy
Class Model
Project Manager
Methodology
6. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Requirements Traceability
Model(s)
End User
Organizational Readiness Assessment
7. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Entity-Relationship Diagram
Checklist
Lessons Learned Process
Solution
8. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Quality Attributes
Verification
Document Analysis
Iteration
9. Any effort undertaken with a defined goal or objective.
Business Requirements Document
Sponsor
Initiative
Class Model
10. 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.
Operative Rule(s)
Requirement(s) Defect
Walkthrough
Organizational Process Asset
11. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.
Relationship Map
Defect
Interface
Verified Requirements
12. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Interview
Gap Analysis
Project Scope
Vertical Prototype
13. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Requirements Iteration
Verified Requirements
Software/Systems Requirements Specification
14. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Requirement(s) Defect
Temporal Event
Decision Analysis
15. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Glossary
Observation
Lessons Learned Process
16. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Brainstorming
State Diagram
Impact Analysis
Exploratory Prototype
17. Metadata related to a requirement used to assist with requirements development and management.
Software/Systems Requirements Specification
Exploratory Prototype
Requirements Workshop
Requirement(s) Attribute
18. 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.
Business Domain Model
Service
Evaluation
Domain Subject Matter Expert (SME)
19. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Structured Walkthrough
Event
Service
Indicator
20. 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.
Enterprise
User Requirements Document
Solution Requirement
Implementation Subject Matter Expert (SME)
21. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Change Control Board (CCB)
Glossary
Use Case Diagram
Document Analysis
22. The quality attributes design and implementation constraints and external interfaces that the product must have.
Interview
Quality Assurance
Non-functional Requirement(s)
Requirements Management
23. 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
Work Breakdown Structure (WBS)
Impact Analysis
Swimlane
Stakeholder Requirement
24. 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.
Deliverable
Enterprise
Actor(s)
Optionality
25. The number of employees a manger is directly (or indirectly) responsible for.
Organization
Span of Control
Organizational Process Asset
Commercial-off-the-Shelf Software (COTS)
26. 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.
Business Policy
Gap Analysis
Temporal Event
Interview
27. The features and functions that characterize a product service or result.
Exploratory Prototype
Business Analysis
Business Domain Model
Product Scope
28. A description of the requirements management process.
Metric
Requirements Management Plan
Data Model
Monitoring
29. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Requirements Validation
System
Fishbone Diagram
Project Manager
30. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Cardinality
Capability
Activity
Force Field Analysis
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.
Data Model
Requirements Traceability
Event
Decision Analysis
32. A model that defines the boundaries of a business domain or solution.
Constraint
Scope Model
Observation
Data Entity
33. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Monitoring
Regulator
Root Cause Analysis
Process Model
34. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Class
Assumption
User Story
Problem Statement
35. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Indicator
Objective
Sponsor
Scope
36. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Scope
Requirements Risk Mitigation Strategy
Requirement(s) Defect
Relationship
37. Creating working software in multiple releases so the entire product is delivered in portions over time.
Project
Feasibility Study
Deliverable
Incremental Delivery
38. A stakeholder who uses products or services delivered by an organization.
Customer
Monitoring
Developer
Document Analysis
39. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Project Scope
Scope Model
Product
Requirements Allocation
40. 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 Event
Business Process
Glossary
Verified Requirements
41. A system trigger that is initiated by time.
Verified Requirements
Temporal Event
Verification
Organization
42. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Root Cause Analysis
Desired Outcome
Horizontal Prototype
Validated Requirements
43. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Project Manager
Business Analysis Plan
Requirements Model
Vision Statement (product vision statement)
44. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Stakeholder Requirement
Entity-Relationship Diagram
Decomposition
Plan-driven Methodology
45. Ability of systems to communicate by exchanging data or services.
Interoperability
Swimlane
End User
Data Model
46. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Project
External Interfaces
Technique
Requirements Management Tool
47. 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.
Metric
Competitive Analysis
Opportunity Analysis
Verification
48. A type of data model that depicts information groups as classes.
Business Analysis Communication Plan
Class Model
Structural Rule
Business Case
49. A link between two elements or objects in a diagram.
Business Constraint(s)
Interface
Association
Supplier
50. 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 Rule(s)
Validation
Project Charter
Business Architecture