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 collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Tester
Assumption
Dialog Hierarchy
System
2. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Business Requirements Document
Glossary
Assumption
Interface
3. 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
Class
Data Flow Diagram (DFD)
Commercial-off-the-Shelf Software (COTS)
Business Analysis Communication Plan
4. 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
Glossary
Operative Rule(s)
Interview
Relationship Map
5. A partial or preliminary version of the system.
Project
Technical Constraint(s)
Prototype
Developer
6. A system trigger that is initiated by humans.
Stakeholder Requirement
Organizational Unit
Organizational Readiness Assessment
Business Event
7. An analysis model that shows user interface dialogs arranged as hierarchies.
Decomposition
SWOT Analysis
Gap Analysis
Dialog Hierarchy
8. 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.
Interoperability
Context Diagram
Activity
Business Analysis Plan
9. A type of data model that depicts information groups as classes.
Class Model
Operative Rule(s)
Stakeholder List
Fishbone Diagram
10. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Functional Requirement(s)
Survey
Return on Investment
11. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Brainstorming
User
Competitive Analysis
Event
12. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Scope Model
Metric
Model(s)
Requirements Model
13. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Process Map
Solution Requirement
Organization
14. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Knowledge Area
Data Model
Requirement(s) Attribute
Baseline
15. 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
Design Constraints
Solution Scope
User Acceptance Test
16. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Scope Model
Fishbone Diagram
Transition Requirement(s)
Product Backlog
17. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Domain
Request For Information (RFI)
Business Analysis Plan
18. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Validation
Subject Matter Expert (SME)
Relationship Map
Domain Subject Matter Expert (SME)
19. A prototype that is continuously modified and updated in response to feedback from users.
Fishbone Diagram
Desired Outcome
Technique
Evolutionary Prototype
20. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Feature
Interoperability
Swimlane
21. 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.
Verified Requirements
Fishbone Diagram
Business Architecture
Brainstorming
22. The number of employees a manger is directly (or indirectly) responsible for.
Stakeholder Analysis
Span of Control
Business Constraint(s)
Verification
23. A stakeholder person device or system that directly or indirectly accesses a system.
Glossary
Iteration
User
Dialog Hierarchy
24. A specific actionable testable directive that is under the control of the business and supports a business policy.
Timebox
Use Case
Business Rule(s)
Dialog Hierarchy
25. 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.
Prioritization
Cost Benefit Analysis
Validation
Project
26. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Request For Information (RFI)
Customer
Requirements Trace Matrix
Peer Review
27. An analysis model showing the life cycle of a data entity or class.
Product Scope
Use Case Diagram
Enterprise Architecture
State Diagram
28. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Verification
Data Model
Assumption
Business Goal
29. A shared boundary between any two persons and/or systems through which information is communicated.
Verified Requirements
Interface
Business Case
Organization
30. The problem area undergoing analysis.
Black Box Tests
Decision Analysis
Scope
Domain
31. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Business Goal
Desired Outcome
Lessons Learned Process
Defect
32. 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
Problem Statement
Data Dictionary
Prototype
Request For Information (RFI)
33. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Object Oriented Modeling
Business Rule(s)
Attribute
Decision Tree
34. Any effort undertaken with a defined goal or objective.
Indicator
Unified Modeling Language (UML)
Document Analysis
Initiative
35. 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
Use Case
Class Model
Requirements Verification
Project Charter
36. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Verification
Impact Analysis
Enterprise
Sponsor
37. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Quality
Organizational Process Asset
Verification
External Interfaces
38. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Throw-away Prototype
Scenario
Process Model
Requirements Management Tool
39. The work that must be performed to deliver a product service or result with the specified features and functions.
User Requirements Document
Project Scope
Tester
Request For Information (RFI)
40. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Operational Support
Business Constraint(s)
Checklist
41. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Requirements Iteration
Prioritization
External Interfaces
Structural Rule
42. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Gap Analysis
Evaluation
Request For Proposal (RFP)
Business Process
43. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Structured Walkthrough
Requirements Model
Scenario
Requirement
44. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Business Need(s)
Included Use Cases
Work Product
Organizational Readiness Assessment
45. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
External Interfaces
Requirements Workshop
Vision Statement (product vision statement)
Class
46. 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.
State Diagram
Competitive Analysis
Business Requirement
Decision Analysis
47. 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
User Requirements Document
Capability
Business Domain Model
Business Requirement
48. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Business Requirements Document
Constraint
Business Analyst
Organization
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.
Lessons Learned Process
Feasibility Study
Business Architecture
Stakeholder List
50. A group of related tasks that support a key function of business analysis.
Vertical Prototype
Opportunity Analysis
Knowledge Area
Class