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 fixed period of time to accomplish a desired outcome.
Timebox
Project
Requirements Management
Verified Requirements
2. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Context Diagram
Organization Modeling
Brainstorming
Data Dictionary
3. A system trigger that is initiated by humans.
Business Event
Initiative
Sponsor
Solution
4. 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.
Solution Requirement
Competitive Analysis
Non-functional Requirement(s)
Throw-away Prototype
5. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Regulator
Context Diagram
Constraint
User Acceptance Test
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.
Requirements Traceability
Feasibility Study
User Story
Organization
7. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Customer
Organizational Readiness Assessment
Product
Code
8. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Problem Statement
Requirements Traceability
Structural Rule
Defect
9. 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.
Organization
Requirements Workshop
Return on Investment
Requirements Traceability
10. A model that defines the boundaries of a business domain or solution.
Scope Model
Span of Control
Sponsor
Solution
11. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Use Case
Enterprise
Unified Modeling Language (UML)
Enterprise Architecture
12. 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
Defect
Technique
Commercial-off-the-Shelf Software (COTS)
13. A stakeholder who uses products or services delivered by an organization.
Subject Matter Expert (SME)
Focus Group
Repository
Customer
14. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Data Entity
Document Analysis
Return on Investment
Swimlane
15. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Initiative
Repository
Feasibility Study
16. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
User Story
Model(s)
Lessons Learned Process
Enterprise
17. 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
Change Control Board (CCB)
Data Flow Diagram (DFD)
Request For Proposal (RFP)
Verified Requirements
18. 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.
Unified Modeling Language (UML)
Business Analysis Communication Plan
Business Analysis Plan
Non-functional Requirement(s)
19. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Quality Assurance
Analyst
Indicator
Requirements Management Tool
20. 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
Request For Quote (RFQ)
Business Domain Model
User Acceptance Test
Process Model
21. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Enterprise
Optionality
Organization
Context Diagram
22. A practitioner of business analysis.
Business Analyst
Interview
Benchmarking
Developer
23. 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.
Non-functional Requirement(s)
Business Analysis
Relationship Map
Business Need(s)
24. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Span of Control
Requirements Iteration
Change-driven Methodology
25. 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.
Requirement
Project Scope
Fishbone Diagram
Elicitation
26. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Project Manager
Observation
Requirement
Lessons Learned Process
27. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Model(s)
Business Analysis Communication Plan
Evaluation
28. 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
Association
Request For Information (RFI)
Decision Tree
Horizontal Prototype
29. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Request For Proposal (RFP)
Data Entity
Requirements Package
Domain
30. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Initiative
Baseline
Decision Tree
Implementation Subject Matter Expert (SME)
31. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Requirements Management Tool
Document Analysis
Quality
Problem Statement
32. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Sequence Diagram
Variance Analysis
Class Model
Change Control Board (CCB)
33. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Requirement(s) Defect
Incremental Delivery
Business Constraint(s)
Tester
34. A system trigger that is initiated by time.
Object Oriented Modeling
Opportunity Analysis
Temporal Event
Stakeholder Analysis
35. The process of examining new business opportunities to improve organizational performance.
Inspection
Dialog Map
Opportunity Analysis
Walkthrough
36. 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.
Attribute
Competitive Analysis
Requirement(s) Attribute
Business Domain Model
37. 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
Class Model
Return on Investment
Problem Statement
Business Architecture
38. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Evolutionary Prototype
Risk
Stakeholder Analysis
Impact Analysis
39. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
User Acceptance Test
Data Entity
Business Analyst
Actor(s)
40. 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).
Organizational Unit
Operational Support
Request For Proposal (RFP)
User Acceptance Test
41. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Indicator
Exploratory Prototype
Root Cause Analysis
Project Manager
42. The human and nonhuman roles that interact with the system.
Data Model
Prioritization
Actor(s)
Evolutionary Prototype
43. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Data Flow Diagram (DFD)
Assumption
Project Charter
Glossary
44. A person with specific expertise in an area or domain under investigation.
Domain Subject Matter Expert (SME)
Verified Requirements
Context Diagram
Assumption
45. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Business Analysis Approach
Monitoring
Peer Review
Commercial-off-the-Shelf Software (COTS)
46. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Object Oriented Modeling
Brainstorming
Relationship Map
Verification
47. The problem area undergoing analysis.
User
Domain Subject Matter Expert (SME)
Domain
Root Cause Analysis
48. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Code
Requirements Allocation
Association
Change Control Board (CCB)
49. A stakeholder who provides products or services to an organization.
Decomposition
Initiative
Class Model
Supplier
50. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Requirements Model
Desired Outcome
Organization Modeling
Timebox