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. 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.
Decision Analysis
Design Constraints
Stated Requirements
Iteration
2. 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
Brainstorming
Solution Scope
Enterprise
3. Ability of systems to communicate by exchanging data or services.
Requirement(s) Defect
Interoperability
Requirement
Constraint
4. An analysis model describing the data structures and attributes needed by the system.
Structured Walkthrough
Solution Scope
Data Dictionary
Benchmarking
5. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Walkthrough
Objective
Prototype
Requirement(s) Defect
6. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Vertical Prototype
Scope Model
Monitoring
Dialog Map
7. A description of the requirements management process.
Business Analysis Approach
State Diagram
Vision Statement (product vision statement)
Requirements Management Plan
8. 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
Requirements Workshop
Use Case
Interview
9. 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
Requirements Risk Mitigation Strategy
Object Oriented Modeling
Business Architecture
Actor(s)
10. Any recognized association of people in the context of an organization or enterprise.
Business Analyst
Organizational Unit
Horizontal Prototype
Attribute
11. 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.
Organizational Process Asset
Change-driven Methodology
Work Breakdown Structure (WBS)
User Acceptance Test
12. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Methodology
Span of Control
Indicator
13. 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.
Solution
Data Entity
Feature
Product Backlog
14. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Requirement
Indicator
Structured Walkthrough
Interface
15. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Cost Benefit Analysis
Organizational Readiness Assessment
Product Scope
Activity Diagram
16. A prototype developed to explore or verify requirements.
Constraint
System
Exploratory Prototype
Requirements Verification
17. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
Business Requirements Document
Requirements Workshop
Requirements Traceability
Business Need(s)
18. A stakeholder person device or system that directly or indirectly accesses a system.
Plan-driven Methodology
Functional Requirement(s)
Baseline
User
19. A prototype that dives into the details of the interface functionality or both.
Project Charter
Focus Group
Walkthrough
Vertical Prototype
20. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Business Need(s)
Use Case Diagram
Project
Enterprise Architecture
21. 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 Trace Matrix
Incremental Delivery
Requirements Verification
User Acceptance Test
22. 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
Project
Enterprise
Relationship Map
23. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Prototype
Methodology
Structural Rule
Unified Modeling Language (UML)
24. 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.
Prioritization
Activity Diagram
Commercial-off-the-Shelf Software (COTS)
Fishbone Diagram
25. 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.
Requirements Verification
Class Model
Change-driven Methodology
Software/Systems Requirements Specification
26. A measure of the profitability of a project or investment.
SWOT Analysis
Return on Investment
Analyst
Glossary
27. A use case composed of a common set of steps used by multiple use cases.
Solution
Swimlane
Project Scope
Included Use Cases
28. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Class Model
Event
Decision Tree
Requirement
29. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Sequence Diagram
Data Flow Diagram (DFD)
Dialog Map
Focus Group
30. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Requirements Management Tool
Quality Attributes
Business Case
Product
31. A temporary endeavor undertaken to create a unique product service or result.
Stated Requirements
Peer Review
Project
Requirements Iteration
32. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
User Requirements Document
Monitoring
Sponsor
Business Analysis Communication Plan
33. 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
Force Field Analysis
Validation
34. The set of capabilities a solution must deliver in order to meet the business need.
Business Case
SWOT Analysis
Solution Scope
User
35. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Work Breakdown Structure (WBS)
Requirements Management Tool
Initiative
Competitive Analysis
36. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Verified Requirements
Use Case Diagram
Business Analysis Plan
Optionality
37. A link between two elements or objects in a diagram.
Requirements Iteration
Evaluation
Association
Enterprise Architecture
38. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Requirements Allocation
Requirement(s) Defect
Assumption
Requirements Signoff
39. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Scope Model
Optionality
Gap Analysis
Data Model
40. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Validation
Object Oriented Modeling
Regulator
Elicitation
41. 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.
Operative Rule(s)
Validation
Domain
Project Charter
42. 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.
Decomposition
Risk
Throw-away Prototype
Software/Systems Requirements Specification
43. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Feasibility Study
Evaluation
Requirements Risk Mitigation Strategy
Sponsor
44. A unit of work performed as part of an initiative or process.
Requirements Workshop
Domain
Activity
Business Process
45. Metadata related to a requirement used to assist with requirements development and management.
Decision Analysis
Requirement(s) Attribute
Requirements Management
Vertical Prototype
46. Software requirements that limit the options available to the system designer.
Project Manager
Design Constraints
Process Model
Lessons Learned Process
47. A solution or component of a solution that is the result of a project.
Product
Service
Exploratory Prototype
Business Constraint(s)
48. 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.
Gap Analysis
Verified Requirements
Knowledge Area
Decision Tables
49. An analysis model showing the life cycle of a data entity or class.
State Diagram
Included Use Cases
Organizational Process Asset
Requirements Management
50. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Data Model
Constraint
Business Analysis Plan
Objective