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 system of programming statements symbols and rules used to represent instructions to a computer.
Evaluation
Product Scope
Code
Verified Requirements
2. A structured examination of an identified problem to understand the underlying causes.
Context Diagram
Requirements Iteration
Root Cause Analysis
Organization
3. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Cost Benefit Analysis
Data Model
Quality Attributes
Objective
4. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Feasibility Study
Commercial-off-the-Shelf Software (COTS)
Initiative
Product Backlog
5. An analysis model that shows user interface dialogs arranged as hierarchies.
Organizational Readiness Assessment
Dialog Hierarchy
Validated Requirements
Data Dictionary
6. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Gap Analysis
Stated Requirements
Verification
Requirement(s) Defect
7. A model that defines the boundaries of a business domain or solution.
Solution
Scope Model
Monitoring
Class Model
8. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
Data Flow Diagram (DFD)
Survey
Competitive Analysis
9. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Brainstorming
Business Requirement
Work Product
Operative Rule(s)
10. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Quality
Sequence Diagram
Black Box Tests
11. A prototype that dives into the details of the interface functionality or both.
Project Scope
System
Requirement
Vertical Prototype
12. A specific actionable testable directive that is under the control of the business and supports a business policy.
Initiative
Business Rule(s)
Organization Modeling
Quality
13. 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
Organizational Unit
Developer
Object Oriented Modeling
Class
14. 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
Capability
Request For Proposal (RFP)
Risk
Requirement
15. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Requirements Trace Matrix
Prototype
End User
16. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Data Entity
Glossary
Fishbone Diagram
Commercial-off-the-Shelf Software (COTS)
17. Creating working software in multiple releases so the entire product is delivered in portions over time.
Data Dictionary
Activity Diagram
Prototype
Incremental Delivery
18. 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.
Iteration
Business Requirement
Decision Tables
Timebox
19. 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
Quality Attributes
Fishbone Diagram
Class
20. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Requirements Iteration
Work Breakdown Structure (WBS)
Focus Group
Requirements Allocation
21. 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.
Benchmarking
Root Cause Analysis
End User
Scope
22. A type of data model that depicts information groups as classes.
Competitive Analysis
Business Constraint(s)
Data Model
Class Model
23. A stakeholder who provides products or services to an organization.
Cardinality
Assumption
Problem Statement
Supplier
24. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Verification
Desired Outcome
Evaluation
Technical Constraint(s)
25. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Model(s)
Gap Analysis
Validated Requirements
Organizational Readiness Assessment
26. The features and functions that characterize a product service or result.
Product Scope
User Acceptance Test
Validation
Tester
27. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Root Cause Analysis
Vision Statement (product vision statement)
Stakeholder Requirement
Enterprise
28. The degree to which a set of inherent characteristics fulfills requirements.
Interface
Cardinality
Constraint
Quality
29. Something that occurs to which an organizational unit system or process must respond.
Developer
Operative Rule(s)
Cardinality
Event
30. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Focus Group
Timebox
Competitive Analysis
Requirements Validation
31. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
SWOT Analysis
Analyst
Requirements Model
Competitive Analysis
32. 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.
Solution Requirement
Glossary
User Acceptance Test
Validation
33. 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.
Evaluation
Structured Walkthrough
Capability
Checklist
34. The problem area undergoing analysis.
Document Analysis
Brainstorming
Domain
Relationship
35. 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.
Organizational Unit
Horizontal Prototype
System
Black Box Tests
36. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Dialog Map
Metadata
Requirements Management Tool
37. A description of the requirements management process.
Requirements Verification
Secondary Actor
Brainstorming
Requirements Management Plan
38. An analysis model that illustrates the architecture of the system's user interface.
Dialog Map
Swimlane
Activity
Impact Analysis
39. The work that must be performed to deliver a product service or result with the specified features and functions.
Baseline
Cost Benefit Analysis
Project Scope
Enterprise Architecture
40. A state or condition the business must satisfy to reach its vision.
Enterprise
Data Dictionary
Root Cause Analysis
Business Goal
41. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Gap Analysis
Timebox
Relationship
Subject Matter Expert (SME)
42. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Subject Matter Expert (SME)
Decision Tables
Lessons Learned Process
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.
Competitive Analysis
Feasibility Study
Prototype
Subject Matter Expert (SME)
44. 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.
Elicitation
Interview
Verified Requirements
Verification
45. 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
Business Analysis
Business Domain Model
Quality Assurance
Non-functional Requirement(s)
46. 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
Throw-away Prototype
Organizational Readiness Assessment
Decision Tables
47. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Impact Analysis
Product Scope
Product Backlog
Requirements Trace Matrix
48. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Horizontal Prototype
Relationship Map
Vertical Prototype
Problem Statement
49. 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.
Methodology
Stakeholder List
Business Policy
Timebox
50. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Deliverable
Subject Matter Expert (SME)
Solution Scope
Indicator