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 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.
Implementation Subject Matter Expert (SME)
Tester
Technique
Metric
2. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Evolutionary Prototype
Methodology
Project Scope
Requirements Workshop
3. An analysis model that shows user interface dialogs arranged as hierarchies.
Design Constraints
Dialog Hierarchy
Decision Tree
Operational Support
4. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Structural Rule
Requirement
Business Event
Focus Group
5. 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.
Business Constraint(s)
Assumption
Business Analyst
Stated Requirements
6. A prototype that dives into the details of the interface functionality or both.
Decision Tree
Event
Vertical Prototype
Business Requirement
7. 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.
Request For Quote (RFQ)
Inspection
Analyst
Process Map
8. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Use Case
Objective
Benchmarking
System
9. An actor who participates in but does not initiate a use case.
Glossary
Secondary Actor
Decision Tables
Evolutionary Prototype
10. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Enterprise Architecture
Interview
Monitoring
11. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Black Box Tests
Brainstorming
System
Change Control Board (CCB)
12. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Evolutionary Prototype
Requirement
Stakeholder List
Metric
13. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Metadata
Project Charter
Scope
Lessons Learned Process
14. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Functional Requirement(s)
Survey
Vertical Prototype
Requirements Validation
15. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Transition Requirement(s)
Request For Information (RFI)
Throw-away Prototype
16. 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 Analyst
Requirement(s) Defect
Decision Tables
Glossary
17. Something that occurs to which an organizational unit system or process must respond.
Analyst
Event
Business Analyst
Opportunity Analysis
18. A prototype developed to explore or verify requirements.
Exploratory Prototype
Scope
Domain Subject Matter Expert (SME)
Knowledge Area
19. 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
User Story
Business Domain Model
Vision Statement (product vision statement)
Metric
20. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Class Model
Sponsor
Stakeholder List
Requirements Management Tool
21. A structured examination of an identified problem to understand the underlying causes.
Defect
Black Box Tests
Structural Rule
Root Cause Analysis
22. 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).
Solution Requirement
Operational Support
Business Domain Model
Sequence Diagram
23. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Requirements Validation
Cardinality
Request For Information (RFI)
Capability
24. A function of an organization that enables it to achieve a business goal or objective.
Capability
Activity
Requirements Iteration
Metadata
25. 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.
Scenario
Structured Walkthrough
Enterprise
Inspection
26. 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.
Requirements Model
Quality
Throw-away Prototype
Scope Model
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
Request For Information (RFI)
Transition Requirement(s)
Return on Investment
User Requirements Document
28. 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
Requirements Iteration
Request For Quote (RFQ)
Stakeholder List
Class
29. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Exploratory Prototype
Verified Requirements
Document Analysis
Interview
30. A partial or preliminary version of the system.
Process Model
Validated Requirements
Prototype
Knowledge Area
31. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Metric
User
Requirement
Feasibility Study
32. 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.
Customer
Object Oriented Modeling
Business Analysis Plan
Activity Diagram
33. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Organizational Process Asset
Stakeholder Analysis
Requirement(s) Attribute
34. A non-actionable directive that supports a business goal.
Business Policy
Unified Modeling Language (UML)
Business Need(s)
Vision Statement (product vision statement)
35. The human and nonhuman roles that interact with the system.
Requirements Trace Matrix
Gap Analysis
Requirements Management Tool
Actor(s)
36. A state or condition the business must satisfy to reach its vision.
Software/Systems Requirements Specification
Requirements Allocation
Business Goal
Product Backlog
37. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Change-driven Methodology
Decomposition
Span of Control
Request For Proposal (RFP)
38. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Business Analysis Approach
User Requirements Document
Validated Requirements
Requirements Model
39. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
Unified Modeling Language (UML)
Requirements Trace Matrix
End User
External Interfaces
40. 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
Process Map
Requirements Iteration
Observation
Requirements Management
41. A temporary endeavor undertaken to create a unique product service or result.
Cardinality
Verified Requirements
Stakeholder Requirement
Project
42. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Decision Analysis
Business Analysis Approach
Metric
Structured Walkthrough
43. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Requirement(s) Defect
Defect
Methodology
Indicator
44. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Competitive Analysis
Activity Diagram
Indicator
Request For Information (RFI)
45. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Structural Rule
Requirement(s) Defect
Solution
Work Breakdown Structure (WBS)
46. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Data Dictionary
Black Box Tests
Tester
Request For Proposal (RFP)
47. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Requirements Traceability
Relationship
Secondary Actor
Use Case
48. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Constraint
Baseline
Unified Modeling Language (UML)
Regulator
49. 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
Process Map
Model(s)
Evolutionary Prototype
Request For Information (RFI)
50. A person with specific expertise in an area or domain under investigation.
Domain Subject Matter Expert (SME)
State Diagram
Class Model
Prioritization