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. 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.
Verified Requirements
Request For Proposal (RFP)
Stakeholder List
Requirements Verification
2. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Dialog Hierarchy
Problem Statement
Swimlane
Variance Analysis
3. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Structured Walkthrough
Span of Control
Domain Subject Matter Expert (SME)
Baseline
4. Software requirements that limit the options available to the system designer.
Business Architecture
Design Constraints
Requirements Validation
Product Scope
5. The work that must be performed to deliver a product service or result with the specified features and functions.
Activity
Stakeholder
Project Scope
Verified Requirements
6. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Structural Rule
Model(s)
Event
Observation
7. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Problem Statement
Prioritization
Metric
Assumption
8. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Domain
Feature
Decision Tree
9. A solution or component of a solution that is the result of a project.
Product
Business Policy
Solution
Interface
10. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Sequence Diagram
Structured Walkthrough
Code
End User
11. All materials used by groups within an organization to define tailor implement and maintain their processes.
Secondary Actor
Indicator
Organizational Process Asset
Change-driven Methodology
12. 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.
Change Control Board (CCB)
Focus Group
Decision Analysis
Business Need(s)
13. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Evaluation
Decision Tree
Requirement(s) Attribute
Lessons Learned Process
14. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Root Cause Analysis
Enterprise Architecture
Business Analysis Approach
Requirement(s) Attribute
15. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Requirements Management Tool
Data Model
Organizational Readiness Assessment
End User
16. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Baseline
Horizontal Prototype
Objective
Risk
17. 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.
Verification
Timebox
Requirement
Domain
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.
Relationship
Scope
Operational Support
Elicitation
19. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Opportunity Analysis
Data Entity
Technique
Sequence Diagram
20. An assessment of the costs and benefits associated with a proposed initiative.
Exploratory Prototype
Organizational Process Asset
Business Case
Iteration
21. A unit of work performed as part of an initiative or process.
Activity
Regulator
Association
Relationship Map
22. 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
Span of Control
User
Swimlane
23. 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
Quality Assurance
Business Analysis Communication Plan
Monitoring
24. 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.
Focus Group
Iteration
Plan-driven Methodology
Requirements Management
25. The human and nonhuman roles that interact with the system.
Actor(s)
Stakeholder Analysis
Deliverable
Interoperability
26. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Request For Quote (RFQ)
Business Analyst
Enterprise Architecture
27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Solution
Regulator
Project Manager
Exploratory Prototype
28. 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.
User Acceptance Test
Evaluation
Project Charter
Metric
29. A system trigger that is initiated by time.
Temporal Event
Decomposition
Activity
Vertical Prototype
30. A partial or preliminary version of the system.
Lessons Learned Process
Prototype
Timebox
Requirements Iteration
31. 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.
Cardinality
Return on Investment
Feasibility Study
Business Analysis
32. A data element with a specified data type that describes information associated with a concept or entity.
Brainstorming
Secondary Actor
Attribute
Knowledge Area
33. Information that is used to understand the context and validity of information recorded in a system.
Association
Operational Support
Metadata
Problem Statement
34. Any recognized association of people in the context of an organization or enterprise.
Work Breakdown Structure (WBS)
Peer Review
Organizational Unit
Business Goal
35. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Implementation Subject Matter Expert (SME)
Stakeholder Analysis
Event Response Table
Requirements Management
36. A group of related tasks that support a key function of business analysis.
Knowledge Area
Brainstorming
Process Map
Analyst
37. The quality attributes design and implementation constraints and external interfaces that the product must have.
Requirement
Non-functional Requirement(s)
Business Analysis
Requirements Validation
38. A prototype that is continuously modified and updated in response to feedback from users.
Evolutionary Prototype
Service
Event
Timebox
39. An analysis model that illustrates the architecture of the system's user interface.
Work Breakdown Structure (WBS)
Optionality
Dialog Map
Requirement(s) Defect
40. Formal approval of a set of requirements by a sponsor or other decision maker.
Prototype
Data Entity
Cardinality
Requirements Signoff
41. A function of an organization that enables it to achieve a business goal or objective.
Business Case
Capability
Walkthrough
Business Rule(s)
42. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Validated Requirements
Monitoring
Requirement(s) Defect
Exploratory Prototype
43. 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.
Project Charter
Subject Matter Expert (SME)
Work Product
Business Need(s)
44. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Document Analysis
Commercial-off-the-Shelf Software (COTS)
Software/Systems Requirements Specification
Change-driven Methodology
45. A practitioner of business analysis.
Span of Control
Monitoring
Business Analyst
Scope
46. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Requirement
Requirements Management
Business Analysis
Business Constraint(s)
47. Work carried out or on behalf of others.
Service
Request For Proposal (RFP)
Glossary
Technique
48. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Process Map
Operative Rule(s)
Association
Relationship Map
49. The problem area undergoing analysis.
Domain
Class
Business Analyst
Evaluation
50. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Monitoring
Methodology
Scope Model