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 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
Interface
User Story
Scope Model
Solution
2. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Assumption
Observation
Return on Investment
Design Constraints
3. 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.
Project Charter
Metadata
User Acceptance Test
Business Requirements Document
4. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Swimlane
Decomposition
Indicator
Commercial-off-the-Shelf Software (COTS)
5. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Force Field Analysis
Data Flow Diagram (DFD)
Interoperability
Use Case Diagram
6. 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.
Interoperability
SWOT Analysis
Solution Requirement
Enterprise
7. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Capability
Knowledge Area
Requirement
Requirements Risk Mitigation Strategy
8. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Process Model
Association
Included Use Cases
Actor(s)
9. An informal solicitation of proposals from vendors.
Business Constraint(s)
Solution
Request For Quote (RFQ)
Feasibility Study
10. 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.
Commercial-off-the-Shelf Software (COTS)
Inspection
Prototype
Work Breakdown Structure (WBS)
11. 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
Analyst
Data Flow Diagram (DFD)
Assumption
12. Any effort undertaken with a defined goal or objective.
Initiative
Business Policy
Survey
Stakeholder Analysis
13. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.
Business Analysis Plan
Enterprise Architecture
Event Response Table
Requirements Traceability
14. 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
Interoperability
Black Box Tests
Scenario
Business Constraint(s)
15. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Product Scope
Domain Subject Matter Expert (SME)
Optionality
Impact Analysis
16. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Transition Requirement(s)
Benchmarking
Knowledge Area
Indicator
17. A system of programming statements symbols and rules used to represent instructions to a computer.
Code
Organizational Readiness Assessment
Object Oriented Modeling
Organization
18. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Structured Walkthrough
State Diagram
Business Event
Lessons Learned Process
19. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
User Acceptance Test
Deliverable
Organization
20. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Data Model
SWOT Analysis
Return on Investment
Technique
21. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Brainstorming
Relationship Map
Decision Tree
Evaluation
22. 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.
Brainstorming
Elicitation
Model(s)
Requirements Management
23. A description of the requirements management process.
Requirements Management Plan
Competitive Analysis
Validation
Temporal Event
24. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Requirements Iteration
Glossary
Domain Subject Matter Expert (SME)
Relationship Map
25. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Design Constraints
Evaluation
Defect
Model(s)
26. A solution or component of a solution that is the result of a project.
Cardinality
Organization
Product
Sponsor
27. 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.
Vertical Prototype
Non-functional Requirement(s)
Feature
Implementation Subject Matter Expert (SME)
28. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Event Response Table
Requirements Iteration
Decision Analysis
Evaluation
29. A group or person who has interests that may be affected by an initiative or influence over it.
Business Requirement
Evolutionary Prototype
Stakeholder
Stakeholder List
30. Limitations on the design of a solution that derive from the technology used in its implementation.
Regulator
Technical Constraint(s)
Peer Review
Stated Requirements
31. A data element with a specified data type that describes information associated with a concept or entity.
Attribute
Unified Modeling Language (UML)
Cardinality
Association
32. Work carried out or on behalf of others.
Service
Event
Domain Subject Matter Expert (SME)
Requirements Signoff
33. The work that must be performed to deliver a product service or result with the specified features and functions.
Functional Requirement(s)
Project Scope
Defect
Transition Requirement(s)
34. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Problem Statement
Variance Analysis
Requirements Allocation
Evolutionary Prototype
35. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Competitive Analysis
Activity
Business Constraint(s)
36. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Domain
Problem Statement
Regulator
Request For Information (RFI)
37. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode
Request For Quote (RFQ)
Requirements Management
Business Domain Model
Relationship
38. A type of data model that depicts information groups as classes.
Data Model
Class Model
Organizational Process Asset
Relationship
39. 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.
Business Analysis Approach
Throw-away Prototype
Use Case
Glossary
40. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Organizational Process Asset
User Requirements Document
Developer
41. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Request For Information (RFI)
Glossary
Project Manager
Requirements Model
42. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Quality Assurance
Customer
Organizational Readiness Assessment
Plan-driven Methodology
43. Any recognized association of people in the context of an organization or enterprise.
Requirements Management Tool
Decomposition
Requirements Model
Organizational Unit
44. A function of an organization that enables it to achieve a business goal or objective.
Problem Statement
Product Backlog
Enterprise Architecture
Capability
45. 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.
User
User Story
Business Need(s)
Activity Diagram
46. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Technique
Functional Requirement(s)
Desired Outcome
Business Requirements Document
47. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Optionality
Attribute
Change-driven Methodology
Secondary Actor
48. An analysis model that shows user interface dialogs arranged as hierarchies.
Requirements Signoff
Quality
Dialog Hierarchy
Model(s)
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
Design Constraints
Business Need(s)
Change-driven Methodology
50. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Requirement(s) Defect
Event
Association
Use Case