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.
Enterprise
Requirements Signoff
User Story
Developer
2. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Quality Attributes
Verified Requirements
Relationship Map
Knowledge Area
3. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Project Manager
Requirements Management
Business Constraint(s)
Structured Walkthrough
4. A link between two elements or objects in a diagram.
Business Analysis Approach
Desired Outcome
Association
Repository
5. A fixed period of time to accomplish a desired outcome.
Timebox
Requirements Management Plan
Peer Review
Knowledge Area
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.
Requirement
Activity Diagram
Business Process
Use Case
7. A type of data model that depicts information groups as classes.
Class Model
Evaluation
Cost Benefit Analysis
Business Constraint(s)
8. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Business Process
Requirement
Business Case
Quality Attributes
9. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Benchmarking
Requirements Signoff
SWOT Analysis
Operative Rule(s)
10. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Fishbone Diagram
Organizational Process Asset
Operative Rule(s)
Work Breakdown Structure (WBS)
11. 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
System
Product Scope
Stakeholder Requirement
Requirement(s) Attribute
12. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Structural Rule
Business Requirements Document
User
Methodology
13. 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)
Subject Matter Expert (SME)
Requirement(s) Attribute
Quality Assurance
14. A stakeholder who uses products or services delivered by an organization.
Customer
Requirements Management Plan
Black Box Tests
Association
15. A person with specific expertise in an area or domain under investigation.
Business Analysis Plan
Domain Subject Matter Expert (SME)
Class Model
Incremental Delivery
16. An analysis model describing the data structures and attributes needed by the system.
Operational Support
Data Dictionary
Business Analysis Communication Plan
Change Control Board (CCB)
17. 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
Functional Requirement(s)
Operative Rule(s)
Root Cause Analysis
18. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Knowledge Area
Quality Assurance
Business Requirements Document
User Requirements Document
19. Any effort undertaken with a defined goal or objective.
Business Event
Variance Analysis
Initiative
Decision Analysis
20. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine
Focus Group
Activity
Business Architecture
Attribute
21. An analysis model that shows user interface dialogs arranged as hierarchies.
Business Analysis Approach
Peer Review
Dialog Hierarchy
Requirement(s) Attribute
22. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Requirements Traceability
Change Control Board (CCB)
Data Entity
Requirements Signoff
23. A group or person who has interests that may be affected by an initiative or influence over it.
Organizational Readiness Assessment
Change Control Board (CCB)
Business Case
Stakeholder
24. 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.
End User
Process Map
Requirements Workshop
Requirement
25. Creating working software in multiple releases so the entire product is delivered in portions over time.
Requirements Iteration
Structural Rule
Domain Subject Matter Expert (SME)
Incremental Delivery
26. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Survey
Validation
Software/Systems Requirements Specification
Event Response Table
27. The work that must be performed to deliver a product service or result with the specified features and functions.
Project Scope
Business Requirement
Use Case
Project
28. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Gap Analysis
Vertical Prototype
End User
Business Architecture
29. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Cardinality
Competitive Analysis
Dialog Hierarchy
30. 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
Repository
Business Need(s)
Request For Proposal (RFP)
Metric
31. A measure of the profitability of a project or investment.
Glossary
Prototype
Return on Investment
User
32. 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
Decision Analysis
Gap Analysis
Stakeholder Requirement
Class
33. Software requirements that limit the options available to the system designer.
Change Control Board (CCB)
Problem Statement
Project
Design Constraints
34. 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.
Vertical Prototype
Business Event
Inspection
Context Diagram
35. 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
Customer
Decision Tables
Business Requirement
36. 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
Unified Modeling Language (UML)
Organization
Data Flow Diagram (DFD)
Business Policy
37. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Requirements Traceability
Requirements Risk Mitigation Strategy
Competitive Analysis
Entity-Relationship Diagram
38. A description of the requirements management process.
Plan-driven Methodology
Change Control Board (CCB)
Requirements Model
Requirements Management Plan
39. The product capabilities or things the product must do for its users.
Business Analysis Plan
Functional Requirement(s)
Developer
Stakeholder List
40. The human and nonhuman roles that interact with the system.
Business Domain Model
Requirements Validation
Actor(s)
Interoperability
41. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Change Control Board (CCB)
Solution
Dialog Map
Requirements Workshop
42. A prototype developed to explore or verify requirements.
Relationship
Exploratory Prototype
Relationship Map
Regulator
43. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Checklist
Requirements Model
Requirements Allocation
Decision Analysis
44. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Indicator
Project Manager
User Requirements Document
Class
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.
Work Breakdown Structure (WBS)
Prioritization
Requirements Management
Analyst
46. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Change Control Board (CCB)
Temporal Event
Organizational Process Asset
Scenario
47. A prototype that is continuously modified and updated in response to feedback from users.
Organizational Unit
Evolutionary Prototype
User Requirements Document
User Acceptance Test
48. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Business Policy
Requirements Risk Mitigation Strategy
Work Product
Regulator
49. A solution or component of a solution that is the result of a project.
Requirements Package
Horizontal Prototype
Walkthrough
Product
50. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Observation
Business Analysis Approach
Vertical Prototype
Throw-away Prototype