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. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Developer
Validation
Competitive Analysis
Technique
2. 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.
Glossary
Stakeholder List
Structured Walkthrough
Peer Review
3. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Glossary
Monitoring
Requirements Trace Matrix
Product
4. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
User Acceptance Test
State Diagram
Temporal Event
Return on Investment
5. A group or person who has interests that may be affected by an initiative or influence over it.
Decomposition
Use Case Diagram
User Acceptance Test
Stakeholder
6. 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.
Cost Benefit Analysis
Class Model
Focus Group
Structured Walkthrough
7. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Validated Requirements
Indicator
Gap Analysis
Opportunity Analysis
8. 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)
Scenario
Span of Control
Stakeholder Analysis
9. A link between two elements or objects in a diagram.
Root Cause Analysis
Association
Decomposition
Operational Support
10. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Swimlane
Initiative
Benchmarking
Work Breakdown Structure (WBS)
11. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Unified Modeling Language (UML)
Inspection
Process Model
Evaluation
12. A description of the requirements management process.
Problem Statement
Objective
Document Analysis
Requirements Management Plan
13. A non-actionable directive that supports a business goal.
Prioritization
Service
Business Policy
Project Scope
14. 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.
Operative Rule(s)
Class
Evaluation
Swimlane
15. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Entity-Relationship Diagram
Dialog Hierarchy
Regulator
Business Constraint(s)
16. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Product
Defect
Constraint
Customer
17. 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.
Business Analysis
User Story
Business Analysis Plan
Actor(s)
18. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Subject Matter Expert (SME)
Plan-driven Methodology
Request For Information (RFI)
Cost Benefit Analysis
19. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Work Product
Interoperability
Business Requirement
Metric
20. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Business Domain Model
Enterprise
Solution Requirement
Survey
21. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Horizontal Prototype
Stakeholder List
Requirements Validation
22. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Black Box Tests
Change Control Board (CCB)
User Requirements Document
Object Oriented Modeling
23. A state or condition the business must satisfy to reach its vision.
Business Goal
Lessons Learned Process
Organizational Unit
Baseline
24. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Work Product
Methodology
Requirements Allocation
Non-functional Requirement(s)
25. The problem area undergoing analysis.
Checklist
Domain
Verification
Relationship
26. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Timebox
Model(s)
Business Constraint(s)
27. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Context Diagram
Association
Business Process
28. A stakeholder who provides products or services to an organization.
Structural Rule
Supplier
Requirements Traceability
Business Domain Model
29. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Project Manager
Entity-Relationship Diagram
Project Scope
Project
30. A system of programming statements symbols and rules used to represent instructions to a computer.
Code
Process Model
External Interfaces
Baseline
31. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Subject Matter Expert (SME)
System
Document Analysis
Competitive Analysis
32. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Methodology
Developer
Stakeholder Requirement
Observation
33. 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.
Metric
Solution
Checklist
Scope
34. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
Evaluation
Peer Review
Change-driven Methodology
35. 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.
Walkthrough
Scope
Business Requirement
Throw-away Prototype
36. The process of examining new business opportunities to improve organizational performance.
Data Dictionary
Cardinality
Opportunity Analysis
Solution Requirement
37. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Sequence Diagram
Requirements Traceability
Requirement
Business Policy
38. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Analysis Approach
Decomposition
Solution
Assumption
39. A prototype developed to explore or verify requirements.
External Interfaces
Exploratory Prototype
Quality Attributes
Deliverable
40. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Organization Modeling
Variance Analysis
Transition Requirement(s)
Solution
41. Work carried out or on behalf of others.
Requirements Validation
Domain
Relationship
Service
42. A prototype that dives into the details of the interface functionality or both.
Context Diagram
Capability
Vertical Prototype
Product Backlog
43. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Requirements Verification
Vision Statement (product vision statement)
Subject Matter Expert (SME)
Data Dictionary
44. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Project Charter
Impact Analysis
Service
Requirements Trace Matrix
45. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Cardinality
Enterprise Architecture
Requirements Management Plan
Data Model
46. 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
Requirements Management
Change Control Board (CCB)
Quality Attributes
47. A group of related tasks that support a key function of business analysis.
Benchmarking
Knowledge Area
Event Response Table
Design Constraints
48. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
Requirements Model
Class Model
Problem Statement
Operational Support
49. An actor who participates in but does not initiate a use case.
Secondary Actor
Business Analysis Approach
Objective
Work Breakdown Structure (WBS)
50. 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.
Stated Requirements
Vertical Prototype
Iteration
Organizational Readiness Assessment