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 data element with a specified data type that describes information associated with a concept or entity.
Plan-driven Methodology
Attribute
Class Model
Model(s)
2. 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.
Temporal Event
Verification
Enterprise Architecture
Exploratory Prototype
3. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Activity
Constraint
Quality Assurance
Business Process
4. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Secondary Actor
Object Oriented Modeling
Requirements Model
Activity
5. 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.
Stated Requirements
Request For Proposal (RFP)
Requirements Traceability
Organizational Readiness Assessment
6. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Requirements Validation
Transition Requirement(s)
Variance Analysis
Solution Scope
7. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Data Entity
Business Architecture
Requirement(s) Defect
8. 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.
Monitoring
Work Breakdown Structure (WBS)
Transition Requirement(s)
Verification
9. 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.
Competitive Analysis
Constraint
Defect
Validation
10. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Business Constraint(s)
Domain Subject Matter Expert (SME)
Feature
Product Backlog
11. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Solution Scope
Requirements Trace Matrix
Timebox
Throw-away Prototype
12. The human and nonhuman roles that interact with the system.
Validated Requirements
Checklist
Actor(s)
Iteration
13. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Operative Rule(s)
Monitoring
Requirements Management
Organization
14. 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.
Enterprise Architecture
Metric
Requirements Workshop
Requirements Risk Mitigation Strategy
15. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Non-functional Requirement(s)
Tester
Customer
Requirements Package
16. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Vision Statement (product vision statement)
Requirements Management Tool
Knowledge Area
Exploratory Prototype
17. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Structural Rule
Decomposition
Business Analysis Communication Plan
Operative Rule(s)
18. Creating working software in multiple releases so the entire product is delivered in portions over time.
Sponsor
Business Analysis Communication Plan
Incremental Delivery
Evolutionary Prototype
19. A system trigger that is initiated by time.
Tester
Evaluation
Customer
Temporal Event
20. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Business Analysis Communication Plan
End User
Baseline
Business Rule(s)
21. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Requirements Signoff
Use Case
Design Constraints
22. 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 Traceability
Prioritization
Walkthrough
Business Rule(s)
23. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Non-functional Requirement(s)
Swimlane
Timebox
Included Use Cases
24. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Attribute
Gap Analysis
Variance Analysis
SWOT Analysis
25. 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
Code
Business Architecture
Deliverable
Metadata
26. A specific actionable testable directive that is under the control of the business and supports a business policy.
Document Analysis
Feature
Business Goal
Business Rule(s)
27. An analysis model that shows user interface dialogs arranged as hierarchies.
Class Model
Quality Attributes
Entity-Relationship Diagram
Dialog Hierarchy
28. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Code
Throw-away Prototype
Opportunity Analysis
Iteration
29. 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.
Dialog Hierarchy
Return on Investment
Implementation Subject Matter Expert (SME)
Business Event
30. An informal solicitation of proposals from vendors.
Request For Quote (RFQ)
Use Case
Service
Span of Control
31. 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.
Prototype
Interface
Cost Benefit Analysis
Business Analysis
32. 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.
Data Model
Solution Requirement
Incremental Delivery
Use Case
33. 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
Object Oriented Modeling
Business Need(s)
Data Entity
Initiative
34. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Interoperability
Interface
Requirements Allocation
35. An actor who participates in but does not initiate a use case.
Design Constraints
Constraint
Secondary Actor
Structural Rule
36. 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.
Metadata
Change-driven Methodology
Project
Requirements Workshop
37. 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.
Organizational Unit
Analyst
Activity Diagram
Use Case Diagram
38. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Survey
Metadata
Request For Information (RFI)
Decision Tree
39. 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.
Data Flow Diagram (DFD)
Project Charter
Project Manager
Inspection
40. A shared boundary between any two persons and/or systems through which information is communicated.
Actor(s)
Interface
Technique
Relationship Map
41. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Quality Attributes
Decision Tables
Business Need(s)
Interoperability
42. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Incremental Delivery
Checklist
Project Manager
Validated Requirements
43. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Business Domain Model
Document Analysis
Inspection
Requirement
44. A prototype developed to explore or verify requirements.
Data Dictionary
Activity Diagram
Product Scope
Exploratory Prototype
45. A system trigger that is initiated by humans.
Entity-Relationship Diagram
Business Event
Decomposition
Actor(s)
46. The number of employees a manger is directly (or indirectly) responsible for.
Regulator
Technique
Survey
Span of Control
47. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Verification
Project Scope
Technique
Implementation Subject Matter Expert (SME)
48. 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
Objective
Peer Review
System
Organization
49. A person with specific expertise in an area or domain under investigation.
Requirements Traceability
State Diagram
Sponsor
Domain Subject Matter Expert (SME)
50. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Solution Scope
Metric
Quality
Process Map