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 recognized association of people in the context of an organization or enterprise.
Throw-away Prototype
Organizational Unit
Prioritization
Product
2. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Elicitation
Risk
Request For Information (RFI)
Requirements Package
3. 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
Product Scope
Business Architecture
Impact Analysis
Requirements Management Plan
4. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Quality Assurance
Evaluation
Exploratory Prototype
Requirement
5. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Requirement(s) Defect
Activity
Verified Requirements
Change Control Board (CCB)
6. 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
Deliverable
Requirement
Request For Information (RFI)
Fishbone Diagram
7. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Process Model
Requirement(s) Defect
Timebox
Request For Proposal (RFP)
8. 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.
Event Response Table
Software/Systems Requirements Specification
Change Control Board (CCB)
Validation
9. A system of programming statements symbols and rules used to represent instructions to a computer.
Code
Sequence Diagram
Business Event
Implementation Subject Matter Expert (SME)
10. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Root Cause Analysis
Requirements Management Tool
Gap Analysis
Desired Outcome
11. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Stated Requirements
Unified Modeling Language (UML)
Decomposition
Requirements Management Tool
12. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Business Event
Technical Constraint(s)
Capability
Activity Diagram
13. A shared boundary between any two persons and/or systems through which information is communicated.
Interface
Initiative
Scenario
Technical Constraint(s)
14. 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.
Stakeholder Analysis
Business Analysis
Included Use Cases
Checklist
15. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Sponsor
Competitive Analysis
Domain Subject Matter Expert (SME)
Exploratory Prototype
16. A system trigger that is initiated by time.
Project Scope
Business Analysis Plan
Class
Temporal Event
17. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Fishbone Diagram
Software/Systems Requirements Specification
Elicitation
Span of Control
18. 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).
Stated Requirements
Cardinality
Incremental Delivery
Capability
19. 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.
Analyst
Developer
Business Case
Data Dictionary
20. An analysis model showing the life cycle of a data entity or class.
Organizational Process Asset
Stakeholder
State Diagram
Iteration
21. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.
Evolutionary Prototype
User
Business Architecture
Use Case
22. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Swimlane
Glossary
Project
Metric
23. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Benchmarking
Business Event
Work Breakdown Structure (WBS)
Unified Modeling Language (UML)
24. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
Project
Initiative
Entity-Relationship Diagram
25. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Dialog Map
Baseline
Interview
Process Model
26. 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
Sequence Diagram
Class
Business Requirement
Event
27. A description of the requirements management process.
Monitoring
Requirements Management Plan
Methodology
Elicitation
28. A stakeholder who uses products or services delivered by an organization.
Project Scope
Customer
Requirements Allocation
Object Oriented Modeling
29. 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.
Temporal Event
Swimlane
Plan-driven Methodology
Defect
30. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Project
Glossary
Capability
Checklist
31. The work that must be performed to deliver a product service or result with the specified features and functions.
Project Scope
Tester
Secondary Actor
Unified Modeling Language (UML)
32. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Event Response Table
Structural Rule
Vertical Prototype
33. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Prototype
Secondary Actor
Stakeholder
34. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Document Analysis
Data Dictionary
Prioritization
Sequence Diagram
35. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
Model(s)
Decision Tables
Customer
Iteration
36. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Validated Requirements
Model(s)
Product Backlog
Repository
37. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Validation
Force Field Analysis
Interface
External Interfaces
38. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
Business Architecture
User Requirements Document
Operational Support
Decomposition
39. A prototype that dives into the details of the interface functionality or both.
Risk
User Requirements Document
Incremental Delivery
Vertical Prototype
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
Initiative
Peer Review
Project Charter
User Story
41. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Structured Walkthrough
Requirement(s) Attribute
Change Control Board (CCB)
End User
42. 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
Fishbone Diagram
Horizontal Prototype
Quality Attributes
43. 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.
Glossary
Fishbone Diagram
Decomposition
Feasibility Study
44. An actor who participates in but does not initiate a use case.
Desired Outcome
Assumption
Opportunity Analysis
Secondary Actor
45. Ability of systems to communicate by exchanging data or services.
State Diagram
Brainstorming
Requirements Management
Interoperability
46. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Work Breakdown Structure (WBS)
Attribute
Incremental Delivery
Solution Requirement
47. A non-actionable directive that supports a business goal.
Data Model
Interoperability
User Requirements Document
Business Policy
48. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Black Box Tests
Business Goal
Interview
Requirements Traceability
49. The human and nonhuman roles that interact with the system.
Organizational Unit
Actor(s)
Incremental Delivery
Timebox
50. 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
Risk
Business Analyst
User Requirements Document