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 team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Decision Tree
Lessons Learned Process
Brainstorming
Request For Information (RFI)
2. 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.
Constraint
Unified Modeling Language (UML)
Regulator
End User
3. 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
Verified Requirements
Data Entity
Focus Group
4. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Knowledge Area
External Interfaces
Requirements Management Plan
Desired Outcome
5. The quality attributes design and implementation constraints and external interfaces that the product must have.
Risk
Defect
Non-functional Requirement(s)
Commercial-off-the-Shelf Software (COTS)
6. 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.
Activity
Event
Requirement
Root Cause Analysis
7. The features and functions that characterize a product service or result.
Object Oriented Modeling
Request For Proposal (RFP)
Product Scope
Requirement
8. 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.
Dialog Map
Vision Statement (product vision statement)
Requirements Management Tool
Interview
9. Any effort undertaken with a defined goal or objective.
Product Scope
Organizational Readiness Assessment
Business Goal
Initiative
10. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Regulator
Iteration
Methodology
11. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Stakeholder List
Requirements Workshop
Optionality
Evaluation
12. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Work Product
Horizontal Prototype
Relationship Map
Sequence Diagram
13. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Plan-driven Methodology
Requirements Trace Matrix
Product
Code
14. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Domain
Product Backlog
Data Dictionary
15. 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
Business Architecture
Enterprise Architecture
Object Oriented Modeling
Solution Scope
16. A prototype that dives into the details of the interface functionality or both.
Sponsor
Vertical Prototype
Business Domain Model
Context Diagram
17. 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.
Feasibility Study
Entity-Relationship Diagram
Requirements Workshop
System
18. 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.
Event
Verified Requirements
Activity Diagram
Incremental Delivery
19. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Dialog Hierarchy
Validated Requirements
Feature
Process Map
20. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
End User
Peer Review
Timebox
Subject Matter Expert (SME)
21. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Operative Rule(s)
Developer
Focus Group
22. 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 Architecture
Organizational Readiness Assessment
Interview
Operational Support
23. 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.
Requirement(s) Defect
Observation
Implementation Subject Matter Expert (SME)
Elicitation
24. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.
Sponsor
Stated Requirements
Business Process
Scenario
25. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Change Control Board (CCB)
Capability
Cardinality
Requirements Management
26. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Dialog Map
Product Scope
Solution Scope
Data Model
27. A function of an organization that enables it to achieve a business goal or objective.
Verified Requirements
Scope
Risk
Capability
28. 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.
Metadata
Focus Group
Stated Requirements
Black Box Tests
29. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Quality
Focus Group
Constraint
Monitoring
30. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Requirement(s) Defect
Competitive Analysis
Data Flow Diagram (DFD)
Impact Analysis
31. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Variance Analysis
User Story
Use Case
Requirements Package
32. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Impact Analysis
Requirement
Requirements Management
33. A link between two elements or objects in a diagram.
Association
Survey
Change-driven Methodology
System
34. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Business Architecture
Stated Requirements
Business Domain Model
Change Control Board (CCB)
35. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Business Analysis Communication Plan
Relationship Map
Assumption
Verified Requirements
36. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Organization Modeling
Business Process
Business Analysis
Included Use Cases
37. The process of examining new business opportunities to improve organizational performance.
SWOT Analysis
Business Analysis
Opportunity Analysis
Exploratory Prototype
38. A prototype developed to explore or verify requirements.
Structural Rule
Project Manager
Exploratory Prototype
Validation
39. 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.
Data Model
Business Constraint(s)
Evaluation
Domain Subject Matter Expert (SME)
40. The problem area undergoing analysis.
Knowledge Area
Unified Modeling Language (UML)
Domain
Enterprise Architecture
41. 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.
Prioritization
Benchmarking
Metric
Context Diagram
42. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Risk Mitigation Strategy
Scope Model
Activity
Requirements Signoff
43. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Lessons Learned Process
Event Response Table
Change-driven Methodology
Data Entity
44. A prototype that is continuously modified and updated in response to feedback from users.
Sponsor
Business Policy
Feature
Evolutionary Prototype
45. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Organizational Process Asset
Subject Matter Expert (SME)
Unified Modeling Language (UML)
Feasibility Study
46. The area covered by a particular activity or topic of interest.
Analyst
Scope
State Diagram
Enterprise
47. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Business Rule(s)
Deliverable
Request For Quote (RFQ)
48. 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.
Assumption
Document Analysis
User Acceptance Test
Focus Group
49. An informal solicitation of proposals from vendors.
Feasibility Study
Business Domain Model
Request For Quote (RFQ)
Stakeholder
50. 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.
Enterprise
Stakeholder
Association
Feature