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 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
Process Model
Cardinality
Organization
Model(s)
2. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Enterprise Architecture
Quality
Event Response Table
3. 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
Elicitation
Business Architecture
Business Domain Model
4. A link between two elements or objects in a diagram.
Evolutionary Prototype
Association
User Requirements Document
Project Scope
5. 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
Impact Analysis
Monitoring
Request For Proposal (RFP)
Class Model
6. 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
Use Case
Business Constraint(s)
Stated Requirements
Change Control Board (CCB)
7. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Design Constraints
Organization Modeling
Walkthrough
Interview
8. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Trace Matrix
External Interfaces
Methodology
Relationship
9. Ability of systems to communicate by exchanging data or services.
Throw-away Prototype
Functional Requirement(s)
Quality
Interoperability
10. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Project Charter
Data Entity
User Acceptance Test
Stated Requirements
11. 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
Relationship Map
Assumption
12. 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.
Verified Requirements
Requirement
Data Dictionary
Document Analysis
13. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Class
Desired Outcome
Business Requirement
14. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Analyst
Stakeholder Analysis
Attribute
Desired Outcome
15. 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
Black Box Tests
Stakeholder Requirement
Requirements Management
Work Breakdown Structure (WBS)
16. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Business Need(s)
Validated Requirements
Metric
Black Box Tests
17. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Product Backlog
Requirements Risk Mitigation Strategy
Deliverable
Objective
18. The area covered by a particular activity or topic of interest.
Scope
Stated Requirements
Decision Analysis
Scope Model
19. A temporary endeavor undertaken to create a unique product service or result.
Decomposition
Project
Non-functional Requirement(s)
Request For Quote (RFQ)
20. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Business Analysis Plan
Business Rule(s)
Work Product
Evaluation
21. The features and functions that characterize a product service or result.
Unified Modeling Language (UML)
Product Scope
Process Map
Attribute
22. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Benchmarking
Objective
Product Backlog
Gap Analysis
23. 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.
Requirements Management Plan
Focus Group
Association
Decision Tree
24. Metadata related to a requirement used to assist with requirements development and management.
Business Analysis Approach
Opportunity Analysis
Stakeholder List
Requirement(s) Attribute
25. Creating working software in multiple releases so the entire product is delivered in portions over time.
Stakeholder List
Document Analysis
Incremental Delivery
Opportunity Analysis
26. The set of capabilities a solution must deliver in order to meet the business need.
Knowledge Area
Vertical Prototype
Requirements Management Plan
Solution Scope
27. An analysis model describing the data structures and attributes needed by the system.
Structured Walkthrough
Data Dictionary
User Acceptance Test
Document Analysis
28. 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.
Regulator
Requirements Signoff
Assumption
Context Diagram
29. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Business Domain Model
Use Case Diagram
Baseline
30. 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.
Black Box Tests
Project Scope
Feasibility Study
Data Entity
31. Any recognized association of people in the context of an organization or enterprise.
Requirements Workshop
Attribute
Organizational Unit
Request For Proposal (RFP)
32. 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
Methodology
Business Requirement
Interview
33. 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.
Fishbone Diagram
Requirements Workshop
Survey
Constraint
34. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Regulator
Structural Rule
Verified Requirements
Supplier
35. Something that occurs to which an organizational unit system or process must respond.
Event
Feature
Requirements Model
Problem Statement
36. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Requirements Validation
Organization
Risk
Stakeholder Analysis
37. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Technique
Product Backlog
Enterprise Architecture
Survey
38. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
Validated Requirements
Initiative
Lessons Learned Process
Evaluation
39. A measure of the profitability of a project or investment.
Return on Investment
Use Case
Methodology
Business Analysis Approach
40. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Project Scope
Organizational Process Asset
Solution
Decision Tables
41. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Subject Matter Expert (SME)
Competitive Analysis
Tester
Validation
42. A stakeholder who provides products or services to an organization.
Timebox
Baseline
Swimlane
Supplier
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.
Operative Rule(s)
Request For Proposal (RFP)
Organizational Unit
Walkthrough
44. The work that must be performed to deliver a product service or result with the specified features and functions.
Project Scope
Metadata
Validated Requirements
Business Analysis Communication Plan
45. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Validated Requirements
Prioritization
Defect
Functional Requirement(s)
46. A prototype that is continuously modified and updated in response to feedback from users.
Fishbone Diagram
Class
Evolutionary Prototype
Business Case
47. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Business Policy
Developer
Scope Model
User Requirements Document
48. An informal solicitation of proposals from vendors.
Sponsor
Horizontal Prototype
Request For Quote (RFQ)
Code
49. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Design Constraints
SWOT Analysis
Requirements Verification
Requirements Management Plan
50. A non-actionable directive that supports a business goal.
Requirement(s) Defect
Product
Work Breakdown Structure (WBS)
Business Policy