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 analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Requirements Verification
Decision Tables
Use Case Diagram
Data Flow Diagram (DFD)
2. The features and functions that characterize a product service or result.
Repository
Business Rule(s)
Product Scope
Lessons Learned Process
3. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Quality Attributes
Constraint
Requirements Allocation
Business Event
4. A state or condition the business must satisfy to reach its vision.
Business Analysis Communication Plan
Transition Requirement(s)
Optionality
Business Goal
5. 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.
Stakeholder Analysis
Verified Requirements
Focus Group
Business Analysis Approach
6. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Business Domain Model
Checklist
Non-functional Requirement(s)
Business Analysis Plan
7. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Interview
Requirements Iteration
Requirements Validation
8. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Event Response Table
Business Case
External Interfaces
9. Software developed and sold for a particular market.
Desired Outcome
Commercial-off-the-Shelf Software (COTS)
Technique
Included Use Cases
10. The problem area undergoing analysis.
Project Manager
Organization
Monitoring
Domain
11. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Survey
Scenario
Requirements Traceability
Quality
12. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Prioritization
Risk
Operational Support
Product Backlog
13. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Trace Matrix
Solution Scope
Technical Constraint(s)
Product Scope
14. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Glossary
Stakeholder Analysis
Change Control Board (CCB)
Business Event
15. A group of related tasks that support a key function of business analysis.
Solution Requirement
Knowledge Area
Plan-driven Methodology
Domain Subject Matter Expert (SME)
16. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Regulator
Business Analysis
Activity Diagram
Desired Outcome
17. 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
Requirements Iteration
Activity
Requirements Model
Requirements Allocation
18. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Structural Rule
Request For Information (RFI)
System
Stakeholder
19. 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.
Focus Group
Request For Quote (RFQ)
Operative Rule(s)
Product
20. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Decision Tree
Timebox
Objective
Scope
21. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Timebox
Work Breakdown Structure (WBS)
Solution Scope
Request For Proposal (RFP)
22. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Requirement(s) Defect
Interview
Product Backlog
Peer Review
23. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Attribute
Vision Statement (product vision statement)
Context Diagram
Data Model
24. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Entity-Relationship Diagram
Relationship
Decomposition
Use Case Diagram
25. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Methodology
Dialog Map
Quality Assurance
26. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Object Oriented Modeling
Product
Metadata
27. An analysis model describing the data structures and attributes needed by the system.
Business Process
Data Dictionary
Metric
Organizational Process Asset
28. An analysis model showing the life cycle of a data entity or class.
Quality Attributes
Attribute
State Diagram
Commercial-off-the-Shelf Software (COTS)
29. A stakeholder who uses products or services delivered by an organization.
Model(s)
Requirement(s) Attribute
Verified Requirements
Customer
30. A system trigger that is initiated by humans.
Business Event
Solution Requirement
Metadata
Gap Analysis
31. The product capabilities or things the product must do for its users.
Checklist
Cost Benefit Analysis
Functional Requirement(s)
Focus Group
32. Work carried out or on behalf of others.
Service
Elicitation
Class Model
Business Analysis Approach
33. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Baseline
Business Analyst
Supplier
Requirements Workshop
34. 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.
Horizontal Prototype
Requirement(s) Attribute
Domain
Solution Scope
35. 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.
End User
Class Model
Decision Tables
Vision Statement (product vision statement)
36. 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).
Repository
Commercial-off-the-Shelf Software (COTS)
Business Analysis Plan
Operational Support
37. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Business Need(s)
Developer
Walkthrough
Enterprise Architecture
38. Creating working software in multiple releases so the entire product is delivered in portions over time.
Business Analysis Approach
Incremental Delivery
Walkthrough
Span of Control
39. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Glossary
Business Analysis Communication Plan
Business Analysis Approach
Stakeholder
40. 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.
Implementation Subject Matter Expert (SME)
Requirements Management
Business Event
Project Charter
41. 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.
Event Response Table
Iteration
Commercial-off-the-Shelf Software (COTS)
Subject Matter Expert (SME)
42. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Root Cause Analysis
Relationship
Stakeholder List
Data Flow Diagram (DFD)
43. 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.
User
Requirement
Business Analysis Approach
Included Use Cases
44. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Metadata
Requirement
Technique
Unified Modeling Language (UML)
45. All materials used by groups within an organization to define tailor implement and maintain their processes.
User Acceptance Test
Attribute
Organizational Process Asset
Entity-Relationship Diagram
46. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Process Map
Incremental Delivery
Business Process
Temporal Event
47. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Cardinality
Decision Tables
Association
48. Any unique and verifiable work product or service that a party has agreed to deliver.
Scope
Deliverable
Commercial-off-the-Shelf Software (COTS)
Business Analysis
49. 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.
Secondary Actor
Organization
Elicitation
Supplier
50. Something that occurs to which an organizational unit system or process must respond.
Project
Survey
Indicator
Event