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 system trigger that is initiated by time.
Temporal Event
Business Need(s)
Feasibility Study
Initiative
2. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Horizontal Prototype
Business Rule(s)
Requirements Signoff
Observation
3. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Evaluation
Brainstorming
Stakeholder Analysis
Organizational Readiness Assessment
4. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Defect
Requirements Signoff
Context Diagram
5. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Walkthrough
Enterprise Architecture
Interoperability
Requirements Management Plan
6. A partial or preliminary version of the system.
Requirements Allocation
Solution Requirement
Prototype
Requirements Package
7. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Requirement
Peer Review
Stakeholder
Requirements Validation
8. Ability of systems to communicate by exchanging data or services.
Request For Information (RFI)
Timebox
User Story
Interoperability
9. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Stakeholder Analysis
Solution Requirement
Product Backlog
Technique
10. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Elicitation
Plan-driven Methodology
Business Analysis Plan
Model(s)
11. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Structured Walkthrough
Observation
Decomposition
Defect
12. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
User Acceptance Test
User Requirements Document
Opportunity Analysis
13. 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
Business Architecture
Force Field Analysis
Vertical Prototype
Attribute
14. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Tester
Feasibility Study
Optionality
Iteration
15. 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.
Business Goal
Checklist
Black Box Tests
Data Model
16. 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
Change Control Board (CCB)
Validation
Operational Support
Business Domain Model
17. 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).
Structured Walkthrough
Activity Diagram
Data Model
Operational Support
18. 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.
Data Entity
Business Need(s)
System
Prioritization
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
Walkthrough
User Story
Requirement
Glossary
20. A stakeholder who uses products or services delivered by an organization.
Customer
Requirements Verification
Optionality
Event Response Table
21. A person with specific expertise in an area or domain under investigation.
Domain Subject Matter Expert (SME)
Survey
Supplier
Business Case
22. A state or condition the business must satisfy to reach its vision.
Business Goal
Business Analysis Plan
Dialog Map
Exploratory Prototype
23. A non-actionable directive that supports a business goal.
Business Policy
Requirements Signoff
Checklist
Commercial-off-the-Shelf Software (COTS)
24. Metadata related to a requirement used to assist with requirements development and management.
Temporal Event
Methodology
Model(s)
Requirement(s) Attribute
25. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Secondary Actor
Force Field Analysis
Relationship Map
User Requirements Document
26. A prototype developed to explore or verify requirements.
Exploratory Prototype
Problem Statement
Requirements Validation
Monitoring
27. 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
Iteration
Request For Proposal (RFP)
Request For Information (RFI)
Optionality
28. 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).
Cardinality
Transition Requirement(s)
Relationship
Temporal Event
29. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Unified Modeling Language (UML)
Interview
Indicator
Data Dictionary
30. A temporary endeavor undertaken to create a unique product service or result.
Quality Attributes
Event
Project
Horizontal Prototype
31. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Cost Benefit Analysis
Methodology
Organizational Process Asset
Dialog Map
32. 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.
Monitoring
Entity-Relationship Diagram
Requirement
Business Domain Model
33. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Peer Review
Document Analysis
Stated Requirements
Functional Requirement(s)
34. Formal approval of a set of requirements by a sponsor or other decision maker.
Activity Diagram
Requirements Signoff
Plan-driven Methodology
Return on Investment
35. A group of related tasks that support a key function of business analysis.
Request For Quote (RFQ)
Knowledge Area
Context Diagram
Force Field Analysis
36. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Change-driven Methodology
Indicator
Project Scope
Monitoring
37. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Initiative
Commercial-off-the-Shelf Software (COTS)
Customer
Solution
38. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Requirements Signoff
Functional Requirement(s)
Use Case Diagram
Throw-away Prototype
39. A specific actionable testable directive that is under the control of the business and supports a business policy.
Commercial-off-the-Shelf Software (COTS)
Solution
Business Rule(s)
Change Control Board (CCB)
40. An analysis model that illustrates the architecture of the system's user interface.
Dialog Map
Code
Observation
Desired Outcome
41. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Horizontal Prototype
Operative Rule(s)
Request For Proposal (RFP)
42. A use case composed of a common set of steps used by multiple use cases.
Opportunity Analysis
Solution Scope
Included Use Cases
Requirements Model
43. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Focus Group
Data Entity
Technique
Software/Systems Requirements Specification
44. 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
Use Case
Entity-Relationship Diagram
Business Analysis Communication Plan
45. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Implementation Subject Matter Expert (SME)
Stakeholder
Requirements Iteration
46. 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.
Evaluation
Decision Tree
Requirements Traceability
Competitive Analysis
47. 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.
Competitive Analysis
Business Requirement
Context Diagram
Cardinality
48. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Monitoring
State Diagram
Non-functional Requirement(s)
SWOT Analysis
49. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Interview
Dialog Map
Requirements Allocation
Requirements Model
50. The work that must be performed to deliver a product service or result with the specified features and functions.
Timebox
Project Scope
Inspection
Data Dictionary