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 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.
Cardinality
Analyst
Decision Tables
Service
2. A system trigger that is initiated by humans.
Requirements Risk Mitigation Strategy
Quality Assurance
Product Backlog
Business Event
3. A system trigger that is initiated by time.
Tester
Temporal Event
Defect
Assumption
4. An actor who participates in but does not initiate a use case.
Request For Information (RFI)
Secondary Actor
Code
Work Product
5. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Survey
Domain Subject Matter Expert (SME)
Technique
Sponsor
6. All materials used by groups within an organization to define tailor implement and maintain their processes.
Checklist
Organizational Process Asset
Baseline
Objective
7. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Requirements Allocation
Validated Requirements
Requirements Signoff
Requirement
8. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Business Policy
Requirements Management Tool
Organization Modeling
Business Requirements Document
9. 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
Vision Statement (product vision statement)
Operational Support
Business Constraint(s)
Methodology
10. 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.
Requirements Iteration
Stakeholder List
Problem Statement
Scope
11. Formal approval of a set of requirements by a sponsor or other decision maker.
Technique
Span of Control
Requirements Signoff
Class
12. A group or person who has interests that may be affected by an initiative or influence over it.
Cardinality
Stakeholder
Analyst
Vertical Prototype
13. An analysis model describing the data structures and attributes needed by the system.
Exploratory Prototype
Stakeholder Requirement
Data Dictionary
Event Response Table
14. 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.
Developer
Included Use Cases
Horizontal Prototype
Implementation Subject Matter Expert (SME)
15. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Deliverable
Model(s)
Desired Outcome
Requirements Allocation
16. A system of programming statements symbols and rules used to represent instructions to a computer.
Process Map
Code
Dialog Hierarchy
Operational Support
17. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Decomposition
Stakeholder Requirement
Observation
Risk
18. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Flow Diagram (DFD)
Focus Group
Requirements Signoff
Non-functional Requirement(s)
19. 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.
Technique
Enterprise
Swimlane
Business Rule(s)
20. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Verified Requirements
Business Policy
Unified Modeling Language (UML)
Structured Walkthrough
21. An assessment of the costs and benefits associated with a proposed initiative.
Domain Subject Matter Expert (SME)
Business Case
Black Box Tests
Verified Requirements
22. 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.
Survey
Requirements Model
Code
Project Charter
23. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Work Breakdown Structure (WBS)
State Diagram
Domain
24. 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.
User Requirements Document
Project Manager
Force Field Analysis
Use Case
25. Any unique and verifiable work product or service that a party has agreed to deliver.
Survey
Deliverable
Stakeholder
Requirements Workshop
26. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Requirements Iteration
Black Box Tests
Peer Review
Requirements Risk Mitigation Strategy
27. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Domain Subject Matter Expert (SME)
Impact Analysis
Requirement(s) Defect
Secondary Actor
28. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Business Rule(s)
End User
Walkthrough
29. 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
Business Goal
Event Response Table
Operative Rule(s)
Request For Proposal (RFP)
30. A prototype developed to explore or verify requirements.
Exploratory Prototype
Business Requirement
Data Model
Tester
31. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Organization Modeling
System
Vertical Prototype
Root Cause Analysis
32. 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.
Validation
Verified Requirements
Constraint
Business Analysis Plan
33. A stakeholder who uses products or services delivered by an organization.
Implementation Subject Matter Expert (SME)
Customer
Project Manager
Requirements Package
34. A link between two elements or objects in a diagram.
Sequence Diagram
Association
Context Diagram
Developer
35. A non-actionable directive that supports a business goal.
Business Policy
Process Map
Assumption
Change-driven Methodology
36. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Structured Walkthrough
Business Analysis Communication Plan
Business Goal
37. The problem area undergoing analysis.
Customer
Domain
Interoperability
Sequence Diagram
38. Any effort undertaken with a defined goal or objective.
Baseline
Validated Requirements
Initiative
Supplier
39. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Decision Tree
Requirements Trace Matrix
Iteration
Requirements Verification
40. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Cardinality
End User
User Acceptance Test
41. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme
User Story
Document Analysis
Organization
Exploratory Prototype
42. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Subject Matter Expert (SME)
Decision Tree
Optionality
Horizontal Prototype
43. 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.
Data Model
Relationship Map
Verification
Benchmarking
44. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
User Story
Vision Statement (product vision statement)
Stakeholder List
Sponsor
45. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
System
Decomposition
Verified Requirements
Product Scope
46. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
User Story
Checklist
Business Requirement
Requirements Verification
47. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Class
Developer
Business Requirement
Organizational Readiness Assessment
48. 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.
Secondary Actor
Subject Matter Expert (SME)
Feature
Requirement
49. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Requirement(s) Attribute
Survey
Verification
50. 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.
Business Analysis Plan
Structured Walkthrough
Interview
State Diagram