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 set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Entity-Relationship Diagram
Work Product
Business Analyst
2. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Secondary Actor
Stakeholder Analysis
Black Box Tests
3. A model that defines the boundaries of a business domain or solution.
Data Model
System
Assumption
Scope Model
4. 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.
Entity-Relationship Diagram
Operative Rule(s)
Requirements Workshop
Context Diagram
5. A stakeholder person device or system that directly or indirectly accesses a system.
Secondary Actor
Requirements Trace Matrix
User
Solution
6. The features and functions that characterize a product service or result.
Design Constraints
Product Scope
Requirements Trace Matrix
User Requirements Document
7. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Requirements Validation
Use Case
SWOT Analysis
Requirements Management Plan
8. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti
Scope
Design Constraints
Class
Cardinality
9. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Verified Requirements
Requirements Trace Matrix
Project
10. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Organizational Unit
Competitive Analysis
Impact Analysis
Requirements Workshop
11. 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.
Business Analysis Communication Plan
Horizontal Prototype
Functional Requirement(s)
Decision Analysis
12. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Implementation Subject Matter Expert (SME)
Risk
Model(s)
Brainstorming
13. 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.
Elicitation
Requirements Management Plan
Span of Control
Business Analysis
14. 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.
Requirements Allocation
Validated Requirements
Business Analysis Plan
Initiative
15. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
Data Entity
User Acceptance Test
Glossary
16. A non-actionable directive that supports a business goal.
Activity
Software/Systems Requirements Specification
Business Policy
Request For Quote (RFQ)
17. 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.
End User
Stakeholder List
Evaluation
Unified Modeling Language (UML)
18. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Unified Modeling Language (UML)
Tester
Work Breakdown Structure (WBS)
Stakeholder Requirement
19. 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.
Walkthrough
Work Breakdown Structure (WBS)
Decision Tables
Service
20. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.
Observation
Domain
Business Analysis Communication Plan
Dialog Hierarchy
21. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Business Case
Actor(s)
Relationship
Data Flow Diagram (DFD)
22. A type of data model that depicts information groups as classes.
Requirements Management Tool
Requirements Signoff
Class Model
Scenario
23. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Work Breakdown Structure (WBS)
Requirements Risk Mitigation Strategy
Quality
Validated Requirements
24. A prototype that dives into the details of the interface functionality or both.
Structured Walkthrough
Scope
Vertical Prototype
Incremental Delivery
25. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
Context Diagram
Stakeholder
Process Map
Stakeholder List
26. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Impact Analysis
Initiative
Metadata
Process Model
27. 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.
Organizational Process Asset
Project Manager
Iteration
Technique
28. A person with specific expertise in an area or domain under investigation.
Domain Subject Matter Expert (SME)
Checklist
Data Flow Diagram (DFD)
Business Requirement
29. A solution or component of a solution that is the result of a project.
Business Need(s)
Product
Swimlane
Requirements Workshop
30. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
Business Analysis Plan
Subject Matter Expert (SME)
Enterprise
31. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Requirements Validation
Product Scope
Solution
Repository
32. Work carried out or on behalf of others.
Transition Requirement(s)
Service
Peer Review
Elicitation
33. A stakeholder who provides products or services to an organization.
Developer
Benchmarking
Supplier
Requirements Iteration
34. A practitioner of business analysis.
Business Analyst
Data Dictionary
Peer Review
Entity-Relationship Diagram
35. A data element with a specified data type that describes information associated with a concept or entity.
Attribute
Tester
Data Dictionary
Deliverable
36. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Requirements Iteration
Requirements Signoff
Structural Rule
37. A group of related tasks that support a key function of business analysis.
Sequence Diagram
Knowledge Area
System
Request For Quote (RFQ)
38. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Analysis Approach
Root Cause Analysis
Quality Assurance
Subject Matter Expert (SME)
39. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Work Breakdown Structure (WBS)
Iteration
Prioritization
40. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Relationship
Survey
Elicitation
Structured Walkthrough
41. Software developed and sold for a particular market.
Commercial-off-the-Shelf Software (COTS)
Verification
Business Analyst
Event
42. 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
Requirements Iteration
Data Entity
Product Scope
User Story
43. 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.
Work Breakdown Structure (WBS)
Peer Review
Relationship Map
Enterprise
44. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Solution
Organization
Desired Outcome
Vision Statement (product vision statement)
45. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Business Analysis Approach
Implementation Subject Matter Expert (SME)
Elicitation
46. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Requirements Model
Attribute
Variance Analysis
Product Scope
47. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
SWOT Analysis
Competitive Analysis
Business Analyst
48. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Root Cause Analysis
Horizontal Prototype
Cardinality
Stakeholder Requirement
49. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Initiative
Requirements Trace Matrix
Customer
Force Field Analysis
50. A shared boundary between any two persons and/or systems through which information is communicated.
Association
Interface
Service
Request For Quote (RFQ)