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. Something that occurs to which an organizational unit system or process must respond.
Checklist
Subject Matter Expert (SME)
Requirements Verification
Event
2. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Project Manager
Verification
Black Box Tests
Opportunity Analysis
3. A description of the requirements management process.
Functional Requirement(s)
Requirements Management Plan
Developer
Force Field Analysis
4. A practitioner of business analysis.
Root Cause Analysis
Business Analyst
Requirements Package
System
5. 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
Request For Proposal (RFP)
Feature
Actor(s)
Change-driven Methodology
6. A group of related tasks that support a key function of business analysis.
Stated Requirements
Decision Tables
Business Requirement
Knowledge Area
7. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
User
Swimlane
Validation
Requirements Model
8. A stakeholder who provides products or services to an organization.
Supplier
Class
Requirements Trace Matrix
Request For Quote (RFQ)
9. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Business Analysis Plan
Brainstorming
Problem Statement
Change Control Board (CCB)
10. A non-actionable directive that supports a business goal.
Scope Model
Product Scope
Data Flow Diagram (DFD)
Business Policy
11. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Model(s)
Deliverable
Decision Tree
Relationship
12. All materials used by groups within an organization to define tailor implement and maintain their processes.
Gap Analysis
Organizational Process Asset
Business Goal
Actor(s)
13. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Assumption
Technical Constraint(s)
End User
Indicator
14. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Supplier
Organization
Document Analysis
Unified Modeling Language (UML)
15. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Product Backlog
Assumption
Black Box Tests
Use Case Diagram
16. A model that defines the boundaries of a business domain or solution.
Enterprise
User
Requirements Management
Scope Model
17. A function of an organization that enables it to achieve a business goal or objective.
Work Breakdown Structure (WBS)
Actor(s)
Scenario
Capability
18. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Requirements Management
Root Cause Analysis
Technique
Business Goal
19. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
User Requirements Document
Organizational Readiness Assessment
Regulator
Business Event
20. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Quality Attributes
Gap Analysis
Data Entity
Subject Matter Expert (SME)
21. The features and functions that characterize a product service or result.
Product Backlog
Knowledge Area
Project Charter
Product Scope
22. 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.
Scope Model
Force Field Analysis
Metric
User Acceptance Test
23. 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.
State Diagram
Plan-driven Methodology
Solution
Product Scope
24. Any unique and verifiable work product or service that a party has agreed to deliver.
Requirement
Impact Analysis
Functional Requirement(s)
Deliverable
25. A system trigger that is initiated by humans.
Technical Constraint(s)
Organizational Unit
Lessons Learned Process
Business Event
26. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
Feasibility Study
Domain
Evaluation
Business Process
27. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Change-driven Methodology
Requirements Verification
Data Flow Diagram (DFD)
28. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Business Event
Product Backlog
Variance Analysis
29. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Relationship
Enterprise Architecture
Peer Review
Use Case
30. The process of examining new business opportunities to improve organizational performance.
Domain Subject Matter Expert (SME)
Gap Analysis
Opportunity Analysis
Assumption
31. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various
Request For Proposal (RFP)
Object Oriented Modeling
Context Diagram
Stakeholder Requirement
32. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Requirements Risk Mitigation Strategy
Event
Risk
Iteration
33. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Organizational Unit
Business Requirement
Unified Modeling Language (UML)
Requirements Validation
34. A group or person who has interests that may be affected by an initiative or influence over it.
Regulator
Competitive Analysis
Stakeholder
Optionality
35. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Metric
Knowledge Area
Risk
Competitive Analysis
36. The area covered by a particular activity or topic of interest.
Project
Relationship Map
Assumption
Scope
37. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Inspection
Functional Requirement(s)
Business Analyst
Operative Rule(s)
38. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Business Requirements Document
Temporal Event
Objective
Fishbone Diagram
39. 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
Scope
Return on Investment
Requirement(s) Attribute
40. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Activity Diagram
Requirement(s) Defect
Relationship Map
User Acceptance Test
41. Software requirements that limit the options available to the system designer.
Developer
User Acceptance Test
Business Event
Design Constraints
42. Software developed and sold for a particular market.
Service
Developer
Decision Tree
Commercial-off-the-Shelf Software (COTS)
43. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Prototype
Software/Systems Requirements Specification
Verified Requirements
Requirements Management Tool
44. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Context Diagram
Repository
Throw-away Prototype
Inspection
45. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Domain Subject Matter Expert (SME)
Stakeholder
Peer Review
Knowledge Area
46. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Requirements Risk Mitigation Strategy
Scope
Focus Group
SWOT Analysis
47. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Event
Desired Outcome
Document Analysis
Business Analysis Approach
48. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Throw-away Prototype
Scenario
Baseline
Solution
49. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Requirements Management Tool
Project Charter
Developer
Cost Benefit Analysis
50. A use case composed of a common set of steps used by multiple use cases.
Product Backlog
Sequence Diagram
Included Use Cases
Dialog Hierarchy