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 description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.
Business Analysis Communication Plan
Assumption
Project Scope
Opportunity Analysis
2. The product capabilities or things the product must do for its users.
Requirements Model
Business Domain Model
Functional Requirement(s)
Activity
3. 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.
Horizontal Prototype
Focus Group
Stakeholder
Requirements Allocation
4. Metadata related to a requirement used to assist with requirements development and management.
Business Analyst
Requirement(s) Attribute
Quality
Stakeholder
5. 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
Metric
Project Manager
Business Need(s)
6. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Decision Tree
User Acceptance Test
Defect
State Diagram
7. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Feasibility Study
Requirements Verification
Decision Analysis
8. A measure of the profitability of a project or investment.
Return on Investment
Analyst
Business Analysis Communication Plan
Requirements Traceability
9. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Request For Quote (RFQ)
Survey
Sequence Diagram
Business Analyst
10. 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
Structural Rule
System
Interoperability
11. Any unique and verifiable work product or service that a party has agreed to deliver.
Process Map
Technique
Deliverable
Validation
12. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
State Diagram
Quality Attributes
Swimlane
Decision Analysis
13. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Use Case Diagram
Optionality
Business Process
Constraint
14. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Domain Subject Matter Expert (SME)
Service
Feature
Technique
15. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Transition Requirement(s)
Interface
Risk
Sequence Diagram
16. Ability of systems to communicate by exchanging data or services.
Business Event
Business Rule(s)
Interoperability
Regulator
17. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Fishbone Diagram
Data Flow Diagram (DFD)
Object Oriented Modeling
Incremental Delivery
18. 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.
Optionality
Business Event
Use Case
Service
19. A model that defines the boundaries of a business domain or solution.
Business Rule(s)
Scope Model
Monitoring
Object Oriented Modeling
20. The features and functions that characterize a product service or result.
Requirement
Product Scope
Data Model
Requirements Workshop
21. 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.
Indicator
Requirement
Knowledge Area
Objective
22. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Operational Support
Temporal Event
Transition Requirement(s)
23. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
System
Requirements Trace Matrix
Impact Analysis
Business Requirement
24. 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.
Process Map
Requirements Workshop
Impact Analysis
Functional Requirement(s)
25. 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.
Requirements Management Plan
Competitive Analysis
Stakeholder Analysis
Analyst
26. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Span of Control
Service
Indicator
27. 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.
Document Analysis
Sequence Diagram
Walkthrough
User Story
28. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Quality Attributes
Lessons Learned Process
Gap Analysis
Focus Group
29. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Iteration
Relationship Map
Stated Requirements
Use Case
30. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Cost Benefit Analysis
Relationship
Process Model
Stated Requirements
31. A prototype that dives into the details of the interface functionality or both.
Change-driven Methodology
Observation
Dialog Hierarchy
Vertical Prototype
32. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Black Box Tests
Vertical Prototype
Subject Matter Expert (SME)
Analyst
33. Software requirements that limit the options available to the system designer.
Secondary Actor
Activity
Opportunity Analysis
Design Constraints
34. A system trigger that is initiated by time.
Business Constraint(s)
Requirements Allocation
Business Case
Temporal Event
35. The set of capabilities a solution must deliver in order to meet the business need.
Solution Scope
Quality Assurance
Secondary Actor
Technique
36. 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
Business Analysis
Requirements Verification
Benchmarking
User Requirements Document
37. The human and nonhuman roles that interact with the system.
Actor(s)
Vision Statement (product vision statement)
Root Cause Analysis
Context Diagram
38. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
User
Requirements Management
Structured Walkthrough
Use Case Diagram
39. 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.
Solution Requirement
Product
Business Need(s)
Requirements Package
40. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Timebox
Constraint
Benchmarking
Work Product
41. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
User Story
Operational Support
Requirements Model
Business Process
42. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Requirements Verification
Inspection
Project Scope
Data Entity
43. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Glossary
Prioritization
Included Use Cases
Variance Analysis
44. A structured examination of an identified problem to understand the underlying causes.
Subject Matter Expert (SME)
State Diagram
Root Cause Analysis
Class Model
45. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Activity Diagram
Object Oriented Modeling
Scope Model
User Requirements Document
46. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
External Interfaces
Baseline
Request For Proposal (RFP)
Implementation Subject Matter Expert (SME)
47. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Evolutionary Prototype
Solution
Interview
Enterprise
48. A stakeholder who uses products or services delivered by an organization.
Organizational Unit
Requirement
Customer
Business Requirements Document
49. A fixed period of time to accomplish a desired outcome.
Project
Walkthrough
Timebox
Domain Subject Matter Expert (SME)
50. A link between two elements or objects in a diagram.
Requirements Allocation
Association
Organizational Unit
Monitoring