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 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.
Structured Walkthrough
Interoperability
Feature
Focus Group
2. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Business Constraint(s)
Quality Assurance
Validated Requirements
Repository
3. 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
Operational Support
Service
Technical Constraint(s)
4. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Process Map
Non-functional Requirement(s)
Sequence Diagram
Verification
5. An actor who participates in but does not initiate a use case.
Secondary Actor
Timebox
Requirements Management
Initiative
6. Software developed and sold for a particular market.
Commercial-off-the-Shelf Software (COTS)
Class Model
Enterprise Architecture
Requirements Management Plan
7. A practitioner of business analysis.
Requirements Trace Matrix
Requirements Risk Mitigation Strategy
Benchmarking
Business Analyst
8. The human and nonhuman roles that interact with the system.
Glossary
Stakeholder Analysis
Methodology
Actor(s)
9. A prototype that dives into the details of the interface functionality or both.
Force Field Analysis
Metadata
Vertical Prototype
Decision Tables
10. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Verification
Stakeholder Analysis
Decision Tree
Requirement(s) Defect
11. 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
Enterprise
Model(s)
Organization
Black Box Tests
12. 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
Business Architecture
Dialog Hierarchy
Organizational Unit
Prototype
13. 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
Methodology
Interoperability
Observation
14. A stakeholder who uses products or services delivered by an organization.
Model(s)
Stated Requirements
Customer
Solution
15. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Interview
Root Cause Analysis
Class
User Acceptance Test
16. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Document Analysis
User Acceptance Test
Capability
Competitive Analysis
17. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Data Flow Diagram (DFD)
Business Analysis Approach
Problem Statement
Business Requirements Document
18. A temporary endeavor undertaken to create a unique product service or result.
Focus Group
Data Flow Diagram (DFD)
Project
Root Cause Analysis
19. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Code
Entity-Relationship Diagram
Supplier
Business Rule(s)
20. A system trigger that is initiated by humans.
Business Event
Requirements Verification
Verified Requirements
Requirements Management
21. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Variance Analysis
Requirements Package
Requirement(s) Attribute
Evaluation
22. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Business Analysis
Customer
Structured Walkthrough
Metadata
23. A stakeholder person device or system that directly or indirectly accesses a system.
Structural Rule
Object Oriented Modeling
User
Swimlane
24. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Analyst
Optionality
Focus Group
Solution Requirement
25. A group of related tasks that support a key function of business analysis.
Commercial-off-the-Shelf Software (COTS)
Product Scope
Knowledge Area
Non-functional Requirement(s)
26. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Iteration
Assumption
Business Need(s)
Prototype
27. The set of capabilities a solution must deliver in order to meet the business need.
User Acceptance Test
User
Requirements Validation
Solution Scope
28. An assessment of the costs and benefits associated with a proposed initiative.
Business Case
Requirements Management
Relationship
Data Entity
29. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Horizontal Prototype
Requirements Management Plan
Risk
Service
30. 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.
Quality Assurance
Focus Group
Technique
Structural Rule
31. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
State Diagram
Work Product
Stakeholder Requirement
32. Software requirements that limit the options available to the system designer.
Non-functional Requirement(s)
Requirements Package
Process Model
Design Constraints
33. Limitations on the design of a solution that derive from the technology used in its implementation.
Deliverable
Baseline
Technical Constraint(s)
Prototype
34. A fixed period of time to accomplish a desired outcome.
Class
Risk
Constraint
Timebox
35. Any recognized association of people in the context of an organization or enterprise.
Stakeholder List
Organizational Unit
Scenario
Sequence Diagram
36. A solution or component of a solution that is the result of a project.
Project Charter
Vision Statement (product vision statement)
Feasibility Study
Product
37. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Change-driven Methodology
Lessons Learned Process
Peer Review
Structural Rule
38. The degree to which a set of inherent characteristics fulfills requirements.
Business Analysis Plan
Subject Matter Expert (SME)
Quality
Organizational Process Asset
39. 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
Requirements Allocation
Impact Analysis
Requirements Iteration
Unified Modeling Language (UML)
40. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.
Requirements Validation
Process Model
Stated Requirements
Business Analysis
41. A non-actionable directive that supports a business goal.
Business Policy
Code
External Interfaces
Requirements Trace Matrix
42. 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
Analyst
Variance Analysis
Survey
Class
43. 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.
Context Diagram
Glossary
Sponsor
Decision Tree
44. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Gap Analysis
Change Control Board (CCB)
Organizational Unit
Project Scope
45. An analysis model that illustrates the architecture of the system's user interface.
Quality Attributes
Regulator
Dialog Map
Requirements Management
46. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Root Cause Analysis
Requirements Risk Mitigation Strategy
Baseline
Product Backlog
47. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Implementation Subject Matter Expert (SME)
Assumption
Feature
Requirements Risk Mitigation Strategy
48. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Quality Attributes
Verification
Product Backlog
Desired Outcome
49. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Lessons Learned Process
Vision Statement (product vision statement)
Vertical Prototype
Association
50. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Data Model
Work Product
Solution Requirement
Horizontal Prototype