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 with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Fishbone Diagram
Requirements Traceability
Variance Analysis
Subject Matter Expert (SME)
2. An informal solicitation of proposals from vendors.
Problem Statement
Request For Quote (RFQ)
Stakeholder Analysis
Risk
3. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Developer
Decision Tree
Transition Requirement(s)
Project Scope
4. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Class
Enterprise Architecture
Gap Analysis
Secondary Actor
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.
Quality Attributes
Objective
Stated Requirements
Focus Group
6. 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.
Throw-away Prototype
Vertical Prototype
Verified Requirements
Object Oriented Modeling
7. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Product Backlog
Survey
Inspection
Developer
8. 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
External Interfaces
Organizational Readiness Assessment
User Acceptance Test
Operative Rule(s)
9. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Desired Outcome
Vertical Prototype
Implementation Subject Matter Expert (SME)
Objective
10. Something that occurs to which an organizational unit system or process must respond.
Requirement
Product Scope
Event
Root Cause Analysis
11. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Transition Requirement(s)
Throw-away Prototype
Requirements Model
Swimlane
12. 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).
Operational Support
Walkthrough
Context Diagram
Inspection
13. The process of examining new business opportunities to improve organizational performance.
Included Use Cases
Stakeholder
Object Oriented Modeling
Opportunity Analysis
14. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Checklist
Feature
Request For Information (RFI)
15. 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.
Business Need(s)
Requirement(s) Defect
Sponsor
Survey
16. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Project Manager
Relationship
Requirements Package
Organizational Readiness Assessment
17. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Organization Modeling
Stakeholder Analysis
Checklist
Dialog Hierarchy
18. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Business Constraint(s)
Enterprise Architecture
Requirements Validation
Sequence Diagram
19. The work that must be performed to deliver a product service or result with the specified features and functions.
Technique
Requirement
Project Scope
Verification
20. A temporary endeavor undertaken to create a unique product service or result.
Project
Supplier
Non-functional Requirement(s)
Validation
21. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Requirements Traceability
Fishbone Diagram
Decision Tables
Organizational Readiness Assessment
22. Software requirements that limit the options available to the system designer.
Relationship
Tester
Design Constraints
Business Need(s)
23. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Validation
Throw-away Prototype
Glossary
24. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Span of Control
Business Constraint(s)
User Requirements Document
Impact Analysis
25. 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.
Variance Analysis
Swimlane
Activity Diagram
Root Cause Analysis
26. 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
Attribute
Business Architecture
User Acceptance Test
Model(s)
27. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Work Product
Business Requirements Document
Business Policy
Defect
28. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Stakeholder Analysis
Quality
Business Need(s)
29. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Stated Requirements
Optionality
Cost Benefit Analysis
Actor(s)
30. 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.
Business Event
Business Analysis Communication Plan
Inspection
Prioritization
31. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Tester
Validated Requirements
Data Entity
Peer Review
32. 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.
Requirement
Horizontal Prototype
Iteration
Structural Rule
33. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Peer Review
User Acceptance Test
Use Case
Assumption
34. A stakeholder who provides products or services to an organization.
Horizontal Prototype
Metric
Constraint
Supplier
35. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Interview
Requirements Risk Mitigation Strategy
Opportunity Analysis
Deliverable
36. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Dialog Hierarchy
Interface
Temporal Event
37. A system trigger that is initiated by humans.
Problem Statement
Requirements Model
Business Event
Event Response Table
38. 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.
Request For Quote (RFQ)
Subject Matter Expert (SME)
Document Analysis
Decision Analysis
39. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Activity Diagram
Evolutionary Prototype
Desired Outcome
Monitoring
40. 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.
Business Analysis Communication Plan
Organizational Readiness Assessment
Inspection
Technique
41. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Project Charter
Solution
Scenario
Brainstorming
42. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Relationship
Structured Walkthrough
Observation
43. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Exploratory Prototype
Relationship Map
End User
Regulator
44. A partial or preliminary version of the system.
Cardinality
Prioritization
Prototype
Impact Analysis
45. A type of data model that depicts information groups as classes.
Product
Use Case
Class Model
Relationship
46. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Attribute
Benchmarking
Organization
47. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Work Breakdown Structure (WBS)
State Diagram
Business Case
Glossary
48. 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
Variance Analysis
Scenario
Activity
Transition Requirement(s)
49. A solution or component of a solution that is the result of a project.
Dialog Map
Product
Actor(s)
Organizational Process Asset
50. An analysis model showing the life cycle of a data entity or class.
Requirement(s) Defect
State Diagram
Timebox
Stated Requirements