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. Any unique and verifiable work product or service that a party has agreed to deliver.
Gap Analysis
Black Box Tests
Requirements Validation
Deliverable
2. A measure of the profitability of a project or investment.
Return on Investment
Requirements Management
Business Event
Capability
3. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Tester
Stated Requirements
Business Domain Model
4. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Event Response Table
Use Case
Organizational Readiness Assessment
Organization
5. 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.
Elicitation
Impact Analysis
Business Rule(s)
Span of Control
6. A data element with a specified data type that describes information associated with a concept or entity.
Interoperability
Sponsor
Attribute
Quality Attributes
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 Analysis Communication Plan
Knowledge Area
Walkthrough
Business Process
8. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Elicitation
Entity-Relationship Diagram
Organizational Unit
9. A temporary endeavor undertaken to create a unique product service or result.
Project Charter
Document Analysis
Project
Objective
10. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Technique
Operational Support
Request For Information (RFI)
Sequence Diagram
11. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Domain
Tester
Structural Rule
12. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Inspection
Cardinality
Metadata
Quality Assurance
13. 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.
Entity-Relationship Diagram
Business Analysis Communication Plan
Observation
Class
14. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Business Domain Model
Lessons Learned Process
Solution Requirement
15. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Fishbone Diagram
Requirements Validation
Survey
16. 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
Interface
Focus Group
Business Need(s)
Organization
17. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Actor(s)
Solution Requirement
Model(s)
Data Entity
18. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Feasibility Study
Relationship Map
Opportunity Analysis
Included Use Cases
19. A shared boundary between any two persons and/or systems through which information is communicated.
State Diagram
Data Dictionary
Request For Information (RFI)
Interface
20. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Horizontal Prototype
Survey
Requirements Validation
Solution Scope
21. 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.
Event
Peer Review
Use Case
End User
22. 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.
Solution
Domain Subject Matter Expert (SME)
Requirements Validation
Requirements Workshop
23. 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.
Force Field Analysis
Stated Requirements
Decision Tree
Return on Investment
24. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Business Domain Model
Scenario
Requirements Verification
Focus Group
25. An assessment of the costs and benefits associated with a proposed initiative.
Requirements Model
Business Case
Indicator
Metric
26. A group of related tasks that support a key function of business analysis.
Black Box Tests
Business Case
Document Analysis
Knowledge Area
27. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Verified Requirements
Request For Information (RFI)
Relationship
Brainstorming
28. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Change-driven Methodology
Inspection
Metric
Scenario
29. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Class Model
Prototype
Indicator
Competitive Analysis
30. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
External Interfaces
Requirement(s) Defect
Model(s)
Business Requirements Document
31. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Solution Scope
Business Analysis Plan
Cost Benefit Analysis
Unified Modeling Language (UML)
32. A state or condition the business must satisfy to reach its vision.
Transition Requirement(s)
Business Goal
Repository
Requirements Management Tool
33. A structured examination of an identified problem to understand the underlying causes.
Evaluation
Interview
Root Cause Analysis
Change-driven Methodology
34. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Brainstorming
Software/Systems Requirements Specification
Business Case
Vision Statement (product vision statement)
35. 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.
Initiative
Context Diagram
Requirement
Opportunity Analysis
36. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Activity Diagram
Brainstorming
Non-functional Requirement(s)
Request For Quote (RFQ)
37. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Initiative
Optionality
Prioritization
Indicator
38. An analysis model showing the life cycle of a data entity or class.
Analyst
Requirement(s) Defect
State Diagram
Transition Requirement(s)
39. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Code
Gap Analysis
Solution
Requirements Iteration
40. 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.
Regulator
Feasibility Study
Code
Desired Outcome
41. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Class Model
Optionality
Request For Proposal (RFP)
Objective
42. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Sponsor
Assumption
Methodology
Class Model
43. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Requirement(s) Attribute
Decomposition
External Interfaces
44. Something that occurs to which an organizational unit system or process must respond.
Requirements Validation
Event
Temporal Event
Survey
45. 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.
Throw-away Prototype
Business Analysis Plan
Scope Model
Elicitation
46. 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.
Decomposition
Business Goal
Dialog Map
Plan-driven Methodology
47. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Domain Subject Matter Expert (SME)
Glossary
Baseline
Problem Statement
48. A model that defines the boundaries of a business domain or solution.
Stated Requirements
Baseline
Observation
Scope Model
49. A practitioner of business analysis.
Business Architecture
Temporal Event
Business Analyst
Metadata
50. 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.
Prototype
Requirement
Validation
Temporal Event