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. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Capability
Request For Proposal (RFP)
End User
2. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Document Analysis
Business Constraint(s)
System
Requirements Trace Matrix
3. 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.
Decision Analysis
Structural Rule
Requirement(s) Attribute
Activity Diagram
4. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Project Scope
Indicator
Walkthrough
Project Manager
5. A use case composed of a common set of steps used by multiple use cases.
Analyst
Supplier
Included Use Cases
Object Oriented Modeling
6. A data element with a specified data type that describes information associated with a concept or entity.
Brainstorming
Attribute
Interoperability
Quality Attributes
7. 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 Plan
Functional Requirement(s)
Verification
Requirements Model
8. 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
Decomposition
Design Constraints
Business Constraint(s)
Iteration
9. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Regulator
Lessons Learned Process
Requirements Management Plan
Project Charter
10. A unit of work performed as part of an initiative or process.
Requirements Management
Activity
Survey
Event
11. All materials used by groups within an organization to define tailor implement and maintain their processes.
Incremental Delivery
Sequence Diagram
Organizational Process Asset
Requirements Risk Mitigation Strategy
12. The area covered by a particular activity or topic of interest.
Operative Rule(s)
Lessons Learned Process
Scope
Requirement(s) Attribute
13. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Monitoring
Sequence Diagram
Feature
Defect
14. 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.
Requirements Management
Verification
Organization Modeling
Activity
15. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Swimlane
Requirements Risk Mitigation Strategy
Decision Analysis
Knowledge Area
16. 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.
Desired Outcome
Work Breakdown Structure (WBS)
Verified Requirements
Sequence Diagram
17. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Horizontal Prototype
User
Repository
Customer
18. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Inspection
SWOT Analysis
Variance Analysis
Vertical Prototype
19. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Business Event
Functional Requirement(s)
Competitive Analysis
20. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Variance Analysis
Defect
Model(s)
Assumption
21. 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.
Organization
Project Scope
Service
Competitive Analysis
22. 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.
Gap Analysis
Change-driven Methodology
Request For Information (RFI)
Technical Constraint(s)
23. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Class
Enterprise Architecture
Glossary
Requirements Management
24. A group or person who has interests that may be affected by an initiative or influence over it.
Object Oriented Modeling
Developer
Stakeholder
Business Process
25. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Quality
Optionality
Decision Analysis
Data Entity
26. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Product Scope
Structured Walkthrough
Relationship
Domain Subject Matter Expert (SME)
27. A fixed period of time to accomplish a desired outcome.
Methodology
Timebox
Business Process
Operative Rule(s)
28. 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.
Activity Diagram
State Diagram
Decision Analysis
Domain
29. 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.
Repository
Metadata
Model(s)
Feature
30. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Return on Investment
Business Analysis
Black Box Tests
Stakeholder List
31. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Class
Initiative
Requirement
Process Model
32. A partial or preliminary version of the system.
Relationship Map
Prototype
Secondary Actor
Implementation Subject Matter Expert (SME)
33. A prototype that dives into the details of the interface functionality or both.
Project Manager
Vertical Prototype
Monitoring
Requirement(s) Defect
34. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Monitoring
Objective
Walkthrough
Unified Modeling Language (UML)
35. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Scenario
Commercial-off-the-Shelf Software (COTS)
Actor(s)
Business Requirement
36. An informal solicitation of proposals from vendors.
Request For Quote (RFQ)
Project
Organizational Readiness Assessment
Data Model
37. 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.
Process Map
Data Entity
User Acceptance Test
Checklist
38. 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.
Business Analysis
Metadata
Competitive Analysis
Structured Walkthrough
39. Metadata related to a requirement used to assist with requirements development and management.
Object Oriented Modeling
Dialog Hierarchy
Inspection
Requirement(s) Attribute
40. The problem area undergoing analysis.
Product Scope
Transition Requirement(s)
Domain
Relationship Map
41. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Quality Assurance
Stakeholder
Business Process
42. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Product
Business Process
SWOT Analysis
Analyst
43. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Prioritization
Dialog Map
Business Policy
Solution Requirement
44. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Vision Statement (product vision statement)
Code
Quality Attributes
Tester
45. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Iteration
Stakeholder Analysis
Data Flow Diagram (DFD)
Organization Modeling
46. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Domain
Prototype
Requirements Validation
Business Goal
47. 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
Temporal Event
Included Use Cases
Functional Requirement(s)
Stakeholder Requirement
48. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Business Process
Organization
Domain Subject Matter Expert (SME)
49. An assessment of the costs and benefits associated with a proposed initiative.
Variance Analysis
Requirements Allocation
Business Case
Product Backlog
50. 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.
System
Project Charter
Brainstorming
Vertical Prototype