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 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
Request For Proposal (RFP)
Design Constraints
Business Requirement
Business Rule(s)
2. A system trigger that is initiated by time.
Requirements Management Tool
Temporal Event
Incremental Delivery
Object Oriented Modeling
3. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Software/Systems Requirements Specification
Quality Assurance
Variance Analysis
4. Any unique and verifiable work product or service that a party has agreed to deliver.
Verification
Business Case
Deliverable
State Diagram
5. 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
Requirements Management Plan
Requirements Management Tool
Metadata
6. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Code
Attribute
Stakeholder
Solution
7. A practitioner of business analysis.
Sponsor
Interface
Business Analyst
Validated Requirements
8. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Requirement
Requirement(s) Defect
Requirements Workshop
Opportunity Analysis
9. A prototype developed to explore or verify requirements.
Request For Proposal (RFP)
Sponsor
Requirements Iteration
Exploratory Prototype
10. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Interoperability
Stakeholder Analysis
Methodology
Checklist
11. A specific actionable testable directive that is under the control of the business and supports a business policy.
Solution Scope
Business Rule(s)
Requirements Verification
Data Entity
12. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Event
Indicator
Work Breakdown Structure (WBS)
Requirements Risk Mitigation Strategy
13. A prototype that dives into the details of the interface functionality or both.
User Acceptance Test
Scope Model
Business Constraint(s)
Vertical Prototype
14. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Cost Benefit Analysis
Risk
Walkthrough
Requirement
15. 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.
Context Diagram
Data Model
End User
Regulator
16. 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
Assumption
Prototype
Competitive Analysis
17. The number of employees a manger is directly (or indirectly) responsible for.
End User
Domain Subject Matter Expert (SME)
Data Entity
Span of Control
18. 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
Project
Sequence Diagram
Methodology
Request For Information (RFI)
19. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Survey
Fishbone Diagram
Subject Matter Expert (SME)
Sequence Diagram
20. 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.
Metric
Business Analysis Communication Plan
Quality Assurance
Span of Control
21. 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.
Stakeholder Analysis
Business Process
Competitive Analysis
Force Field Analysis
22. A temporary endeavor undertaken to create a unique product service or result.
Attribute
Project
Design Constraints
Requirements Traceability
23. 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.
Document Analysis
Use Case
Business Process
Software/Systems Requirements Specification
24. 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
Service
User Story
Structural Rule
Organizational Unit
25. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Stakeholder Analysis
Enterprise Architecture
Requirements Risk Mitigation Strategy
Optionality
26. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Data Entity
Observation
Software/Systems Requirements Specification
Scope
27. A model that defines the boundaries of a business domain or solution.
Root Cause Analysis
Vision Statement (product vision statement)
Variance Analysis
Scope Model
28. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Elicitation
Structured Walkthrough
Brainstorming
Use Case
29. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Analysis Approach
Stakeholder Analysis
Project
Decision Tree
30. 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.
Stated Requirements
User
Business Analysis Plan
Business Architecture
31. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
Requirements Workshop
Exploratory Prototype
Stakeholder Analysis
32. 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 Policy
Verified Requirements
Requirements Verification
Business Analyst
33. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Exploratory Prototype
Requirements Trace Matrix
Throw-away Prototype
Product
34. 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.
Scope Model
Data Flow Diagram (DFD)
Feature
Business Need(s)
35. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Objective
Scenario
Prioritization
36. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Project Charter
Quality Attributes
Requirements Signoff
37. A fixed period of time to accomplish a desired outcome.
Timebox
Organizational Unit
Requirement(s) Attribute
User Requirements Document
38. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Class
Product Backlog
Prioritization
Change-driven Methodology
39. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Quality
User Story
Stakeholder
Repository
40. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Iteration
Metadata
Sequence Diagram
41. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Impact Analysis
Requirements Package
Competitive Analysis
42. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Return on Investment
Requirements Trace Matrix
Work Product
Requirements Model
43. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Verification
Glossary
Class Model
Requirements Trace Matrix
44. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Capability
Evaluation
Feasibility Study
Brainstorming
45. 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.
Decision Analysis
Domain
Inspection
Stated Requirements
46. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Technique
Product Backlog
Temporal Event
Validation
47. A link between two elements or objects in a diagram.
Association
SWOT Analysis
Decision Analysis
Repository
48. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Tester
Walkthrough
Interoperability
Optionality
49. 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
Relationship
Vision Statement (product vision statement)
Unified Modeling Language (UML)
50. The human and nonhuman roles that interact with the system.
Business Process
Business Need(s)
Actor(s)
Incremental Delivery