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 recognized association of people in the context of an organization or enterprise.
Organizational Unit
Process Map
Business Need(s)
Verified Requirements
2. 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
End User
Requirements Workshop
Business Constraint(s)
Dialog Map
3. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Problem Statement
Capability
SWOT Analysis
Black Box Tests
4. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Request For Proposal (RFP)
Work Product
Metadata
Cost Benefit Analysis
5. 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
Metric
Use Case Diagram
System
Operative Rule(s)
6. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Prototype
Interview
Verified Requirements
Evolutionary Prototype
7. 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.
Work Breakdown Structure (WBS)
User Requirements Document
Code
Evaluation
8. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Use Case Diagram
Business Rule(s)
Technique
9. An analysis model describing the data structures and attributes needed by the system.
Evolutionary Prototype
Data Dictionary
Stakeholder List
Objective
10. 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.
Implementation Subject Matter Expert (SME)
Evolutionary Prototype
Business Analysis
Project
11. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Business Requirements Document
Requirement
Requirements Risk Mitigation Strategy
Entity-Relationship Diagram
12. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Code
Business Policy
Solution Scope
Business Analysis Approach
13. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Observation
Requirements Trace Matrix
Software/Systems Requirements Specification
Requirements Management
14. A system trigger that is initiated by time.
Project Manager
Temporal Event
Methodology
Validation
15. 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.
Competitive Analysis
Requirements Allocation
Operational Support
Requirements Management Plan
16. Software developed and sold for a particular market.
Association
Developer
Commercial-off-the-Shelf Software (COTS)
Objective
17. An informal solicitation of proposals from vendors.
Project Scope
Business Analysis Approach
Request For Quote (RFQ)
Requirements Management Plan
18. 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.
Requirements Package
User Acceptance Test
Iteration
Requirements Traceability
19. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Request For Proposal (RFP)
Requirement(s) Attribute
Subject Matter Expert (SME)
Return on Investment
20. 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.
End User
Process Map
Root Cause Analysis
Requirements Allocation
21. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
Indicator
Requirements Iteration
Validated Requirements
Design Constraints
22. Software requirements that limit the options available to the system designer.
Checklist
Opportunity Analysis
Included Use Cases
Design Constraints
23. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Document Analysis
Association
Gap Analysis
Peer Review
24. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Data Entity
Verification
Constraint
Cost Benefit Analysis
25. The area covered by a particular activity or topic of interest.
Technical Constraint(s)
Domain
Scope
Requirements Workshop
26. A group of related tasks that support a key function of business analysis.
Metadata
Actor(s)
SWOT Analysis
Knowledge Area
27. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Business Architecture
Analyst
Structural Rule
Validated Requirements
28. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Objective
Business Requirement
Solution
Requirements Model
29. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Process Map
Event
User Story
Quality Assurance
30. A system trigger that is initiated by humans.
Scope
Decision Tables
Constraint
Business Event
31. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Change-driven Methodology
Requirements Verification
Scope Model
Incremental Delivery
32. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Feature
Change Control Board (CCB)
Class
Requirements Trace Matrix
33. The set of capabilities a solution must deliver in order to meet the business need.
Tester
Elicitation
Included Use Cases
Solution Scope
34. Information that is used to understand the context and validity of information recorded in a system.
Competitive Analysis
Stated Requirements
Metadata
Interoperability
35. A state or condition the business must satisfy to reach its vision.
End User
Business Goal
System
Tester
36. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Black Box Tests
Data Model
Commercial-off-the-Shelf Software (COTS)
37. The number of employees a manger is directly (or indirectly) responsible for.
Scenario
Organizational Readiness Assessment
Initiative
Span of Control
38. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Class Model
Sequence Diagram
Implementation Subject Matter Expert (SME)
Stakeholder Requirement
39. A stakeholder who uses products or services delivered by an organization.
Request For Information (RFI)
Focus Group
Decomposition
Customer
40. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode
Vision Statement (product vision statement)
Business Domain Model
Requirements Validation
Repository
41. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Actor(s)
Requirements Management
User Requirements Document
Root Cause Analysis
42. 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.
Data Model
Business Constraint(s)
Iteration
Validated Requirements
43. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
Organizational Process Asset
Domain
Interface
44. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Developer
Sequence Diagram
Business Event
Optionality
45. A data element with a specified data type that describes information associated with a concept or entity.
Stakeholder
Fishbone Diagram
Attribute
Requirements Management Plan
46. The problem area undergoing analysis.
Capability
User
Structured Walkthrough
Domain
47. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Business Policy
Enterprise
Assumption
48. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Quality
Incremental Delivery
Process Model
Activity Diagram
49. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Project Charter
Tester
Methodology
Change Control Board (CCB)
50. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Design Constraints
Vision Statement (product vision statement)
Organizational Readiness Assessment
Solution Requirement