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 characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Business Process
Survey
Throw-away Prototype
2. The features and functions that characterize a product service or result.
Product Scope
Solution Requirement
Repository
Deliverable
3. Software developed and sold for a particular market.
Survey
Commercial-off-the-Shelf Software (COTS)
Context Diagram
Request For Quote (RFQ)
4. A unit of work performed as part of an initiative or process.
Data Entity
Business Analysis Communication Plan
Activity
Deliverable
5. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Business Constraint(s)
Competitive Analysis
Validated Requirements
Requirement
6. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Validation
Organizational Readiness Assessment
Business Requirement
Cardinality
7. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Methodology
Domain Subject Matter Expert (SME)
Observation
Monitoring
8. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Request For Quote (RFQ)
Technique
Initiative
9. Metadata related to a requirement used to assist with requirements development and management.
Business Analysis
Stakeholder Analysis
Structured Walkthrough
Requirement(s) Attribute
10. A non-actionable directive that supports a business goal.
Use Case
Attribute
Temporal Event
Business Policy
11. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Requirements Validation
Optionality
Change Control Board (CCB)
Feasibility Study
12. 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.
Association
Code
Organizational Unit
Horizontal Prototype
13. A fixed period of time to accomplish a desired outcome.
Operational Support
Sequence Diagram
Timebox
Event Response Table
14. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Domain Subject Matter Expert (SME)
Inspection
Non-functional Requirement(s)
Implementation Subject Matter Expert (SME)
15. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Unified Modeling Language (UML)
User Acceptance Test
Requirements Management Tool
Quality
16. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Organizational Readiness Assessment
Data Flow Diagram (DFD)
Requirements Management Tool
Entity-Relationship Diagram
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.
Technique
Business Analysis
Stakeholder Analysis
Requirements Risk Mitigation Strategy
18. A specific actionable testable directive that is under the control of the business and supports a business policy.
Evaluation
Requirement(s) Attribute
User Story
Business Rule(s)
19. An analysis model showing the life cycle of a data entity or class.
State Diagram
Requirements Validation
Requirements Model
Requirements Risk Mitigation Strategy
20. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
Sponsor
Business Rule(s)
Domain
Implementation Subject Matter Expert (SME)
21. A structured examination of an identified problem to understand the underlying causes.
Business Analysis Approach
Root Cause Analysis
Feasibility Study
Project
22. 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
Organization
Temporal Event
Secondary Actor
User Acceptance Test
23. 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
Association
Developer
Requirements Package
24. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine
Enterprise
Stakeholder Analysis
Business Requirement
Business Architecture
25. Any recognized association of people in the context of an organization or enterprise.
Business Analysis Communication Plan
Requirements Validation
Organizational Unit
Verification
26. 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
Cost Benefit Analysis
Business Analysis Approach
External Interfaces
27. 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.
Business Policy
Decision Tables
Project Manager
End User
28. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Business Need(s)
Defect
Subject Matter Expert (SME)
Requirement(s) Defect
29. 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.
Evaluation
SWOT Analysis
Tester
Business Requirement
30. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Cardinality
Unified Modeling Language (UML)
Interoperability
Decomposition
31. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Defect
Business Need(s)
Business Architecture
Project Scope
32. An analysis model that illustrates the architecture of the system's user interface.
Verified Requirements
Dialog Map
Developer
Customer
33. Formal approval of a set of requirements by a sponsor or other decision maker.
Throw-away Prototype
Solution Requirement
Requirements Signoff
Quality
34. 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.
Data Flow Diagram (DFD)
Requirement(s) Attribute
User Requirements Document
Cost Benefit Analysis
35. Information that is used to understand the context and validity of information recorded in a system.
Dialog Map
Metadata
Prioritization
User Requirements Document
36. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Activity
Constraint
Supplier
Objective
37. A partial or preliminary version of the system.
Secondary Actor
Prototype
Business Requirements Document
Customer
38. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Activity
Competitive Analysis
Monitoring
39. 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.
Organizational Process Asset
Evaluation
Verification
Methodology
40. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Verified Requirements
Use Case Diagram
Impact Analysis
Organizational Unit
41. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Model(s)
Class Model
Document Analysis
Span of Control
42. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Stakeholder Analysis
Product Backlog
Document Analysis
43. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Lessons Learned Process
Project
Requirement(s) Attribute
44. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Monitoring
Vertical Prototype
Business Rule(s)
45. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Risk
Requirements Model
SWOT Analysis
Checklist
46. A practitioner of business analysis.
Capability
Business Analyst
Organizational Process Asset
Monitoring
47. 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
Data Model
Technique
User Story
Subject Matter Expert (SME)
48. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Request For Information (RFI)
Business Need(s)
Methodology
Requirements Verification
49. A measure of the profitability of a project or investment.
Defect
Dialog Map
Requirement
Return on Investment
50. The quality attributes design and implementation constraints and external interfaces that the product must have.
Quality Attributes
Brainstorming
Non-functional Requirement(s)
Prototype