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. The set of capabilities a solution must deliver in order to meet the business need.
Solution Scope
Root Cause Analysis
State Diagram
Vision Statement (product vision statement)
2. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Data Dictionary
Decision Analysis
Tester
Prioritization
3. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Prioritization
Work Product
Exploratory Prototype
Timebox
4. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Business Event
Context Diagram
Repository
Defect
5. 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
Impact Analysis
Functional Requirement(s)
Class
Customer
6. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Evolutionary Prototype
Requirement
Relationship Map
Metadata
7. A practitioner of business analysis.
Developer
Business Analyst
Business Analysis Plan
Swimlane
8. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Swimlane
Requirements Validation
Software/Systems Requirements Specification
Organizational Readiness Assessment
9. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Tester
Decision Analysis
Business Process
Business Requirement
10. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Project Scope
Peer Review
Supplier
Change-driven Methodology
11. 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.
Project Manager
User Acceptance Test
Return on Investment
Vertical Prototype
12. An analysis model that shows user interface dialogs arranged as hierarchies.
Checklist
Data Entity
Organizational Readiness Assessment
Dialog Hierarchy
13. A measure of the profitability of a project or investment.
Use Case
Return on Investment
Decomposition
Verification
14. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Data Flow Diagram (DFD)
Requirements Iteration
Enterprise Architecture
Dialog Map
15. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
SWOT Analysis
Requirement(s) Defect
Organizational Process Asset
Walkthrough
16. All materials used by groups within an organization to define tailor implement and maintain their processes.
Interoperability
Temporal Event
Organizational Process Asset
Indicator
17. 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.
Constraint
Class Model
Business Need(s)
Process Model
18. A type of data model that depicts information groups as classes.
Organizational Readiness Assessment
Project Charter
Class Model
Observation
19. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Horizontal Prototype
Brainstorming
Methodology
Plan-driven Methodology
20. 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 Domain Model
State Diagram
Structured Walkthrough
Operational Support
21. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Product Backlog
Data Model
Solution
Product
22. 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.
Organization
Process Model
Requirements Verification
Requirements Traceability
23. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Business Rule(s)
Impact Analysis
Opportunity Analysis
Requirements Package
24. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Solution
Requirements Validation
Data Dictionary
25. The human and nonhuman roles that interact with the system.
Association
User Requirements Document
Actor(s)
Software/Systems Requirements Specification
26. 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.
Class Model
Iteration
Force Field Analysis
Feasibility Study
27. An analysis model that illustrates the architecture of the system's user interface.
Validation
Secondary Actor
Dialog Map
Prototype
28. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Span of Control
Business Requirements Document
Document Analysis
Decision Tree
29. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Technique
Project Charter
Customer
30. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Entity-Relationship Diagram
Quality Assurance
Decision Tree
Feature
31. Limitations on the design of a solution that derive from the technology used in its implementation.
SWOT Analysis
Black Box Tests
Object Oriented Modeling
Technical Constraint(s)
32. A temporary endeavor undertaken to create a unique product service or result.
Project
Business Case
Business Analyst
Cardinality
33. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Gap Analysis
SWOT Analysis
Data Model
Requirements Management
34. 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
Constraint
Stakeholder Requirement
Use Case
35. 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.
Relationship
Verification
Evaluation
Product Backlog
36. 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.
Vertical Prototype
Commercial-off-the-Shelf Software (COTS)
Use Case
Indicator
37. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Enterprise Architecture
Defect
Data Entity
Technical Constraint(s)
38. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.
Competitive Analysis
Requirements Traceability
Business Analysis Communication Plan
Commercial-off-the-Shelf Software (COTS)
39. 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.
Verification
Validated Requirements
End User
Data Flow Diagram (DFD)
40. A structured examination of an identified problem to understand the underlying causes.
Supplier
Root Cause Analysis
Decision Tree
Requirements Risk Mitigation Strategy
41. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Organizational Unit
Benchmarking
Survey
Requirements Management Tool
42. 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.
Stakeholder Analysis
Vertical Prototype
Verified Requirements
Code
43. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Gap Analysis
Survey
Opportunity Analysis
Sponsor
44. The degree to which a set of inherent characteristics fulfills requirements.
Project Manager
Objective
Organization Modeling
Quality
45. 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.
Horizontal Prototype
Business Rule(s)
Feature
Association
46. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
State Diagram
Impact Analysis
Cost Benefit Analysis
Technique
47. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Class
Requirements Management
Interface
Data Entity
48. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
User Requirements Document
Association
Decision Tables
Stakeholder
49. A use case composed of a common set of steps used by multiple use cases.
Process Map
Assumption
Included Use Cases
Enterprise
50. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Repository
Tester
Included Use Cases
Business Requirements Document