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 uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Request For Quote (RFQ)
Evolutionary Prototype
Risk
Decision Tree
2. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Sponsor
Requirements Allocation
Requirement(s) Defect
Defect
3. A state or condition the business must satisfy to reach its vision.
Organization
Business Goal
Solution
Organizational Unit
4. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Organizational Readiness Assessment
Capability
Incremental Delivery
Checklist
5. The set of capabilities a solution must deliver in order to meet the business need.
Solution Scope
Included Use Cases
Fishbone Diagram
Quality Assurance
6. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Verified Requirements
Feasibility Study
Root Cause Analysis
Requirements Allocation
7. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Constraint
Change-driven Methodology
Requirements Validation
Business Requirement
8. Metadata related to a requirement used to assist with requirements development and management.
Lessons Learned Process
Incremental Delivery
Requirement(s) Attribute
Knowledge Area
9. Creating working software in multiple releases so the entire product is delivered in portions over time.
Work Product
Business Domain Model
Incremental Delivery
Product Backlog
10. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Checklist
Peer Review
Opportunity Analysis
Timebox
11. A stakeholder person device or system that directly or indirectly accesses a system.
Business Analysis Approach
User
Commercial-off-the-Shelf Software (COTS)
Decision Analysis
12. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Scope Model
Validation
State Diagram
13. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Exploratory Prototype
Black Box Tests
Data Model
Observation
14. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Survey
Vision Statement (product vision statement)
Benchmarking
Data Model
15. 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.
Sequence Diagram
Service
Change Control Board (CCB)
Horizontal Prototype
16. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Temporal Event
Requirement(s) Defect
Business Requirement
Model(s)
17. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Scope Model
Problem Statement
Domain
Domain Subject Matter Expert (SME)
18. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Analyst
Entity-Relationship Diagram
Business Need(s)
Business Event
19. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Inspection
Product Backlog
Developer
Change Control Board (CCB)
20. An informal solicitation of proposals from vendors.
Constraint
Gap Analysis
Requirements Model
Request For Quote (RFQ)
21. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Problem Statement
Validated Requirements
Activity
Black Box Tests
22. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Commercial-off-the-Shelf Software (COTS)
Requirements Management Plan
Impact Analysis
Activity
23. 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.
Competitive Analysis
Verified Requirements
Root Cause Analysis
Focus Group
24. 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.
Glossary
Verified Requirements
Elicitation
Business Requirement
25. 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)
Solution Requirement
Model(s)
Repository
26. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Verification
Developer
Customer
27. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti
Business Requirement
Business Analyst
Class
Survey
28. 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
Business Analyst
Business Domain Model
Change Control Board (CCB)
Work Product
29. A model that defines the boundaries of a business domain or solution.
Brainstorming
Methodology
Organizational Unit
Scope Model
30. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Force Field Analysis
Software/Systems Requirements Specification
Cost Benefit Analysis
Repository
31. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Tester
Objective
Interoperability
Feasibility Study
32. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Change Control Board (CCB)
Force Field Analysis
Project Manager
Tester
33. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Requirement(s) Attribute
Solution Requirement
Use Case Diagram
Knowledge Area
34. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Business Analysis
Metric
Model(s)
Solution Requirement
35. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Context Diagram
User Acceptance Test
User Requirements Document
Stakeholder Analysis
36. Any effort undertaken with a defined goal or objective.
Enterprise
User
Focus Group
Initiative
37. An assessment of the costs and benefits associated with a proposed initiative.
Request For Proposal (RFP)
Business Case
Business Analyst
Design Constraints
38. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Process Model
Project Manager
Prioritization
Horizontal Prototype
39. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Brainstorming
Scope
Requirements Risk Mitigation Strategy
Data Model
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.
Project Charter
Business Process
Risk
Software/Systems Requirements Specification
41. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Plan-driven Methodology
Indicator
Requirements Iteration
Exploratory Prototype
42. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
System
Validated Requirements
Included Use Cases
Inspection
43. 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.
Product Backlog
Solution Scope
Business Analysis Communication Plan
Requirement(s) Attribute
44. 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
Stakeholder
Request For Proposal (RFP)
Object Oriented Modeling
Opportunity Analysis
45. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Model(s)
Entity-Relationship Diagram
Vision Statement (product vision statement)
Process Model
46. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Deliverable
Use Case
Work Product
Structured Walkthrough
47. A stakeholder who uses products or services delivered by an organization.
Requirement(s) Attribute
Customer
Return on Investment
Business Analysis Approach
48. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Requirements Signoff
Product
Work Breakdown Structure (WBS)
Gap Analysis
49. 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.
External Interfaces
Context Diagram
Focus Group
Timebox
50. The human and nonhuman roles that interact with the system.
Prototype
Requirement(s) Attribute
Association
Actor(s)