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 brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Requirements Package
Vision Statement (product vision statement)
Business Event
Business Analysis Communication Plan
2. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Verified Requirements
Span of Control
Requirements Workshop
3. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Requirements Management
Requirements Trace Matrix
Code
4. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Stakeholder List
Interoperability
Plan-driven Methodology
Quality Attributes
5. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Developer
Organization
Checklist
User
6. 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
Evolutionary Prototype
Product
Requirements Management
7. A stakeholder person device or system that directly or indirectly accesses a system.
User
Requirements Package
Repository
Requirements Management
8. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Vision Statement (product vision statement)
Metric
Context Diagram
Decomposition
9. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Interface
Business Need(s)
Product Backlog
Stakeholder Analysis
10. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Flow Diagram (DFD)
Desired Outcome
Metadata
System
11. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Data Model
Stakeholder
Observation
Requirements Model
12. A function of an organization that enables it to achieve a business goal or objective.
Service
Capability
Dialog Map
Evaluation
13. Formal approval of a set of requirements by a sponsor or other decision maker.
Temporal Event
Requirements Validation
Organizational Readiness Assessment
Requirements Signoff
14. A specific actionable testable directive that is under the control of the business and supports a business policy.
Knowledge Area
Exploratory Prototype
Business Rule(s)
Variance Analysis
15. A shared boundary between any two persons and/or systems through which information is communicated.
Brainstorming
Interface
Work Product
Optionality
16. A partial or preliminary version of the system.
Quality
Relationship Map
Request For Information (RFI)
Prototype
17. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Data Flow Diagram (DFD)
Event
Cardinality
Work Product
18. 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.
Business Event
Scenario
Feature
Elicitation
19. A stakeholder who provides products or services to an organization.
Enterprise
Solution Scope
Supplier
Regulator
20. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Class Model
Repository
Monitoring
Throw-away Prototype
21. 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.
Business Analysis Approach
Sponsor
Context Diagram
Project Manager
22. The area covered by a particular activity or topic of interest.
Solution Requirement
Impact Analysis
Scope
Operational Support
23. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
Prototype
Implementation Subject Matter Expert (SME)
Data Entity
24. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Change Control Board (CCB)
Change-driven Methodology
Peer Review
Business Requirements Document
25. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
Implementation Subject Matter Expert (SME)
System
Project Charter
Relationship
26. The set of capabilities a solution must deliver in order to meet the business need.
Class
Implementation Subject Matter Expert (SME)
Solution Scope
Regulator
27. 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.
Use Case Diagram
Verification
Request For Information (RFI)
Entity-Relationship Diagram
28. A use case composed of a common set of steps used by multiple use cases.
Scope
Solution
Vision Statement (product vision statement)
Included Use Cases
29. All materials used by groups within an organization to define tailor implement and maintain their processes.
Metadata
Stakeholder
Baseline
Organizational Process Asset
30. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Prototype
Exploratory Prototype
Peer Review
Observation
31. 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
Dialog Map
Regulator
Product
32. A data element with a specified data type that describes information associated with a concept or entity.
Enterprise Architecture
Work Breakdown Structure (WBS)
Attribute
Analyst
33. A solution or component of a solution that is the result of a project.
Developer
Validated Requirements
Product
Business Analysis Plan
34. The quality attributes design and implementation constraints and external interfaces that the product must have.
Commercial-off-the-Shelf Software (COTS)
Business Analyst
Non-functional Requirement(s)
Organization Modeling
35. The problem area undergoing analysis.
Domain
Competitive Analysis
Scope Model
Organizational Readiness Assessment
36. 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.
Project Charter
Stakeholder List
Use Case
Black Box Tests
37. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Requirements Verification
Class
System
Organizational Readiness Assessment
38. A description of the requirements management process.
Stakeholder Requirement
Requirement(s) Defect
Supplier
Requirements Management Plan
39. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Commercial-off-the-Shelf Software (COTS)
Structured Walkthrough
Entity-Relationship Diagram
Requirements Trace Matrix
40. Any effort undertaken with a defined goal or objective.
Interface
Software/Systems Requirements Specification
Initiative
Brainstorming
41. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Model(s)
Business Case
Swimlane
External Interfaces
42. 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.
Sponsor
Evaluation
Project Scope
Risk
43. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
Regulator
Business Analysis Approach
Solution Scope
Decision Tables
44. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Project Manager
Evolutionary Prototype
Desired Outcome
User Acceptance Test
45. 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.
Elicitation
Technique
Timebox
Verified Requirements
46. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Cardinality
Competitive Analysis
Actor(s)
47. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Developer
Non-functional Requirement(s)
Temporal Event
Indicator
48. An assessment of the costs and benefits associated with a proposed initiative.
Business Case
Business Need(s)
Problem Statement
Process Map
49. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Feasibility Study
Survey
Technique
Metric
50. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Interview
Commercial-off-the-Shelf Software (COTS)
Organization Modeling
Vision Statement (product vision statement)