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. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Black Box Tests
Solution Requirement
Product Scope
Business Analysis Approach
2. 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.
Feasibility Study
Business Analysis Communication Plan
User Acceptance Test
Change-driven Methodology
3. The human and nonhuman roles that interact with the system.
Organization Modeling
Actor(s)
Solution Scope
Constraint
4. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Opportunity Analysis
Relationship Map
Impact Analysis
Peer Review
5. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Requirements Trace Matrix
Quality
Product Scope
Decision Tree
6. 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.
Quality Attributes
Business Goal
Lessons Learned Process
Business Analysis Plan
7. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Cardinality
Problem Statement
Business Need(s)
Interface
8. Ability of systems to communicate by exchanging data or services.
Interoperability
Service
Impact Analysis
Requirements Validation
9. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.
Domain Subject Matter Expert (SME)
Constraint
Requirements Risk Mitigation Strategy
Event Response Table
10. Metadata related to a requirement used to assist with requirements development and management.
Vision Statement (product vision statement)
Feature
Object Oriented Modeling
Requirement(s) Attribute
11. A function of an organization that enables it to achieve a business goal or objective.
Glossary
Requirements Trace Matrix
Capability
Stated Requirements
12. An analysis model that shows user interface dialogs arranged as hierarchies.
Quality Attributes
Requirements Allocation
Dialog Hierarchy
Work Breakdown Structure (WBS)
13. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Walkthrough
Decomposition
Enterprise
Entity-Relationship Diagram
14. The process of examining new business opportunities to improve organizational performance.
Class Model
Enterprise
Opportunity Analysis
Organization
15. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Work Product
Tester
Analyst
Model(s)
16. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various
Stakeholder Requirement
Supplier
Desired Outcome
Span of Control
17. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Validated Requirements
Actor(s)
State Diagram
18. All materials used by groups within an organization to define tailor implement and maintain their processes.
Span of Control
Organizational Process Asset
Variance Analysis
User Requirements Document
19. 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.
Work Product
Requirements Risk Mitigation Strategy
Business Analysis
Association
20. A solution or component of a solution that is the result of a project.
Relationship
Product
Secondary Actor
User Acceptance Test
21. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Business Constraint(s)
Vertical Prototype
Benchmarking
Quality
22. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Requirements Allocation
Metric
Scope Model
Decision Analysis
23. 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
Actor(s)
Context Diagram
Desired Outcome
Business Constraint(s)
24. 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 Management Plan
Data Dictionary
User Story
Functional Requirement(s)
25. A prototype that dives into the details of the interface functionality or both.
Interview
Request For Information (RFI)
Document Analysis
Vertical Prototype
26. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Prioritization
Survey
Decomposition
Commercial-off-the-Shelf Software (COTS)
27. A shared boundary between any two persons and/or systems through which information is communicated.
Solution Requirement
Business Requirement
Requirements Signoff
Interface
28. An informal solicitation of proposals from vendors.
Solution Scope
Prioritization
Request For Quote (RFQ)
Enterprise Architecture
29. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
User Story
Use Case
Horizontal Prototype
Enterprise
30. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Requirement
Data Model
Solution Scope
Validation
31. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Business Rule(s)
Baseline
SWOT Analysis
Association
32. Work carried out or on behalf of others.
Peer Review
Service
Stakeholder
Monitoring
33. An analysis model that illustrates the architecture of the system's user interface.
Requirements Iteration
Structured Walkthrough
Software/Systems Requirements Specification
Dialog Map
34. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Enterprise
Change-driven Methodology
Requirement
35. 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
Organization Modeling
Project
Class
Feasibility Study
36. 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.
Cost Benefit Analysis
Requirements Management Tool
Checklist
Service
37. 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.
Data Dictionary
Scope Model
Requirements Workshop
User Acceptance Test
38. 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
Methodology
Quality Assurance
Competitive Analysis
Organization
39. A stakeholder who uses products or services delivered by an organization.
Variance Analysis
Requirement(s) Defect
Interoperability
Customer
40. Software requirements that limit the options available to the system designer.
Design Constraints
Knowledge Area
Process Model
Monitoring
41. 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
Business Domain Model
Scenario
Quality Assurance
Benchmarking
42. 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.
Requirement
Product Backlog
Problem Statement
Baseline
43. A non-actionable directive that supports a business goal.
Observation
Stated Requirements
Requirements Signoff
Business Policy
44. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Sequence Diagram
External Interfaces
Black Box Tests
45. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Scenario
Attribute
Change Control Board (CCB)
Business Case
46. 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.
Horizontal Prototype
Business Analysis
Business Architecture
Decision Tables
47. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Business Requirements Document
Competitive Analysis
Dialog Hierarchy
Requirements Allocation
48. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Requirements Workshop
Business Analyst
Technical Constraint(s)
Tester
49. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Document Analysis
Unified Modeling Language (UML)
Relationship
User Acceptance Test
50. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Organizational Unit
Event Response Table
Defect