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 link between two elements or objects in a diagram.
Regulator
Association
Transition Requirement(s)
End User
2. 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.
User Story
Solution Scope
Timebox
Requirements Traceability
3. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Implementation Subject Matter Expert (SME)
Peer Review
Requirement
Metric
4. 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.
Walkthrough
Fishbone Diagram
Change-driven Methodology
Organizational Readiness Assessment
5. The features and functions that characterize a product service or result.
Product Scope
Survey
Fishbone Diagram
Evaluation
6. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Service
Temporal Event
Sponsor
Span of Control
7. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Peer Review
Requirements Management
Solution Scope
Change-driven Methodology
8. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Business Event
Quality
Requirements Trace Matrix
Implementation Subject Matter Expert (SME)
9. 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.
Verified Requirements
Interoperability
Organization
Baseline
10. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Business Case
Evaluation
Request For Information (RFI)
11. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Survey
Methodology
Analyst
Competitive Analysis
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
Process Model
Request For Proposal (RFP)
Secondary Actor
Request For Information (RFI)
13. A stakeholder person device or system that directly or indirectly accesses a system.
User
Metric
Relationship Map
Subject Matter Expert (SME)
14. A partial or preliminary version of the system.
Prototype
Scenario
Benchmarking
Project Manager
15. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Relationship
Tester
Focus Group
Attribute
16. An analysis model describing the data structures and attributes needed by the system.
Work Product
Data Dictionary
Organizational Readiness Assessment
Request For Proposal (RFP)
17. A solution or component of a solution that is the result of a project.
Repository
Quality Attributes
Prioritization
Product
18. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Domain
Business Requirements Document
Problem Statement
SWOT Analysis
19. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Business Domain Model
Unified Modeling Language (UML)
Relationship
Commercial-off-the-Shelf Software (COTS)
20. A prototype that is continuously modified and updated in response to feedback from users.
Operational Support
Unified Modeling Language (UML)
Data Entity
Evolutionary Prototype
21. A model that defines the boundaries of a business domain or solution.
Requirements Model
Unified Modeling Language (UML)
Business Analysis Communication Plan
Scope Model
22. A temporary endeavor undertaken to create a unique product service or result.
Product Backlog
Requirements Trace Matrix
Cost Benefit Analysis
Project
23. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Data Entity
Scope
Customer
Use Case Diagram
24. An informal solicitation of proposals from vendors.
Requirement
Gap Analysis
Request For Quote (RFQ)
Methodology
25. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Requirements Allocation
Supplier
Requirements Trace Matrix
Change-driven Methodology
26. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Business Requirements Document
Use Case Diagram
Activity
Request For Information (RFI)
27. All materials used by groups within an organization to define tailor implement and maintain their processes.
Subject Matter Expert (SME)
Product Backlog
System
Organizational Process Asset
28. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Process Model
Product Backlog
Product Scope
29. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Request For Information (RFI)
Feasibility Study
Temporal Event
User
30. The number of employees a manger is directly (or indirectly) responsible for.
Evolutionary Prototype
Span of Control
Fishbone Diagram
State Diagram
31. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Unified Modeling Language (UML)
User Acceptance Test
Gap Analysis
32. A practitioner of business analysis.
Problem Statement
Request For Proposal (RFP)
Requirements Workshop
Business Analyst
33. Work carried out or on behalf of others.
Service
Swimlane
Requirements Trace Matrix
User Acceptance Test
34. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Process Map
Temporal Event
Design Constraints
Sponsor
35. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Supplier
Structured Walkthrough
Metric
User Requirements Document
36. 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.
Sponsor
Actor(s)
Supplier
Benchmarking
37. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
State Diagram
Evaluation
Vision Statement (product vision statement)
38. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Iteration
Evolutionary Prototype
Opportunity Analysis
User
39. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Solution Requirement
Vision Statement (product vision statement)
Process Model
Scope Model
40. 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.
Context Diagram
Feature
Observation
Requirements Workshop
41. 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.
Focus Group
Operational Support
Cardinality
Business Need(s)
42. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Requirements Traceability
Knowledge Area
Timebox
Business Requirements Document
43. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Included Use Cases
Structured Walkthrough
Repository
Solution Requirement
44. 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.
Domain
Feasibility Study
Force Field Analysis
Business Case
45. 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
Operative Rule(s)
Requirements Signoff
Relationship
Requirements Risk Mitigation Strategy
46. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Iteration
Organization
Desired Outcome
Indicator
47. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
State Diagram
Organizational Readiness Assessment
Unified Modeling Language (UML)
Analyst
48. A prototype developed to explore or verify requirements.
Exploratory Prototype
Unified Modeling Language (UML)
Business Architecture
Plan-driven Methodology
49. 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
User Requirements Document
Business Domain Model
Regulator
50. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Black Box Tests
Data Flow Diagram (DFD)
Business Constraint(s)
Incremental Delivery