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
Software/Systems Requirements Specification
Elicitation
Request For Information (RFI)
2. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Data Entity
Relationship Map
Data Model
Project Manager
3. The number of employees a manger is directly (or indirectly) responsible for.
Change Control Board (CCB)
Span of Control
Operational Support
Requirement
4. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Organizational Unit
Supplier
Process Model
Validated Requirements
5. An actor who participates in but does not initiate a use case.
Indicator
Secondary Actor
Use Case
Vertical Prototype
6. A group or person who has interests that may be affected by an initiative or influence over it.
Interoperability
User Story
Organization Modeling
Stakeholder
7. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Structured Walkthrough
User Story
Project Charter
Elicitation
8. The degree to which a set of inherent characteristics fulfills requirements.
Operative Rule(s)
Quality
Business Domain Model
Project Charter
9. A group of related tasks that support a key function of business analysis.
Vertical Prototype
Business Process
Decomposition
Knowledge Area
10. 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.
Inspection
Indicator
Incremental Delivery
Decision Tree
11. 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).
Vision Statement (product vision statement)
Operative Rule(s)
Business Analysis Approach
Operational Support
12. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Stakeholder
Data Model
Change Control Board (CCB)
Solution
13. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Feature
User Requirements Document
Brainstorming
Change Control Board (CCB)
14. 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)
Secondary Actor
Fishbone Diagram
Event Response Table
15. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Sponsor
Vision Statement (product vision statement)
Requirements Allocation
Project Manager
16. The problem area undergoing analysis.
Verified Requirements
Included Use Cases
Domain
Sponsor
17. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Validated Requirements
Design Constraints
Validation
18. A practitioner of business analysis.
Organization
Use Case Diagram
Solution Requirement
Business Analyst
19. 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
System
Iteration
Peer Review
20. A non-actionable directive that supports a business goal.
Request For Quote (RFQ)
Business Policy
Event Response Table
Variance Analysis
21. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Requirements Management
Process Model
Glossary
Stakeholder List
22. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Change-driven Methodology
End User
Survey
23. The process of examining new business opportunities to improve organizational performance.
Business Analysis Plan
Work Product
Domain Subject Matter Expert (SME)
Opportunity Analysis
24. 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.
Requirements Allocation
Checklist
Impact Analysis
Stakeholder List
25. A fixed period of time to accomplish a desired outcome.
Technique
Timebox
Project Scope
Validated Requirements
26. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Document Analysis
Business Policy
Business Analysis Approach
Deliverable
27. The human and nonhuman roles that interact with the system.
Stakeholder Requirement
Actor(s)
Stakeholder Analysis
Focus Group
28. 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
Requirements Validation
Assumption
Dialog Map
29. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Root Cause Analysis
Quality Assurance
Product Scope
Verification
30. 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.
Business Domain Model
Plan-driven Methodology
Deliverable
Focus Group
31. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Developer
Product
Product Backlog
32. 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.
Developer
Feature
Benchmarking
Business Event
33. A stakeholder who provides products or services to an organization.
Supplier
Use Case
Assumption
Activity
34. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Requirements Signoff
Plan-driven Methodology
Survey
35. 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
Structural Rule
Interface
Business Constraint(s)
Requirements Management
36. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Regulator
Requirements Workshop
Stakeholder Analysis
Requirements Traceability
37. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
Business Case
Requirements Management
Data Model
38. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.
Business Analysis Plan
Verified Requirements
Project
Constraint
39. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Requirements Traceability
Initiative
Use Case
40. 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.
Data Flow Diagram (DFD)
Requirement(s) Defect
Service
Requirement
41. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Initiative
Variance Analysis
Force Field Analysis
Temporal Event
42. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Interface
Product Scope
Iteration
Baseline
43. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Business Requirements Document
Business Architecture
Prototype
Business Event
44. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Business Requirement
Regulator
Dialog Hierarchy
Subject Matter Expert (SME)
45. A link between two elements or objects in a diagram.
Requirements Signoff
Association
Class Model
Gap Analysis
46. A shared boundary between any two persons and/or systems through which information is communicated.
Baseline
Interface
Organizational Process Asset
Vertical Prototype
47. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Requirements Management Plan
Peer Review
State Diagram
48. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Solution Scope
Survey
Domain
Requirements Signoff
49. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Scenario
Data Flow Diagram (DFD)
Exploratory Prototype
Survey
50. Something that occurs to which an organizational unit system or process must respond.
Organizational Readiness Assessment
Event
Solution Requirement
Business Process