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 model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Activity Diagram
Requirements Model
Requirements Trace Matrix
Requirement(s) Defect
2. 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.
Dialog Hierarchy
Requirements Traceability
Requirements Management Plan
Work Breakdown Structure (WBS)
3. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Observation
Unified Modeling Language (UML)
Interview
Cost Benefit Analysis
4. 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
Requirements Verification
Use Case
Metadata
Structural Rule
5. 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.
Attribute
Project
Requirements Management Plan
Elicitation
6. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Cost Benefit Analysis
Knowledge Area
Optionality
Tester
7. 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.
User Acceptance Test
Requirement(s) Defect
Work Breakdown Structure (WBS)
Objective
8. A stakeholder person device or system that directly or indirectly accesses a system.
User
Requirements Workshop
Desired Outcome
Requirements Management
9. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Requirements Model
Brainstorming
Requirements Workshop
Requirements Management Plan
10. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Stated Requirements
Request For Information (RFI)
Requirement(s) Attribute
Data Entity
11. A stakeholder who uses products or services delivered by an organization.
Stakeholder
Non-functional Requirement(s)
Organizational Readiness Assessment
Customer
12. 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
Use Case
Business Analysis
Organization
13. 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.
Requirement(s) Defect
Requirements Management Tool
Force Field Analysis
User Acceptance Test
14. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Timebox
Change-driven Methodology
Included Use Cases
Repository
15. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Change-driven Methodology
Use Case
Stakeholder Analysis
Vertical Prototype
16. 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.
Requirement
Benchmarking
Business Architecture
Design Constraints
17. 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
Gap Analysis
Initiative
Requirements Management
18. An analysis model that illustrates the architecture of the system's user interface.
Requirement
Business Analysis Approach
Dialog Map
Brainstorming
19. Software developed and sold for a particular market.
Project Scope
Validated Requirements
Commercial-off-the-Shelf Software (COTS)
Requirements Management Tool
20. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Product
Iteration
Software/Systems Requirements Specification
Business Event
21. 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.
Verification
Functional Requirement(s)
Force Field Analysis
Solution Scope
22. A link between two elements or objects in a diagram.
Process Map
Requirements Signoff
Business Domain Model
Association
23. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Requirements Verification
Requirements Workshop
Operative Rule(s)
24. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Data Flow Diagram (DFD)
Developer
Black Box Tests
Prototype
25. 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
Knowledge Area
Plan-driven Methodology
Operative Rule(s)
Span of Control
26. A type of data model that depicts information groups as classes.
Process Model
Class Model
Functional Requirement(s)
Prototype
27. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
User Story
Throw-away Prototype
Business Analysis Approach
28. Information that is used to understand the context and validity of information recorded in a system.
Requirements Management Tool
Interview
Metadata
Vertical Prototype
29. 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.
Glossary
Inspection
Use Case Diagram
Sequence Diagram
30. A prototype developed to explore or verify requirements.
Exploratory Prototype
Indicator
Requirements Management Plan
Validation
31. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Regulator
Business Event
Operative Rule(s)
Domain Subject Matter Expert (SME)
32. The number of employees a manger is directly (or indirectly) responsible for.
Product Scope
Objective
Use Case Diagram
Span of Control
33. An analysis model showing the life cycle of a data entity or class.
System
Capability
State Diagram
Object Oriented Modeling
34. 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)
Business Requirement
Project Charter
Scope Model
35. A system trigger that is initiated by time.
Technical Constraint(s)
Temporal Event
Constraint
Product Backlog
36. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Event Response Table
Methodology
Requirements Management Tool
Solution Scope
37. 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.
Context Diagram
Elicitation
Horizontal Prototype
Decision Tables
38. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Brainstorming
Request For Information (RFI)
Requirements Signoff
Quality Attributes
39. A system trigger that is initiated by humans.
Business Event
Design Constraints
Business Architecture
Business Analysis Approach
40. 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.
Iteration
Repository
Request For Proposal (RFP)
Project Charter
41. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Benchmarking
Requirements Validation
Entity-Relationship Diagram
Business Domain Model
42. A person with specific expertise in an area or domain under investigation.
Repository
Requirements Management Plan
Domain Subject Matter Expert (SME)
Fishbone Diagram
43. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Business Goal
User Story
Customer
Decision Tree
44. An assessment of the costs and benefits associated with a proposed initiative.
Regulator
Business Case
Project
Process Map
45. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Walkthrough
Code
Secondary Actor
Prioritization
46. Metadata related to a requirement used to assist with requirements development and management.
Work Product
Requirement(s) Attribute
Survey
External Interfaces
47. 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
Business Analysis Communication Plan
Exploratory Prototype
Peer Review
Organization
48. 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
Technical Constraint(s)
Business Event
Supplier
Class
49. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Domain
Model(s)
Requirements Validation
Structured Walkthrough
50. 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.
Commercial-off-the-Shelf Software (COTS)
Defect
Stakeholder Analysis
Force Field Analysis