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 point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
External Interfaces
Baseline
Business Need(s)
Data Entity
2. 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
Business Constraint(s)
Change-driven Methodology
Lessons Learned Process
Project Scope
3. 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.
Organization Modeling
Evolutionary Prototype
Requirements Traceability
Project Manager
4. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Requirements Model
Model(s)
Business Analysis Communication Plan
Gap Analysis
5. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Stakeholder
Assumption
Feature
Impact Analysis
6. 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.
Evolutionary Prototype
Decision Analysis
Use Case
External Interfaces
7. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Requirements Traceability
Indicator
Evolutionary Prototype
Stated Requirements
8. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Event Response Table
Project Scope
Business Domain Model
9. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Context Diagram
Interface
Impact Analysis
Cardinality
10. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
State Diagram
Dialog Hierarchy
Project Manager
Interface
11. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Dialog Map
Focus Group
Throw-away Prototype
Organization Modeling
12. 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
Competitive Analysis
Request For Proposal (RFP)
Solution Requirement
Horizontal Prototype
13. A fixed period of time to accomplish a desired outcome.
Enterprise
Timebox
Decomposition
Structured Walkthrough
14. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
User
Scope Model
Data Model
Quality Assurance
15. An analysis model showing the life cycle of a data entity or class.
Quality
Commercial-off-the-Shelf Software (COTS)
Feasibility Study
State Diagram
16. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
Implementation Subject Matter Expert (SME)
Initiative
Tester
Requirements Risk Mitigation Strategy
17. An informal solicitation of proposals from vendors.
Work Breakdown Structure (WBS)
Request For Quote (RFQ)
Data Model
Quality Attributes
18. Software developed and sold for a particular market.
User
Commercial-off-the-Shelf Software (COTS)
Plan-driven Methodology
Data Entity
19. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Elicitation
Product Scope
User Requirements Document
Attribute
20. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Requirements Risk Mitigation Strategy
Requirements Allocation
Design Constraints
Peer Review
21. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Requirements Validation
Work Product
Incremental Delivery
Solution
22. The problem area undergoing analysis.
Supplier
Domain
Design Constraints
Context Diagram
23. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Evolutionary Prototype
Entity-Relationship Diagram
Project
Requirement
24. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Process Model
Work Product
Relationship
Data Model
25. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Verified Requirements
Non-functional Requirement(s)
Glossary
User Story
26. 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
Object Oriented Modeling
Observation
Problem Statement
Request For Proposal (RFP)
27. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Swimlane
Assumption
Inspection
Technical Constraint(s)
28. A group of related tasks that support a key function of business analysis.
User
Model(s)
Decomposition
Knowledge Area
29. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Non-functional Requirement(s)
Process Model
Objective
Project Manager
30. 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.
End User
Relationship Map
Walkthrough
Data Dictionary
31. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Assumption
Metric
Document Analysis
Dialog Map
32. A shared boundary between any two persons and/or systems through which information is communicated.
Prototype
SWOT Analysis
Indicator
Interface
33. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Use Case Diagram
End User
Class
Tester
34. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Checklist
Desired Outcome
Organizational Readiness Assessment
Business Event
35. A temporary endeavor undertaken to create a unique product service or result.
Project
Tester
Process Map
Data Flow Diagram (DFD)
36. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Temporal Event
System
Project Manager
Stakeholder Analysis
37. A prototype that dives into the details of the interface functionality or both.
Product Scope
Glossary
Work Product
Vertical Prototype
38. 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
Class
Business Domain Model
Metric
Repository
39. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
External Interfaces
Regulator
Software/Systems Requirements Specification
Organizational Unit
40. Software requirements that limit the options available to the system designer.
Objective
Design Constraints
Data Model
Request For Quote (RFQ)
41. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Cardinality
Object Oriented Modeling
Model(s)
Temporal Event
42. Ability of systems to communicate by exchanging data or services.
Prioritization
Interoperability
Indicator
Requirement
43. A data element with a specified data type that describes information associated with a concept or entity.
Objective
Attribute
Organization
Service
44. Any unique and verifiable work product or service that a party has agreed to deliver.
End User
Repository
Class
Deliverable
45. 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
Transition Requirement(s)
Requirement(s) Attribute
Technical Constraint(s)
Implementation Subject Matter Expert (SME)
46. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Organization Modeling
Developer
Subject Matter Expert (SME)
Implementation Subject Matter Expert (SME)
47. A group or person who has interests that may be affected by an initiative or influence over it.
Quality
Organizational Unit
Stakeholder
Focus Group
48. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Business Architecture
Structural Rule
Decomposition
Structured Walkthrough
49. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Regulator
Fishbone Diagram
Scope Model
Activity Diagram
50. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.
Opportunity Analysis
User Story
Verified Requirements
Model(s)