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 validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Requirements Management Plan
System
Operational Support
Peer Review
2. A state or condition the business must satisfy to reach its vision.
Exploratory Prototype
Domain
Decision Analysis
Business Goal
3. A measure of the profitability of a project or investment.
Vision Statement (product vision statement)
Business Policy
Return on Investment
Design Constraints
4. Any unique and verifiable work product or service that a party has agreed to deliver.
Commercial-off-the-Shelf Software (COTS)
Deliverable
Gap Analysis
Quality Attributes
5. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Process Map
Metric
Design Constraints
Domain Subject Matter Expert (SME)
6. Ability of systems to communicate by exchanging data or services.
Commercial-off-the-Shelf Software (COTS)
User Requirements Document
Repository
Interoperability
7. 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
Business Process
Association
Business Constraint(s)
Verification
8. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Organization
Optionality
Validation
Business Architecture
9. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Requirements Iteration
Scenario
Fishbone Diagram
Iteration
10. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Optionality
Indicator
Business Analyst
Survey
11. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Document Analysis
Developer
Methodology
Inspection
12. An analysis model describing the data structures and attributes needed by the system.
Exploratory Prototype
Regulator
Requirements Management Plan
Data Dictionary
13. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Desired Outcome
Structured Walkthrough
Process Map
Class Model
14. 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.
Competitive Analysis
Requirements Model
Verified Requirements
Business Process
15. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Service
User Story
SWOT Analysis
Metric
16. An analysis model that shows user interface dialogs arranged as hierarchies.
Validated Requirements
Gap Analysis
Dialog Hierarchy
Stated Requirements
17. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Feature
Tester
Cardinality
18. 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.
Knowledge Area
Survey
End User
Requirement(s) Defect
19. A system trigger that is initiated by humans.
Plan-driven Methodology
Business Event
Requirements Management Plan
Enterprise
20. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Unified Modeling Language (UML)
Interview
Verification
Stated Requirements
21. A solution or component of a solution that is the result of a project.
Product
End User
Process Model
Fishbone Diagram
22. A stakeholder who uses products or services delivered by an organization.
Unified Modeling Language (UML)
Customer
Analyst
Business Rule(s)
23. Work carried out or on behalf of others.
User
Project Scope
Feature
Service
24. The set of capabilities a solution must deliver in order to meet the business need.
Business Goal
Walkthrough
Solution Scope
Initiative
25. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Customer
Problem Statement
Impact Analysis
Transition Requirement(s)
26. 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.
Verification
Monitoring
Request For Information (RFI)
Request For Proposal (RFP)
27. 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.
Developer
End User
Requirements Trace Matrix
Benchmarking
28. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Monitoring
User Requirements Document
Business Analysis Plan
Impact Analysis
29. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Scenario
Stated Requirements
Throw-away Prototype
Technique
30. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Data Model
Technical Constraint(s)
Feasibility Study
31. 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.
Analyst
Requirements Iteration
Validation
Requirement
32. 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.
Verified Requirements
Work Breakdown Structure (WBS)
Sponsor
Process Map
33. 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.
Business Domain Model
Focus Group
Checklist
Requirements Signoff
34. The human and nonhuman roles that interact with the system.
Actor(s)
Business Rule(s)
Assumption
Cardinality
35. 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.
Requirement(s) Defect
Design Constraints
Enterprise
Requirements Verification
36. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Interface
Business Analysis Communication Plan
Requirements Model
Requirements Package
37. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Lessons Learned Process
Project Scope
Prioritization
38. Formal approval of a set of requirements by a sponsor or other decision maker.
Stakeholder List
Plan-driven Methodology
Requirements Signoff
Enterprise
39. An informal solicitation of proposals from vendors.
Data Model
Request For Quote (RFQ)
Domain
Inspection
40. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Developer
Structural Rule
Horizontal Prototype
Sponsor
41. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Entity-Relationship Diagram
Process Model
Structured Walkthrough
Service
42. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Quality Assurance
Constraint
Gap Analysis
Deliverable
43. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Domain Subject Matter Expert (SME)
Activity Diagram
Attribute
Structured Walkthrough
44. A link between two elements or objects in a diagram.
Association
Secondary Actor
Business Constraint(s)
Problem Statement
45. An analysis model showing the life cycle of a data entity or class.
Organization Modeling
Desired Outcome
State Diagram
Data Dictionary
46. 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
Data Flow Diagram (DFD)
Business Policy
Structural Rule
Stakeholder Requirement
47. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Model(s)
Document Analysis
Work Breakdown Structure (WBS)
Subject Matter Expert (SME)
48. A fixed period of time to accomplish a desired outcome.
Throw-away Prototype
Knowledge Area
Timebox
Interface
49. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a
Force Field Analysis
Requirements Package
Object Oriented Modeling
Analyst
50. 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
Data Flow Diagram (DFD)
Class
Assumption
Event