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. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Stakeholder List
Requirements Package
Business Case
Tester
2. The process of examining new business opportunities to improve organizational performance.
Business Event
Opportunity Analysis
Project
Organization Modeling
3. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Project Scope
Competitive Analysis
Solution Requirement
Observation
4. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
System
Validated Requirements
Requirements Trace Matrix
Iteration
5. 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
Business Goal
User Story
Observation
Enterprise Architecture
6. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Decision Tree
Verified Requirements
Request For Quote (RFQ)
Process Model
7. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Business Process
Interview
Business Analysis Approach
External Interfaces
8. The quality attributes design and implementation constraints and external interfaces that the product must have.
Implementation Subject Matter Expert (SME)
Metadata
Non-functional Requirement(s)
Association
9. A specific actionable testable directive that is under the control of the business and supports a business policy.
Change Control Board (CCB)
Organization Modeling
Business Rule(s)
External Interfaces
10. An analysis model describing the data structures and attributes needed by the system.
Requirement(s) Attribute
Data Dictionary
Request For Information (RFI)
User Story
11. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Process Map
Commercial-off-the-Shelf Software (COTS)
Structured Walkthrough
Change Control Board (CCB)
12. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Risk
Requirements Risk Mitigation Strategy
Included Use Cases
13. A system trigger that is initiated by humans.
Use Case Diagram
Requirement
Business Event
Requirements Risk Mitigation Strategy
14. All materials used by groups within an organization to define tailor implement and maintain their processes.
Business Analysis Communication Plan
Organizational Process Asset
Incremental Delivery
Optionality
15. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Scenario
Organization Modeling
Span of Control
Solution Requirement
16. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Quality Assurance
Business Architecture
Data Dictionary
System
17. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
External Interfaces
Product Backlog
Requirements Package
Structured Walkthrough
18. 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.
Technique
Requirements Iteration
Elicitation
Data Flow Diagram (DFD)
19. 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.
Inspection
Decision Analysis
Cost Benefit Analysis
Requirement
20. The problem area undergoing analysis.
Domain
Requirements Validation
User Story
Business Constraint(s)
21. An assessment of the costs and benefits associated with a proposed initiative.
Business Constraint(s)
Quality Attributes
Problem Statement
Business Case
22. 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.
Solution Scope
Data Entity
Feature
Work Breakdown Structure (WBS)
23. An analysis model that illustrates the architecture of the system's user interface.
Dialog Map
Repository
Data Flow Diagram (DFD)
Enterprise
24. A group of related tasks that support a key function of business analysis.
Project Charter
Knowledge Area
Stakeholder List
Commercial-off-the-Shelf Software (COTS)
25. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Developer
Code
Requirement(s) Defect
Document Analysis
26. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Objective
Requirements Model
Request For Proposal (RFP)
Black Box Tests
27. 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
Scenario
Sequence Diagram
SWOT Analysis
28. A person with specific expertise in an area or domain under investigation.
Included Use Cases
Requirements Package
Feasibility Study
Domain Subject Matter Expert (SME)
29. A prototype that dives into the details of the interface functionality or both.
Swimlane
Business Rule(s)
Vertical Prototype
Transition Requirement(s)
30. 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
Business Constraint(s)
Decomposition
Business Analysis Plan
31. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
Baseline
Decision Tables
Business Policy
Project Manager
32. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Horizontal Prototype
Observation
System
Root Cause Analysis
33. 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.
Monitoring
End User
Verified Requirements
Incremental Delivery
34. A stakeholder with legal or governance authority over the solution or the process used to develop it.
User Requirements Document
Stated Requirements
Regulator
Requirement(s) Attribute
35. 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.
Business Goal
Object Oriented Modeling
Change Control Board (CCB)
Project Charter
36. 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
Operative Rule(s)
Validation
Requirement
Transition Requirement(s)
37. The features and functions that characterize a product service or result.
Use Case
Verification
State Diagram
Product Scope
38. Work carried out or on behalf of others.
Code
Scope
Stakeholder List
Service
39. A system trigger that is initiated by time.
Requirement(s) Defect
Temporal Event
Code
Evolutionary Prototype
40. 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.
Peer Review
Requirements Allocation
Business Architecture
Verification
41. The work that must be performed to deliver a product service or result with the specified features and functions.
Interface
Project Scope
Problem Statement
Walkthrough
42. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
Request For Information (RFI)
Dialog Hierarchy
External Interfaces
43. 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.
Activity Diagram
Scope Model
Inspection
Request For Proposal (RFP)
44. 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.
Analyst
Benchmarking
User Story
Implementation Subject Matter Expert (SME)
45. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Requirement(s) Defect
Organization Modeling
Process Map
Functional Requirement(s)
46. A prototype that is continuously modified and updated in response to feedback from users.
Walkthrough
Model(s)
Code
Evolutionary Prototype
47. 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.
Baseline
Throw-away Prototype
Transition Requirement(s)
Requirements Package
48. 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.
Plan-driven Methodology
Fishbone Diagram
Baseline
Requirements Package
49. A stakeholder person device or system that directly or indirectly accesses a system.
Class
Black Box Tests
User
Data Entity
50. A link between two elements or objects in a diagram.
Span of Control
Association
Knowledge Area
Operative Rule(s)