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. 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.
Technique
Non-functional Requirement(s)
Baseline
Enterprise
2. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Focus Group
Elicitation
Work Product
Risk
3. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode
Business Domain Model
Prioritization
Business Goal
Business Process
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
Model(s)
Organizational Unit
Product Scope
5. A prototype developed to explore or verify requirements.
Requirements Signoff
Exploratory Prototype
Operative Rule(s)
Interoperability
6. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Technical Constraint(s)
Requirement
Stakeholder Analysis
Prioritization
7. 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
Business Requirements Document
Stakeholder Requirement
User
Requirements Management Tool
8. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Requirements Management
Walkthrough
Swimlane
Evolutionary Prototype
9. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Quality Attributes
Defect
Benchmarking
Context Diagram
10. Creating working software in multiple releases so the entire product is delivered in portions over time.
End User
Transition Requirement(s)
Incremental Delivery
Variance Analysis
11. 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
Requirements Allocation
Requirement(s) Defect
Operative Rule(s)
Requirements Trace Matrix
12. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Cost Benefit Analysis
Business Goal
Organizational Unit
Business Process
13. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Variance Analysis
Service
Business Requirements Document
Deliverable
14. The features and functions that characterize a product service or result.
Validated Requirements
Organization Modeling
Product Scope
Stakeholder
15. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Verified Requirements
Business Analyst
Product
System
16. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Inspection
Black Box Tests
Feature
Organization Modeling
17. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.
Dialog Map
Verification
Design Constraints
Developer
18. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Problem Statement
Customer
Interoperability
19. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Requirements Workshop
Stakeholder List
Risk
Monitoring
20. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Impact Analysis
Glossary
Competitive Analysis
Decomposition
21. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Domain Subject Matter Expert (SME)
Requirements Model
Indicator
Subject Matter Expert (SME)
22. 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.
Metric
Request For Proposal (RFP)
Stated Requirements
Verification
23. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Activity Diagram
Solution Scope
Business Rule(s)
24. A system of programming statements symbols and rules used to represent instructions to a computer.
Tester
Business Event
Implementation Subject Matter Expert (SME)
Code
25. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Requirements Verification
Validated Requirements
Business Analysis
Product
26. A unit of work performed as part of an initiative or process.
Temporal Event
Activity
Use Case Diagram
Business Analysis Approach
27. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Business Case
Requirement(s) Defect
Event Response Table
28. 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
Stakeholder Analysis
Data Flow Diagram (DFD)
Use Case
Business Constraint(s)
29. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Observation
Attribute
Requirements Signoff
Monitoring
30. Work carried out or on behalf of others.
Technical Constraint(s)
State Diagram
Requirements Risk Mitigation Strategy
Service
31. 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.
Assumption
Iteration
System
Force Field Analysis
32. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Brainstorming
State Diagram
Cost Benefit Analysis
System
33. 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.
Gap Analysis
Verified Requirements
Desired Outcome
Object Oriented Modeling
34. The human and nonhuman roles that interact with the system.
Actor(s)
Product
Initiative
Process Model
35. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Scope
Developer
Regulator
36. A partial or preliminary version of the system.
Feature
Prototype
Root Cause Analysis
Project Scope
37. A function of an organization that enables it to achieve a business goal or objective.
Opportunity Analysis
Capability
Feature
Knowledge Area
38. 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.
Stakeholder
Context Diagram
Attribute
Activity Diagram
39. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Unified Modeling Language (UML)
Requirement
Cost Benefit Analysis
Commercial-off-the-Shelf Software (COTS)
40. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Stakeholder Analysis
Project Scope
Relationship Map
Requirement(s) Attribute
41. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.
Requirement
Class Model
Verification
Assumption
42. 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.
Feature
Observation
Unified Modeling Language (UML)
Evolutionary Prototype
43. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Decision Analysis
Activity Diagram
Structured Walkthrough
Requirements Allocation
44. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Regulator
External Interfaces
Project Manager
Prototype
45. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Evolutionary Prototype
Technique
Horizontal Prototype
46. A shared boundary between any two persons and/or systems through which information is communicated.
Decision Tables
Structural Rule
Interface
Included Use Cases
47. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Requirements Trace Matrix
Organizational Readiness Assessment
Requirements Verification
Decomposition
48. Any recognized association of people in the context of an organization or enterprise.
Technical Constraint(s)
Baseline
Class
Organizational Unit
49. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Unified Modeling Language (UML)
Solution
Project Manager
50. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Transition Requirement(s)
Use Case
Walkthrough