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 set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Allocation
Data Flow Diagram (DFD)
Cardinality
Requirements Package
2. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Horizontal Prototype
Software/Systems Requirements Specification
Project
3. 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.
Requirement(s) Defect
SWOT Analysis
Verified Requirements
Process Map
4. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Interview
Structured Walkthrough
Verified Requirements
Business Requirement
5. An analysis model showing the life cycle of a data entity or class.
State Diagram
Timebox
Process Model
Requirement(s) Defect
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.
Context Diagram
User
Prioritization
Analyst
7. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Cardinality
Methodology
Subject Matter Expert (SME)
Solution Scope
8. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Process Model
Iteration
Actor(s)
User Requirements Document
9. 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.
Implementation Subject Matter Expert (SME)
Verified Requirements
Elicitation
End User
10. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Initiative
Metadata
Monitoring
Interoperability
11. The quality attributes design and implementation constraints and external interfaces that the product must have.
Opportunity Analysis
Developer
Non-functional Requirement(s)
Solution
12. 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
Problem Statement
Operative Rule(s)
Change Control Board (CCB)
13. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Feature
Process Map
Business Need(s)
Observation
14. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Technique
Structural Rule
Analyst
Solution
15. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Product Scope
Organizational Readiness Assessment
Activity
Context Diagram
16. 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.
Vertical Prototype
Competitive Analysis
Enterprise
Sequence Diagram
17. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Organizational Process Asset
Quality Attributes
Requirements Trace Matrix
18. 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
Developer
Object Oriented Modeling
Business Requirement
Metadata
19. The features and functions that characterize a product service or result.
Product Scope
Process Map
Secondary Actor
Interoperability
20. A stakeholder who provides products or services to an organization.
Requirement
Checklist
Supplier
State Diagram
21. 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.
Data Entity
User
Vision Statement (product vision statement)
Requirements Traceability
22. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Use Case Diagram
Solution Requirement
Data Entity
Verified Requirements
23. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Gap Analysis
Desired Outcome
Stakeholder Analysis
Requirements Workshop
24. The human and nonhuman roles that interact with the system.
Analyst
Actor(s)
Inspection
Force Field Analysis
25. 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.
SWOT Analysis
Problem Statement
Data Flow Diagram (DFD)
Requirement
26. 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.
Requirements Iteration
Sequence Diagram
Context Diagram
Quality Assurance
27. 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.
Requirements Workshop
Walkthrough
Business Policy
Project Scope
28. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Context Diagram
Data Model
Prioritization
Use Case Diagram
29. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Incremental Delivery
Code
Technique
Data Model
30. 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.
Deliverable
Document Analysis
Work Breakdown Structure (WBS)
Decision Tree
31. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Use Case
User Requirements Document
Plan-driven Methodology
Throw-away Prototype
32. The product capabilities or things the product must do for its users.
Business Requirement
Data Model
Functional Requirement(s)
Customer
33. 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
Business Architecture
Business Process
Transition Requirement(s)
Return on Investment
34. Metadata related to a requirement used to assist with requirements development and management.
Business Architecture
Span of Control
Cost Benefit Analysis
Requirement(s) Attribute
35. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Evaluation
Business Rule(s)
Risk
Walkthrough
36. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Impact Analysis
Software/Systems Requirements Specification
Risk
Business Event
37. A unit of work performed as part of an initiative or process.
Requirements Risk Mitigation Strategy
Business Need(s)
Activity
Requirements Trace Matrix
38. An analysis model that shows user interface dialogs arranged as hierarchies.
Use Case Diagram
Requirements Traceability
Technique
Dialog Hierarchy
39. A practitioner of business analysis.
Business Analyst
Object Oriented Modeling
Subject Matter Expert (SME)
Change-driven Methodology
40. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Opportunity Analysis
Solution Scope
Cost Benefit Analysis
41. 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.
Technique
Object Oriented Modeling
Stated Requirements
Regulator
42. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Project Manager
Interface
Data Entity
Requirements Validation
43. Something that occurs to which an organizational unit system or process must respond.
Included Use Cases
Event
Walkthrough
Code
44. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Baseline
Stakeholder List
Focus Group
Regulator
45. 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.
Request For Information (RFI)
User Story
User Requirements Document
Verification
46. An assessment of the costs and benefits associated with a proposed initiative.
Business Analysis Plan
Business Case
Quality
Association
47. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Requirements Signoff
Enterprise Architecture
Project Scope
Validation
48. Any unique and verifiable work product or service that a party has agreed to deliver.
Deliverable
Verified Requirements
Throw-away Prototype
Software/Systems Requirements Specification
49. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Throw-away Prototype
Operational Support
Work Product
Vision Statement (product vision statement)
50. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Lessons Learned Process
Objective
Plan-driven Methodology
Quality Assurance