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 system of programming statements symbols and rules used to represent instructions to a computer.
Code
Opportunity Analysis
Business Analysis
Monitoring
2. 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
Activity Diagram
Gap Analysis
Feasibility Study
Business Architecture
3. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Business Requirement
Organization Modeling
Requirements Management
Requirements Iteration
4. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Walkthrough
Process Model
Business Rule(s)
Metric
5. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Organizational Unit
Optionality
Change Control Board (CCB)
6. 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
Vision Statement (product vision statement)
Return on Investment
Requirements Management
7. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Product
Validation
Transition Requirement(s)
Scope
8. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Business Analysis Communication Plan
Lessons Learned Process
Peer Review
Request For Information (RFI)
9. 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.
Interface
Commercial-off-the-Shelf Software (COTS)
User Acceptance Test
Evaluation
10. Work carried out or on behalf of others.
Throw-away Prototype
Service
User Requirements Document
Actor(s)
11. A stakeholder person device or system that directly or indirectly accesses a system.
User
Request For Quote (RFQ)
Focus Group
Stakeholder
12. A prototype that dives into the details of the interface functionality or both.
Defect
Vertical Prototype
Project Manager
Benchmarking
13. An analysis model that illustrates the architecture of the system's user interface.
Actor(s)
Dialog Map
Business Goal
Document Analysis
14. 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.
Request For Proposal (RFP)
Relationship
Functional Requirement(s)
Enterprise
15. A structured examination of an identified problem to understand the underlying causes.
Business Goal
Requirements Workshop
Event
Root Cause Analysis
16. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Stakeholder Requirement
Decomposition
Business Goal
Repository
17. The product capabilities or things the product must do for its users.
Functional Requirement(s)
Sponsor
Actor(s)
Glossary
18. 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
Relationship Map
Scope
Walkthrough
19. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Swimlane
Relationship Map
Decision Analysis
Quality Assurance
20. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Business Need(s)
Requirement(s) Defect
Analyst
Data Flow Diagram (DFD)
21. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Vision Statement (product vision statement)
Use Case
Product Scope
Requirements Management Tool
22. 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.
Optionality
Product Scope
Actor(s)
Verification
23. 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
Unified Modeling Language (UML)
User Story
Requirements Allocation
Regulator
24. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Exploratory Prototype
System
Structured Walkthrough
Process Map
25. 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.
Interoperability
Organizational Unit
Monitoring
Feature
26. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Inspection
SWOT Analysis
Domain Subject Matter Expert (SME)
Business Requirements Document
27. 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.
Requirements Validation
Business Analysis Communication Plan
Supplier
Walkthrough
28. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Process Model
Temporal Event
Stakeholder Analysis
Cost Benefit Analysis
29. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Cardinality
Defect
Temporal Event
Data Entity
30. The set of capabilities a solution must deliver in order to meet the business need.
Black Box Tests
Variance Analysis
Focus Group
Solution Scope
31. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Focus Group
Force Field Analysis
Deliverable
Feasibility Study
32. A stakeholder who provides products or services to an organization.
Business Process
Product Backlog
Supplier
Glossary
33. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Stakeholder Requirement
Document Analysis
Activity Diagram
Software/Systems Requirements Specification
34. 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
Business Requirement
Product
Dialog Map
Request For Information (RFI)
35. 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.
Activity Diagram
Dialog Map
Process Map
Feasibility Study
36. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Organization Modeling
Product Backlog
Throw-away Prototype
Data Entity
37. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Benchmarking
Unified Modeling Language (UML)
Defect
Requirements Workshop
38. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Software/Systems Requirements Specification
Project Scope
Baseline
39. The work that must be performed to deliver a product service or result with the specified features and functions.
Deliverable
Use Case
Requirements Workshop
Project Scope
40. An analysis model describing the data structures and attributes needed by the system.
Timebox
Plan-driven Methodology
Monitoring
Data Dictionary
41. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Stakeholder Requirement
Vision Statement (product vision statement)
Product Backlog
Requirements Allocation
42. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Class Model
Project Charter
Business Analysis Plan
43. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Checklist
Peer Review
Work Breakdown Structure (WBS)
44. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Process Model
Business Case
Data Model
Business Requirement
45. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Flow Diagram (DFD)
Relationship Map
Business Requirements Document
Structural Rule
46. 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.
Request For Quote (RFQ)
Checklist
Cost Benefit Analysis
Project
47. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Stakeholder Requirement
Requirement
Class
Brainstorming
48. A temporary endeavor undertaken to create a unique product service or result.
Decision Tables
Project
Prioritization
Use Case Diagram
49. 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.
Request For Proposal (RFP)
Throw-away Prototype
Product
Methodology
50. 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.
Vertical Prototype
Defect
Implementation Subject Matter Expert (SME)
Relationship