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 type of diagram that shows objects participating in interactions and the messages exchanged between them.
Assumption
Black Box Tests
Sequence Diagram
Problem Statement
2. 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
Competitive Analysis
Business Analysis Communication Plan
Subject Matter Expert (SME)
3. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
User Requirements Document
Regulator
Black Box Tests
Work Product
4. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.
Secondary Actor
Business Requirements Document
User Acceptance Test
Walkthrough
5. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Organizational Process Asset
Decision Tables
Stakeholder Requirement
Swimlane
6. A prototype that dives into the details of the interface functionality or both.
Temporal Event
Stakeholder List
Technical Constraint(s)
Vertical Prototype
7. Metadata related to a requirement used to assist with requirements development and management.
Stakeholder Analysis
Business Analyst
Requirement(s) Attribute
End User
8. 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
Service
Requirements Iteration
Timebox
Metadata
9. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.
Verification
Dialog Hierarchy
Product
Organization
10. A prototype that is continuously modified and updated in response to feedback from users.
Assumption
Evolutionary Prototype
Prioritization
Baseline
11. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Evolutionary Prototype
Root Cause Analysis
Dialog Map
Requirements Package
12. Any unique and verifiable work product or service that a party has agreed to deliver.
Deliverable
Scope Model
Requirements Traceability
Force Field Analysis
13. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Verified Requirements
Requirements Validation
Business Goal
Cost Benefit Analysis
14. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Evaluation
Solution Requirement
External Interfaces
15. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Requirements Management
Scope Model
Technical Constraint(s)
16. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Stakeholder
Technical Constraint(s)
End User
Requirements Model
17. A data element with a specified data type that describes information associated with a concept or entity.
Vision Statement (product vision statement)
Enterprise
Attribute
Peer Review
18. 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
Exploratory Prototype
Requirements Model
Object Oriented Modeling
Baseline
19. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Business Requirement
Solution Requirement
Solution Scope
Variance Analysis
20. A solution or component of a solution that is the result of a project.
Business Analysis Communication Plan
Requirements Model
Cost Benefit Analysis
Product
21. 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.
Interoperability
Requirements Validation
User Acceptance Test
Attribute
22. A fixed period of time to accomplish a desired outcome.
Timebox
Work Breakdown Structure (WBS)
Domain Subject Matter Expert (SME)
Requirements Iteration
23. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Metric
Business Goal
Optionality
Methodology
24. 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.
Walkthrough
Exploratory Prototype
Project Charter
Plan-driven Methodology
25. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Survey
User
Product
Lessons Learned Process
26. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Activity
Validated Requirements
Change Control Board (CCB)
27. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Unified Modeling Language (UML)
Object Oriented Modeling
Scenario
Vertical Prototype
28. A stakeholder who uses products or services delivered by an organization.
Scope
Customer
Business Goal
Business Analysis
29. 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.
Optionality
Analyst
Operative Rule(s)
Use Case
30. 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.
Monitoring
Business Analysis Communication Plan
Business Case
Business Requirement
31. 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.
Requirements Management
Elicitation
State Diagram
Horizontal Prototype
32. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Process Map
Gap Analysis
Opportunity Analysis
Decision Analysis
33. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Verified Requirements
Business Requirements Document
Iteration
Root Cause Analysis
34. An actor who participates in but does not initiate a use case.
Verified Requirements
Inspection
Secondary Actor
Cost Benefit Analysis
35. A group or person who has interests that may be affected by an initiative or influence over it.
User Requirements Document
Stakeholder
Requirement(s) Attribute
Validation
36. 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.
Work Breakdown Structure (WBS)
Class
Change Control Board (CCB)
Requirements Validation
37. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Gap Analysis
Exploratory Prototype
Stakeholder Analysis
Feasibility Study
38. A non-actionable directive that supports a business goal.
Requirements Management Tool
Business Policy
Requirements Traceability
Stakeholder Analysis
39. A system of programming statements symbols and rules used to represent instructions to a computer.
Association
User Story
Event
Code
40. 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
Event Response Table
Class
Opportunity Analysis
Requirement(s) Defect
41. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Dialog Map
Functional Requirement(s)
Repository
Object Oriented Modeling
42. 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.
Project Charter
Feasibility Study
Solution
Solution Scope
43. 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.
Business Analysis Plan
Scope
Capability
Vision Statement (product vision statement)
44. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Return on Investment
Solution Scope
User Acceptance Test
45. Information that is used to understand the context and validity of information recorded in a system.
Quality
Evaluation
Sponsor
Metadata
46. A stakeholder who provides products or services to an organization.
Association
Data Flow Diagram (DFD)
Software/Systems Requirements Specification
Supplier
47. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Cost Benefit Analysis
Organization
Business Analysis Approach
Supplier
48. A state or condition the business must satisfy to reach its vision.
Business Goal
Evolutionary Prototype
Fishbone Diagram
Data Flow Diagram (DFD)
49. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Business Architecture
External Interfaces
Business Domain Model
Subject Matter Expert (SME)
50. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Technical Constraint(s)
Request For Information (RFI)
Regulator
Observation