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 target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Throw-away Prototype
Analyst
Lessons Learned Process
2. A fixed period of time to accomplish a desired outcome.
Initiative
Stated Requirements
Project
Timebox
3. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Unified Modeling Language (UML)
Domain
Quality Attributes
Requirements Management Plan
4. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Requirements Management Plan
Feature
Scope Model
5. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Cardinality
Problem Statement
Technical Constraint(s)
Dialog Map
6. A practitioner of business analysis.
Risk
Business Analyst
Use Case Diagram
User Requirements Document
7. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Dialog Map
Stakeholder Requirement
Requirement
Product Backlog
8. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Dialog Hierarchy
Subject Matter Expert (SME)
Stakeholder Analysis
Included Use Cases
9. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User
Interview
User Requirements Document
Stakeholder List
10. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Optionality
Work Breakdown Structure (WBS)
Developer
Operative Rule(s)
11. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Evolutionary Prototype
Sponsor
Quality Attributes
Validated Requirements
12. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Request For Information (RFI)
Product Scope
Activity Diagram
Business Analysis Approach
13. A type of data model that depicts information groups as classes.
Business Need(s)
Process Model
Timebox
Class Model
14. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Document Analysis
Context Diagram
Business Analyst
Risk
15. 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.
Problem Statement
Feature
Business Goal
Interview
16. Any recognized association of people in the context of an organization or enterprise.
Interview
Organizational Unit
Impact Analysis
Business Requirements Document
17. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Service
Organization
Survey
Quality Assurance
18. The problem area undergoing analysis.
Business Rule(s)
Request For Proposal (RFP)
Product Backlog
Domain
19. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Product Backlog
Design Constraints
Technical Constraint(s)
Data Model
20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Business Event
Deliverable
Quality Attributes
Stakeholder Analysis
21. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Defect
Sequence Diagram
Implementation Subject Matter Expert (SME)
Requirements Signoff
22. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Scope
Dialog Hierarchy
Monitoring
23. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Repository
Timebox
Problem Statement
Domain Subject Matter Expert (SME)
24. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Activity Diagram
Variance Analysis
Unified Modeling Language (UML)
Constraint
25. Software developed and sold for a particular market.
Organization Modeling
Commercial-off-the-Shelf Software (COTS)
Brainstorming
Association
26. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Elicitation
Desired Outcome
Defect
Code
27. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Supplier
Dialog Hierarchy
Requirement(s) Attribute
28. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Quality Attributes
Business Process
Benchmarking
Scenario
29. 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.
Requirements Verification
Process Map
Activity Diagram
Requirements Model
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
Risk
Requirements Model
Requirements Verification
31. 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.
Optionality
Checklist
Included Use Cases
Initiative
32. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Code
Knowledge Area
Return on Investment
33. A stakeholder who uses products or services delivered by an organization.
Inspection
Requirement
Force Field Analysis
Customer
34. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Tester
Stakeholder List
Requirements Validation
35. 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
State Diagram
Business Domain Model
Request For Proposal (RFP)
Unified Modeling Language (UML)
36. 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.
Cost Benefit Analysis
Document Analysis
Class
Enterprise Architecture
37. The product capabilities or things the product must do for its users.
Enterprise
Functional Requirement(s)
Brainstorming
User Story
38. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Requirements Allocation
Defect
User Acceptance Test
Risk
39. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Included Use Cases
Decision Analysis
Organization Modeling
State Diagram
40. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Business Requirement
Repository
Benchmarking
Black Box Tests
41. 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
Event
Transition Requirement(s)
Requirements Verification
Inspection
42. A prototype that dives into the details of the interface functionality or both.
Fishbone Diagram
Span of Control
State Diagram
Vertical Prototype
43. 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.
Work Breakdown Structure (WBS)
Scope
Walkthrough
Gap Analysis
44. 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.
Feature
Use Case
Verification
Enterprise Architecture
45. 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
Enterprise
Request For Proposal (RFP)
Variance Analysis
46. A solution or component of a solution that is the result of a project.
Metric
Product
Work Breakdown Structure (WBS)
Requirements Management Plan
47. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Requirements Traceability
Requirements Model
Work Product
Organizational Unit
48. Formal approval of a set of requirements by a sponsor or other decision maker.
Design Constraints
Quality
Cardinality
Requirements Signoff
49. A stakeholder who provides products or services to an organization.
Span of Control
Unified Modeling Language (UML)
Gap Analysis
Supplier
50. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Structural Rule
Work Breakdown Structure (WBS)
Temporal Event
Requirements Validation