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 practitioner of business analysis.
Tester
Solution
Constraint
Business Analyst
2. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Class Model
Scope
Indicator
Repository
3. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Cardinality
Stated Requirements
Business Analysis Communication Plan
4. Ability of systems to communicate by exchanging data or services.
Supplier
Requirements Iteration
Interoperability
Activity
5. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Incremental Delivery
Business Domain Model
Baseline
Included Use Cases
6. The area covered by a particular activity or topic of interest.
Capability
Data Dictionary
Scope
Request For Proposal (RFP)
7. 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.
Regulator
Business Analysis Communication Plan
Business Analysis
Association
8. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Operational Support
Requirements Model
Operative Rule(s)
Transition Requirement(s)
9. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Organization Modeling
Problem Statement
Solution
Sequence Diagram
10. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Subject Matter Expert (SME)
Constraint
End User
Indicator
11. 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.
Requirements Workshop
Business Constraint(s)
Black Box Tests
Cardinality
12. A fixed period of time to accomplish a desired outcome.
Feasibility Study
Service
User Acceptance Test
Timebox
13. A shared boundary between any two persons and/or systems through which information is communicated.
Cardinality
Inspection
Interface
Horizontal Prototype
14. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Code
Peer Review
Black Box Tests
Organizational Readiness Assessment
15. 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.
Work Product
Enterprise
Model(s)
Business Analysis Plan
16. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Change-driven Methodology
Unified Modeling Language (UML)
Timebox
Scope Model
17. A group of related tasks that support a key function of business analysis.
Knowledge Area
Throw-away Prototype
Process Model
Business Requirement
18. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Object Oriented Modeling
Association
Requirements Signoff
Organization Modeling
19. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Product Backlog
Document Analysis
Requirements Allocation
Cost Benefit Analysis
20. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Validated Requirements
Decision Analysis
Assumption
21. 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
Request For Information (RFI)
Subject Matter Expert (SME)
Business Policy
Stakeholder Analysis
22. Software requirements that limit the options available to the system designer.
Activity
Model(s)
Data Dictionary
Design Constraints
23. The product capabilities or things the product must do for its users.
Monitoring
Functional Requirement(s)
Evolutionary Prototype
Objective
24. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Stakeholder List
Business Analyst
Actor(s)
User Story
25. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Class
Requirement(s) Defect
Stakeholder Analysis
Relationship
26. An analysis model that shows user interface dialogs arranged as hierarchies.
Business Architecture
Product
Dialog Hierarchy
Transition Requirement(s)
27. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
Enterprise
System
Quality
Software/Systems Requirements Specification
28. Software developed and sold for a particular market.
Checklist
Requirements Management
Organizational Readiness Assessment
Commercial-off-the-Shelf Software (COTS)
29. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Vision Statement (product vision statement)
Software/Systems Requirements Specification
Defect
Customer
30. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Business Constraint(s)
User Acceptance Test
Desired Outcome
Plan-driven Methodology
31. A temporary endeavor undertaken to create a unique product service or result.
Process Model
Cost Benefit Analysis
Activity Diagram
Project
32. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Requirements Allocation
Repository
Requirements Model
Cost Benefit Analysis
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
Work Breakdown Structure (WBS)
Span of Control
Business Constraint(s)
Project
34. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Use Case
Project Scope
Risk
Data Flow Diagram (DFD)
35. 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.
Horizontal Prototype
Business Policy
Knowledge Area
Initiative
36. 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.
User Story
Requirements Package
Business Goal
Feature
37. 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.
Project Charter
Solution
Request For Quote (RFQ)
Event Response Table
38. 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.
Decision Analysis
Class
Organizational Unit
Context Diagram
39. A description of the requirements management process.
Business Analysis
Enterprise Architecture
Requirements Management Plan
Business Analysis Approach
40. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Decomposition
Lessons Learned Process
Business Constraint(s)
41. A stakeholder who uses products or services delivered by an organization.
Monitoring
Customer
Methodology
Solution Requirement
42. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
Vision Statement (product vision statement)
Class Model
Scenario
Requirements Iteration
43. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Business Architecture
Solution Scope
Vision Statement (product vision statement)
Implementation Subject Matter Expert (SME)
44. Creating working software in multiple releases so the entire product is delivered in portions over time.
Inspection
Force Field Analysis
Baseline
Incremental Delivery
45. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Validation
Change Control Board (CCB)
Actor(s)
46. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
Actor(s)
End User
Class
Use Case Diagram
47. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Event Response Table
Business Process
Business Requirement
Brainstorming
48. 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.
Requirements Traceability
Walkthrough
Variance Analysis
Prioritization
49. 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.
Analyst
Project Scope
Business Analysis
Fishbone Diagram
50. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Prototype
Swimlane
Business Need(s)
Desired Outcome