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 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.
Incremental Delivery
Survey
Checklist
Competitive Analysis
2. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Business Analyst
Survey
Structural Rule
Assumption
3. Something that occurs to which an organizational unit system or process must respond.
Decision Tables
Event
Project Manager
Opportunity Analysis
4. Any effort undertaken with a defined goal or objective.
Throw-away Prototype
Initiative
Project
Association
5. A unit of work performed as part of an initiative or process.
Sponsor
Project Charter
Activity
Risk
6. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Relationship Map
Initiative
Sequence Diagram
Business Requirements Document
7. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Stakeholder
Process Map
Peer Review
Requirement(s) Defect
8. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Quality Assurance
Problem Statement
Sequence Diagram
Requirements Validation
9. A description of the requirements management process.
Design Constraints
Quality
Organizational Readiness Assessment
Requirements Management Plan
10. A state or condition the business must satisfy to reach its vision.
Observation
Lessons Learned Process
Business Goal
Sequence Diagram
11. 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.
SWOT Analysis
Stated Requirements
Requirements Traceability
Tester
12. A use case composed of a common set of steps used by multiple use cases.
End User
Elicitation
Decision Tables
Included Use Cases
13. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Desired Outcome
Business Event
Glossary
Monitoring
14. A group of related tasks that support a key function of business analysis.
Competitive Analysis
Business Analysis Plan
Stakeholder List
Knowledge Area
15. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Included Use Cases
Model(s)
Iteration
16. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Requirements Package
Request For Proposal (RFP)
Survey
Requirements Risk Mitigation Strategy
17. Work carried out or on behalf of others.
Metric
Knowledge Area
Incremental Delivery
Service
18. 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.
Requirements Traceability
Business Analysis Plan
Objective
Enterprise Architecture
19. A stakeholder person device or system that directly or indirectly accesses a system.
Unified Modeling Language (UML)
Transition Requirement(s)
User
Business Constraint(s)
20. A type of data model that depicts information groups as classes.
Requirements Verification
Class Model
Sequence Diagram
Request For Information (RFI)
21. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Verification
Requirements Model
Root Cause Analysis
System
22. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Structured Walkthrough
Incremental Delivery
Initiative
Enterprise Architecture
23. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
SWOT Analysis
Lessons Learned Process
Methodology
Fishbone Diagram
24. 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
Class
Cardinality
Knowledge Area
Requirements Iteration
25. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Feature
Business Analysis Plan
Timebox
Requirements Traceability
26. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Feasibility Study
Decomposition
Activity
Verification
27. A measure of the profitability of a project or investment.
Return on Investment
Project Manager
Tester
Business Analysis
28. A system trigger that is initiated by time.
Temporal Event
Activity
Event
Survey
29. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Validation
Quality
Work Product
30. A stakeholder who uses products or services delivered by an organization.
Customer
Metadata
Timebox
Technique
31. 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
Operative Rule(s)
Requirements Trace Matrix
Tester
Business Domain Model
32. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Plan-driven Methodology
Domain Subject Matter Expert (SME)
Quality Attributes
Implementation Subject Matter Expert (SME)
33. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Design Constraints
Monitoring
Domain Subject Matter Expert (SME)
Cost Benefit Analysis
34. Formal approval of a set of requirements by a sponsor or other decision maker.
Structured Walkthrough
Requirements Signoff
Gap Analysis
Business Analysis Communication Plan
35. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Organizational Process Asset
Inspection
Structural Rule
Cost Benefit Analysis
36. A prototype developed to explore or verify requirements.
Black Box Tests
Exploratory Prototype
Structural Rule
Secondary Actor
37. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Evaluation
Peer Review
Problem Statement
End User
38. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Operative Rule(s)
Brainstorming
Swimlane
Methodology
39. A practitioner of business analysis.
Stated Requirements
Request For Information (RFI)
Software/Systems Requirements Specification
Business Analyst
40. 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.
Repository
Interview
Elicitation
Actor(s)
41. An informal solicitation of proposals from vendors.
Requirements Verification
Process Model
Request For Quote (RFQ)
User
42. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Vision Statement (product vision statement)
Assumption
Operative Rule(s)
Requirements Model
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.
Requirement(s) Attribute
Solution Requirement
Commercial-off-the-Shelf Software (COTS)
Business Analysis Communication Plan
44. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Class
Business Constraint(s)
Document Analysis
Quality Attributes
45. Software developed and sold for a particular market.
Structural Rule
Commercial-off-the-Shelf Software (COTS)
Class Model
Quality Attributes
46. 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
Throw-away Prototype
Iteration
Request For Proposal (RFP)
Repository
47. 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
Lessons Learned Process
Organizational Process Asset
System
Supplier
48. The area covered by a particular activity or topic of interest.
Knowledge Area
Entity-Relationship Diagram
Scope
Enterprise Architecture
49. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Requirements Workshop
Enterprise
Project Manager
Methodology
50. 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
Objective
Technique
Organization
Business Architecture