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 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.
Product Backlog
Requirements Allocation
Activity Diagram
Monitoring
2. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Quality Attributes
Domain
Business Requirement
3. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Peer Review
Requirements Management Plan
Constraint
Tester
4. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Interface
Change-driven Methodology
Data Entity
5. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Document Analysis
Relationship Map
Class
Competitive Analysis
6. 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
Feasibility Study
Organizational Process Asset
Organization
Solution Requirement
7. A partial or preliminary version of the system.
Desired Outcome
Prototype
Transition Requirement(s)
Business Case
8. Work carried out or on behalf of others.
Entity-Relationship Diagram
Service
Business Policy
Methodology
9. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Baseline
Product
Business Rule(s)
10. 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
Stated Requirements
Dialog Hierarchy
Requirements Iteration
Relationship
11. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User Requirements Document
Interoperability
Validation
Return on Investment
12. 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.
Walkthrough
Brainstorming
Business Analysis Plan
Business Analysis
13. Metadata related to a requirement used to assist with requirements development and management.
Technique
Knowledge Area
Requirements Traceability
Requirement(s) Attribute
14. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Secondary Actor
Process Model
Decision Tables
User Requirements Document
15. 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
Business Constraint(s)
Business Need(s)
Business Analysis Approach
Stakeholder Requirement
16. A fixed period of time to accomplish a desired outcome.
External Interfaces
Activity
Timebox
Business Analyst
17. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
User Story
Enterprise Architecture
Activity Diagram
Operational Support
18. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Prioritization
Brainstorming
Business Requirement
19. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
System
Work Product
Scope
Decision Tree
20. The process of examining new business opportunities to improve organizational performance.
Business Architecture
Code
Opportunity Analysis
Commercial-off-the-Shelf Software (COTS)
21. Limitations on the design of a solution that derive from the technology used in its implementation.
Iteration
Dialog Hierarchy
Scope Model
Technical Constraint(s)
22. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Requirements Management
Observation
Peer Review
Verification
23. 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.
Interview
Span of Control
Implementation Subject Matter Expert (SME)
Verification
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.
Interoperability
Evolutionary Prototype
Methodology
Software/Systems Requirements Specification
25. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Temporal Event
Requirements Validation
Regulator
Business Analysis Approach
26. A type of data model that depicts information groups as classes.
Cost Benefit Analysis
Class Model
Desired Outcome
Organization Modeling
27. 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
Transition Requirement(s)
Organizational Readiness Assessment
Feasibility Study
Validated Requirements
28. An analysis model describing the data structures and attributes needed by the system.
Data Model
Requirements Management Tool
Data Dictionary
Business Need(s)
29. The quality attributes design and implementation constraints and external interfaces that the product must have.
Product Scope
Non-functional Requirement(s)
Span of Control
Business Analysis
30. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Tester
Product Scope
Black Box Tests
Organization Modeling
31. 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
Benchmarking
Business Case
Attribute
32. A model that defines the boundaries of a business domain or solution.
Scope Model
Request For Information (RFI)
Iteration
Code
33. 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.
Data Entity
Activity
Evaluation
Class
34. 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.
Requirement
Object Oriented Modeling
Metadata
Inspection
35. 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.
Organizational Unit
Structural Rule
Indicator
Enterprise
36. 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).
Sponsor
Developer
Operational Support
Quality Assurance
37. 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.
Stated Requirements
Event Response Table
Force Field Analysis
Tester
38. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Survey
Data Model
Model(s)
Code
39. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Project Manager
Exploratory Prototype
Validated Requirements
40. An actor who participates in but does not initiate a use case.
Secondary Actor
Change Control Board (CCB)
Operational Support
Domain
41. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Requirements Trace Matrix
Requirements Traceability
Use Case
Prioritization
42. A state or condition the business must satisfy to reach its vision.
Lessons Learned Process
Plan-driven Methodology
Business Analysis Communication Plan
Business Goal
43. 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.
Gap Analysis
User
Requirements Verification
Context Diagram
44. A temporary endeavor undertaken to create a unique product service or result.
Functional Requirement(s)
Event
Project
Unified Modeling Language (UML)
45. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Data Dictionary
SWOT Analysis
Monitoring
Vision Statement (product vision statement)
46. Any unique and verifiable work product or service that a party has agreed to deliver.
Requirements Management Plan
Non-functional Requirement(s)
Requirements Package
Deliverable
47. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Verification
Requirements Allocation
Data Flow Diagram (DFD)
Business Analysis
48. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Quality Attributes
Structural Rule
Indicator
Decision Analysis
49. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Requirements Package
Project Manager
Walkthrough
Peer Review
50. 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.
Code
Cost Benefit Analysis
Decision Tree
Use Case