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 graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Force Field Analysis
Scope
Business Goal
SWOT Analysis
2. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Evolutionary Prototype
Business Analysis Approach
Requirements Model
Relationship Map
3. 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.
Non-functional Requirement(s)
Developer
Benchmarking
Process Map
4. 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
Lessons Learned Process
Dialog Hierarchy
Business Requirements Document
5. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Business Analysis Approach
Return on Investment
Data Entity
Quality Assurance
6. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Requirements Allocation
Requirements Iteration
Transition Requirement(s)
Validation
7. A system trigger that is initiated by time.
Sponsor
Risk
Activity Diagram
Temporal Event
8. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Requirements Verification
Impact Analysis
SWOT Analysis
Model(s)
9. A prototype developed to explore or verify requirements.
Document Analysis
Change-driven Methodology
Exploratory Prototype
Entity-Relationship Diagram
10. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Data Model
Model(s)
Domain Subject Matter Expert (SME)
Business Goal
11. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Iteration
Decomposition
Business Case
Sequence Diagram
12. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Document Analysis
Temporal Event
Decision Analysis
13. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Inspection
Evolutionary Prototype
Focus Group
Change Control Board (CCB)
14. An analysis model describing the data structures and attributes needed by the system.
Domain
Data Dictionary
Business Need(s)
Change-driven Methodology
15. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Entity-Relationship Diagram
Root Cause Analysis
Business Event
Observation
16. A model that defines the boundaries of a business domain or solution.
Scope Model
Prototype
Implementation Subject Matter Expert (SME)
Root Cause Analysis
17. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Model(s)
Business Need(s)
Solution Requirement
User Acceptance Test
18. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Requirements Model
Interoperability
Decomposition
Decision Tree
19. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Requirement(s) Attribute
Association
Change Control Board (CCB)
Fishbone Diagram
20. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Tester
Work Product
Event
Decomposition
21. Ability of systems to communicate by exchanging data or services.
Requirements Package
Requirements Management Tool
Interoperability
Secondary Actor
22. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Requirements Management
Use Case
Validated Requirements
Optionality
23. A link between two elements or objects in a diagram.
User
Business Requirement
Association
Horizontal Prototype
24. 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.
Impact Analysis
Initiative
Stated Requirements
Developer
25. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Return on Investment
Variance Analysis
Organizational Readiness Assessment
Service
26. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Decision Tree
Developer
Risk
27. 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
Feature
Supplier
Requirements Management
Requirements Iteration
28. The product capabilities or things the product must do for its users.
Prioritization
Assumption
Requirement(s) Attribute
Functional Requirement(s)
29. 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.
Indicator
Subject Matter Expert (SME)
Stakeholder Requirement
End User
30. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Organizational Process Asset
Feature
Design Constraints
Product Backlog
31. 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
Structured Walkthrough
Verified Requirements
Service
Stakeholder Requirement
32. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Requirements Trace Matrix
Throw-away Prototype
Defect
Exploratory Prototype
33. 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.
Vision Statement (product vision statement)
Service
Event Response Table
Constraint
34. Creating working software in multiple releases so the entire product is delivered in portions over time.
Analyst
Prioritization
Incremental Delivery
Deliverable
35. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Optionality
Object Oriented Modeling
Indicator
Exploratory Prototype
36. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Plan-driven Methodology
Temporal Event
Project Scope
Supplier
37. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Defect
Transition Requirement(s)
Organizational Unit
Prioritization
38. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Competitive Analysis
Analyst
Data Flow Diagram (DFD)
Unified Modeling Language (UML)
39. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Root Cause Analysis
Plan-driven Methodology
Document Analysis
40. 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.
Requirements Iteration
Root Cause Analysis
Inspection
Business Analyst
41. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
User Acceptance Test
Dialog Map
Objective
Methodology
42. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Lessons Learned Process
Technical Constraint(s)
Repository
Requirements Verification
43. 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.
Technical Constraint(s)
Indicator
Activity Diagram
Problem Statement
44. 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.
Operative Rule(s)
Exploratory Prototype
Decision Tables
Requirements Management
45. Work carried out or on behalf of others.
Elicitation
Organization
Event
Service
46. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Data Model
Sponsor
Business Goal
Swimlane
47. A stakeholder person device or system that directly or indirectly accesses a system.
Domain
Non-functional Requirement(s)
User
Interoperability
48. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Assumption
User
Stakeholder Analysis
Solution Scope
49. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Optionality
Requirements Management Tool
Business Analysis Approach
Implementation Subject Matter Expert (SME)
50. A type of data model that depicts information groups as classes.
Verification
Service
Code
Class Model