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 group or person who has interests that may be affected by an initiative or influence over it.
Organization Modeling
Stakeholder
Regulator
Requirements Validation
2. The area covered by a particular activity or topic of interest.
Metric
Process Model
Scope
Domain Subject Matter Expert (SME)
3. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Quality Attributes
Included Use Cases
Observation
Vision Statement (product vision statement)
4. 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
Requirements Model
Vision Statement (product vision statement)
Deliverable
5. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
User Story
Change Control Board (CCB)
Project Charter
Use Case Diagram
6. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Glossary
Decision Tree
Requirements Verification
Analyst
7. 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
Activity Diagram
Secondary Actor
Relationship
8. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Requirements Package
Prioritization
Object Oriented Modeling
Process Model
9. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Swimlane
External Interfaces
Cost Benefit Analysis
Optionality
10. Information that is used to understand the context and validity of information recorded in a system.
Implementation Subject Matter Expert (SME)
Benchmarking
Metadata
Domain
11. A person with specific expertise in an area or domain under investigation.
Operational Support
Domain Subject Matter Expert (SME)
Supplier
Interview
12. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
Event Response Table
User Acceptance Test
Code
Requirement(s) Attribute
13. 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.
Project Scope
Business Analysis Communication Plan
Cost Benefit Analysis
Requirements Traceability
14. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a
Business Case
Object Oriented Modeling
Desired Outcome
Technical Constraint(s)
15. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Business Requirement
Model(s)
Data Entity
Solution Scope
16. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Enterprise
User
Structural Rule
Elicitation
17. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
External Interfaces
Functional Requirement(s)
Quality Assurance
Design Constraints
18. An actor who participates in but does not initiate a use case.
Secondary Actor
Evolutionary Prototype
Business Goal
Deliverable
19. A stakeholder who provides products or services to an organization.
Model(s)
Process Map
Included Use Cases
Supplier
20. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Capability
Requirements Management Plan
Black Box Tests
Validation
21. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Data Model
Data Entity
Requirements Allocation
Feasibility Study
22. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Baseline
Enterprise Architecture
Interface
Relationship
23. 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.
Work Product
Feature
Solution
Customer
24. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Subject Matter Expert (SME)
Force Field Analysis
Data Dictionary
Risk
25. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Constraint
Timebox
Impact Analysis
26. The set of capabilities a solution must deliver in order to meet the business need.
Requirements Signoff
Requirements Verification
Solution Scope
Elicitation
27. An analysis model that illustrates the architecture of the system's user interface.
Dialog Map
Context Diagram
Project Manager
Business Analysis Approach
28. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Enterprise
Class Model
Survey
Activity Diagram
29. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Change Control Board (CCB)
Stakeholder Analysis
Fishbone Diagram
Transition Requirement(s)
30. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Requirement
Iteration
Problem Statement
Verification
31. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Implementation Subject Matter Expert (SME)
Product Backlog
Root Cause Analysis
Data Flow Diagram (DFD)
32. A shared boundary between any two persons and/or systems through which information is communicated.
Quality Assurance
Requirements Signoff
Data Dictionary
Interface
33. The product capabilities or things the product must do for its users.
Activity Diagram
Functional Requirement(s)
Requirements Allocation
External Interfaces
34. A prototype that dives into the details of the interface functionality or both.
Benchmarking
Technique
Vertical Prototype
Opportunity Analysis
35. A unit of work performed as part of an initiative or process.
Risk
Activity
Stakeholder List
Document Analysis
36. 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
Organizational Process Asset
Class
Requirements Risk Mitigation Strategy
Swimlane
37. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Validated Requirements
Entity-Relationship Diagram
Process Model
Constraint
38. 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
Developer
Organization
Association
Solution Requirement
39. Any unique and verifiable work product or service that a party has agreed to deliver.
Validation
Business Domain Model
Deliverable
Quality
40. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Assumption
Unified Modeling Language (UML)
Observation
System
41. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
Operational Support
Return on Investment
Defect
Business Need(s)
42. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Throw-away Prototype
Swimlane
Constraint
Requirements Package
43. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Analyst
Inspection
Scope Model
Evolutionary Prototype
44. Ability of systems to communicate by exchanging data or services.
Change-driven Methodology
Requirements Allocation
Domain
Interoperability
45. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
User Requirements Document
End User
Requirements Management Tool
Event
46. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Work Breakdown Structure (WBS)
Business Domain Model
Organization
Business Analysis Plan
47. 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
Impact Analysis
Stakeholder Requirement
Stakeholder
Validated Requirements
48. A measure of the profitability of a project or investment.
Requirement(s) Defect
Data Entity
Organizational Readiness Assessment
Return on Investment
49. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Technical Constraint(s)
Observation
Cardinality
Request For Proposal (RFP)
50. 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
Business Analysis Approach
Validated Requirements
Indicator
Operative Rule(s)