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 description of the requirements management process.
Constraint
Dialog Hierarchy
Methodology
Requirements Management Plan
2. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Brainstorming
Capability
Validation
Dialog Map
3. 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.
Business Analyst
Subject Matter Expert (SME)
Feature
Transition Requirement(s)
4. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Technique
Product Backlog
Vision Statement (product vision statement)
Enterprise
5. 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.
Requirements Package
Requirements Trace Matrix
Decision Analysis
Focus Group
6. 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.
Organization Modeling
Verified Requirements
Validated Requirements
Scope
7. 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.
Interview
Requirement
Product
Variance Analysis
8. A model that defines the boundaries of a business domain or solution.
Design Constraints
Initiative
Scope Model
End User
9. A stakeholder who provides products or services to an organization.
Decomposition
Business Constraint(s)
Constraint
Supplier
10. A prototype developed to explore or verify requirements.
Data Dictionary
Class Model
Baseline
Exploratory Prototype
11. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Data Model
Data Entity
Work Breakdown Structure (WBS)
Event Response Table
12. 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
Included Use Cases
Baseline
Business Architecture
Business Requirement
13. Metadata related to a requirement used to assist with requirements development and management.
Data Flow Diagram (DFD)
Requirement(s) Attribute
Organizational Readiness Assessment
Request For Quote (RFQ)
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.
Requirements Workshop
Stakeholder Requirement
Glossary
Brainstorming
15. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Business Analysis Communication Plan
Initiative
Fishbone Diagram
Domain Subject Matter Expert (SME)
16. 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
Force Field Analysis
Transition Requirement(s)
User Story
Decomposition
17. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stated Requirements
Operative Rule(s)
Stakeholder Analysis
Product
18. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Scope Model
Enterprise Architecture
Solution
Document Analysis
19. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Elicitation
Cardinality
Desired Outcome
Business Need(s)
20. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Operative Rule(s)
Assumption
Problem Statement
Solution Scope
21. A data element with a specified data type that describes information associated with a concept or entity.
Attribute
Capability
Supplier
User
22. Any unique and verifiable work product or service that a party has agreed to deliver.
Sequence Diagram
Decision Tree
Deliverable
Work Product
23. 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.
Business Requirements Document
Decision Analysis
Checklist
Requirements Model
24. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
Knowledge Area
Requirements Iteration
Regulator
End User
25. A practitioner of business analysis.
Business Analysis
Business Analyst
Solution
Requirement
26. A prototype that is continuously modified and updated in response to feedback from users.
Elicitation
Evolutionary Prototype
Feasibility Study
Business Requirements Document
27. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Solution
State Diagram
Dialog Map
28. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Business Analysis Plan
Solution Requirement
Requirements Allocation
Decision Tables
29. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Scenario
Requirements Management
Impact Analysis
Class Model
30. A system trigger that is initiated by humans.
Operative Rule(s)
Business Event
Business Requirements Document
Structured Walkthrough
31. 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.
Business Process
Requirements Verification
Tester
Cost Benefit Analysis
32. 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
Stakeholder Requirement
Solution
User
Business Goal
33. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Exploratory Prototype
User Requirements Document
Opportunity Analysis
Business Analysis Plan
34. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Iteration
Vision Statement (product vision statement)
Feature
Temporal Event
35. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Assumption
Business Process
Business Analysis Communication Plan
Tester
36. The number of employees a manger is directly (or indirectly) responsible for.
Span of Control
Supplier
Force Field Analysis
Non-functional Requirement(s)
37. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Requirements Risk Mitigation Strategy
Data Model
Validation
Project Charter
38. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Requirements Management
Validated Requirements
Work Product
Requirements Trace Matrix
39. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Competitive Analysis
Decision Analysis
Plan-driven Methodology
Requirements Management Plan
40. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Gap Analysis
Peer Review
Code
Solution
41. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Stakeholder
Project Manager
Sponsor
Customer
42. The problem area undergoing analysis.
Domain
Technique
Code
Data Model
43. The work that must be performed to deliver a product service or result with the specified features and functions.
Repository
Project Scope
Requirements Validation
Analyst
44. 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.
Black Box Tests
Iteration
Verified Requirements
Peer Review
45. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Structural Rule
Feasibility Study
Entity-Relationship Diagram
Observation
46. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Brainstorming
Requirements Trace Matrix
Transition Requirement(s)
Entity-Relationship Diagram
47. An analysis model showing the life cycle of a data entity or class.
Document Analysis
Domain Subject Matter Expert (SME)
State Diagram
Requirements Management Plan
48. 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.
Interface
Validation
Event Response Table
User Requirements Document
49. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Requirements Allocation
Stakeholder List
Requirements Package
Evaluation
50. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Requirements Traceability
Validation
Stakeholder Analysis
Data Flow Diagram (DFD)