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. 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.
Requirements Allocation
Decision Analysis
Assumption
Process Map
2. 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.
User
Black Box Tests
Incremental Delivery
Project Charter
3. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Product
Requirements Trace Matrix
Business Analysis Approach
Prioritization
4. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a
Organizational Process Asset
Context Diagram
Object Oriented Modeling
Business Analysis
5. 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).
Business Policy
Cardinality
Tester
Objective
6. Limitations on the design of a solution that derive from the technology used in its implementation.
Solution Requirement
Structural Rule
Technical Constraint(s)
Interface
7. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Gap Analysis
Glossary
Process Model
Incremental Delivery
8. 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.
Entity-Relationship Diagram
End User
Attribute
Event
9. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.
Dialog Map
Requirements Package
Monitoring
Use Case
10. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Attribute
Regulator
Feasibility Study
Data Entity
11. 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.
Association
Relationship
Context Diagram
System
12. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Evaluation
Optionality
Enterprise Architecture
Subject Matter Expert (SME)
13. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Regulator
User Story
Gap Analysis
External Interfaces
14. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
Exploratory Prototype
Organization
Requirements Workshop
Business Requirement
15. A practitioner of business analysis.
Feasibility Study
Variance Analysis
Business Analyst
Data Dictionary
16. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Prototype
Request For Information (RFI)
Objective
Checklist
17. The area covered by a particular activity or topic of interest.
Scope
Inspection
User Requirements Document
Prototype
18. A type of data model that depicts information groups as classes.
Peer Review
Organization Modeling
Software/Systems Requirements Specification
Class Model
19. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Requirements Traceability
Brainstorming
Requirements Verification
Business Process
20. 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.
Validation
Evaluation
Regulator
Organization Modeling
21. 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.
Analyst
Focus Group
Use Case
Inspection
22. A prototype that is continuously modified and updated in response to feedback from users.
Evolutionary Prototype
Scope
Fishbone Diagram
Stakeholder Analysis
23. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Change-driven Methodology
Prototype
Business Requirement
Relationship Map
24. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Assumption
Baseline
Use Case Diagram
Attribute
25. A partial or preliminary version of the system.
Metric
Decision Tables
Incremental Delivery
Prototype
26. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Product
System
Project Charter
Observation
27. 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
Structured Walkthrough
Business Rule(s)
Validation
Business Architecture
28. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Capability
Subject Matter Expert (SME)
Technique
Code
29. A unit of work performed as part of an initiative or process.
Activity
Monitoring
Optionality
External Interfaces
30. 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
Throw-away Prototype
Business Architecture
Transition Requirement(s)
Domain Subject Matter Expert (SME)
31. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Requirements Risk Mitigation Strategy
Dialog Hierarchy
Evolutionary Prototype
Attribute
32. 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.
Business Analysis
Force Field Analysis
Use Case
Data Dictionary
33. An analysis model describing the data structures and attributes needed by the system.
Requirements Iteration
Opportunity Analysis
System
Data Dictionary
34. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
System
User
Context Diagram
Constraint
35. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Requirements Validation
Swimlane
Project Charter
Requirements Signoff
36. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Structured Walkthrough
Business Constraint(s)
SWOT Analysis
User
37. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Dialog Hierarchy
Decision Tree
Use Case Diagram
38. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Gap Analysis
Monitoring
Project Manager
Prototype
39. 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.
Object Oriented Modeling
Enterprise
Knowledge Area
Organizational Process Asset
40. A non-actionable directive that supports a business goal.
Business Policy
Risk
Methodology
Activity Diagram
41. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Business Rule(s)
Product Backlog
Technical Constraint(s)
42. A shared boundary between any two persons and/or systems through which information is communicated.
Class
Knowledge Area
SWOT Analysis
Interface
43. 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.
Stated Requirements
Scope
Cardinality
Technique
44. The human and nonhuman roles that interact with the system.
Operative Rule(s)
Regulator
Actor(s)
Developer
45. The number of employees a manger is directly (or indirectly) responsible for.
Scope
Event Response Table
Inspection
Span of Control
46. A stakeholder who provides products or services to an organization.
Inspection
Peer Review
Change Control Board (CCB)
Supplier
47. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Timebox
Operational Support
Baseline
Metadata
48. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.
Walkthrough
Quality Assurance
Implementation Subject Matter Expert (SME)
Decision Analysis
49. A system trigger that is initiated by time.
Interoperability
Temporal Event
Data Entity
Business Constraint(s)
50. An analysis model that shows user interface dialogs arranged as hierarchies.
Gap Analysis
Exploratory Prototype
Dialog Hierarchy
Solution Requirement