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 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.
Use Case
Work Product
Interview
Baseline
2. 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
Organization
Interoperability
Temporal Event
3. 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
Checklist
Business Process
Assumption
4. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Feasibility Study
Supplier
Activity Diagram
Structural Rule
5. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Service
User
Business Need(s)
6. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Developer
User Acceptance Test
Force Field Analysis
Code
7. 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
Included Use Cases
Request For Proposal (RFP)
Fishbone Diagram
Requirements Risk Mitigation Strategy
8. Creating working software in multiple releases so the entire product is delivered in portions over time.
Iteration
Feature
Activity
Incremental Delivery
9. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Sequence Diagram
Operative Rule(s)
Data Entity
Black Box Tests
10. A system trigger that is initiated by time.
Activity Diagram
Checklist
Temporal Event
Prototype
11. A model that defines the boundaries of a business domain or solution.
Domain
External Interfaces
Scope Model
Design Constraints
12. 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.
Scope
Use Case Diagram
Stakeholder Requirement
Business Analysis
13. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Sponsor
Data Flow Diagram (DFD)
Requirements Iteration
Business Case
14. A prototype that dives into the details of the interface functionality or both.
Context Diagram
Non-functional Requirement(s)
Vertical Prototype
Developer
15. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Monitoring
Requirements Validation
Tester
Dialog Hierarchy
16. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Swimlane
Optionality
Class Model
Business Rule(s)
17. 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.
Validated Requirements
User Story
Cost Benefit Analysis
Quality
18. A stakeholder who provides products or services to an organization.
Metadata
Business Analysis Communication Plan
Supplier
Iteration
19. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Regulator
Request For Information (RFI)
Sequence Diagram
Activity
20. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Verification
Requirements Signoff
Feature
Actor(s)
21. Any unique and verifiable work product or service that a party has agreed to deliver.
Requirement
Repository
User Requirements Document
Deliverable
22. 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
Product Scope
Root Cause Analysis
Business Process
Use Case Diagram
23. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Design Constraints
Stakeholder List
Requirements Risk Mitigation Strategy
Project Manager
24. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Opportunity Analysis
Interface
Operative Rule(s)
Request For Quote (RFQ)
25. A fixed period of time to accomplish a desired outcome.
Indicator
Feasibility Study
Timebox
Decision Tables
26. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Decision Tree
Throw-away Prototype
Assumption
SWOT Analysis
27. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Dialog Map
Evolutionary Prototype
Request For Information (RFI)
28. 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
Capability
Requirements Management Plan
Business Goal
29. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
State Diagram
Indicator
Work Product
Requirements Traceability
30. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Business Process
Validated Requirements
Sequence Diagram
31. 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.
Baseline
SWOT Analysis
Requirements Workshop
Enterprise
32. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Business Analysis Communication Plan
Requirements Signoff
Requirements Management
Technical Constraint(s)
33. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Object Oriented Modeling
Deliverable
Glossary
34. A structured examination of an identified problem to understand the underlying causes.
Domain Subject Matter Expert (SME)
Enterprise Architecture
Risk
Root Cause Analysis
35. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Incremental Delivery
Solution
Monitoring
Operational Support
36. A state or condition the business must satisfy to reach its vision.
Evaluation
Activity
Business Goal
Transition Requirement(s)
37. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Organization
Data Entity
Interview
Validation
38. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User Requirements Document
Class Model
Defect
Plan-driven Methodology
39. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Use Case Diagram
Business Analysis
Project Charter
Impact Analysis
40. An informal solicitation of proposals from vendors.
Service
Quality Attributes
Requirements Risk Mitigation Strategy
Request For Quote (RFQ)
41. 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.
Metadata
Design Constraints
User Acceptance Test
Verification
42. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Scope Model
Throw-away Prototype
User
Requirements Risk Mitigation Strategy
43. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Brainstorming
Request For Proposal (RFP)
Competitive Analysis
44. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Initiative
Subject Matter Expert (SME)
User Story
Vertical Prototype
45. 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).
User Acceptance Test
Decision Tree
Operational Support
Technical Constraint(s)
46. 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
Process Map
Walkthrough
Requirements Package
Business Domain Model
47. An assessment of the costs and benefits associated with a proposed initiative.
Technique
Business Case
Plan-driven Methodology
Requirements Iteration
48. A group or person who has interests that may be affected by an initiative or influence over it.
Supplier
Stakeholder
Requirement
User Requirements Document
49. A unit of work performed as part of an initiative or process.
Survey
Force Field Analysis
Activity
Data Entity
50. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Business Analysis Plan
Requirements Iteration
System
Stakeholder Analysis