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 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
Actor(s)
Operational Support
Black Box Tests
2. 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.
Return on Investment
Force Field Analysis
Interview
Technique
3. The quality attributes design and implementation constraints and external interfaces that the product must have.
Stakeholder Analysis
Interview
Non-functional Requirement(s)
User Requirements Document
4. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Validated Requirements
Process Model
User Story
Monitoring
5. 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.
Horizontal Prototype
Implementation Subject Matter Expert (SME)
Business Case
Structural Rule
6. Work carried out or on behalf of others.
Service
Commercial-off-the-Shelf Software (COTS)
Attribute
Unified Modeling Language (UML)
7. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Force Field Analysis
Interface
End User
8. A group of related tasks that support a key function of business analysis.
User Acceptance Test
Organization Modeling
Knowledge Area
Stakeholder Requirement
9. An analysis model describing the data structures and attributes needed by the system.
Vertical Prototype
Code
Variance Analysis
Data Dictionary
10. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Functional Requirement(s)
Metric
Opportunity Analysis
11. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Work Breakdown Structure (WBS)
Process Model
Scope
Solution
12. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Project Manager
Desired Outcome
Prototype
Problem Statement
13. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Structural Rule
Attribute
Desired Outcome
Change Control Board (CCB)
14. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Included Use Cases
Secondary Actor
Vertical Prototype
Monitoring
15. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Change-driven Methodology
Sponsor
Transition Requirement(s)
External Interfaces
16. 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
Decision Tree
Glossary
Operative Rule(s)
Process Model
17. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Dialog Hierarchy
User Story
Lessons Learned Process
Gap Analysis
18. A fixed period of time to accomplish a desired outcome.
Indicator
Class
Timebox
Requirements Validation
19. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Deliverable
User Story
Unified Modeling Language (UML)
20. 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
Validation
Stakeholder Analysis
Process Model
21. An analysis model that illustrates the architecture of the system's user interface.
Interface
Implementation Subject Matter Expert (SME)
Dialog Map
Association
22. A prototype that dives into the details of the interface functionality or both.
Observation
Capability
Business Analysis Plan
Vertical Prototype
23. 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
Knowledge Area
Technique
Work Breakdown Structure (WBS)
24. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Request For Information (RFI)
Model(s)
Domain Subject Matter Expert (SME)
Project
25. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Regulator
Plan-driven Methodology
Software/Systems Requirements Specification
Organization Modeling
26. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Baseline
User Acceptance Test
Actor(s)
Quality Attributes
27. 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.
Business Need(s)
Repository
SWOT Analysis
Document Analysis
28. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Checklist
Product Scope
Requirement
29. A stakeholder who provides products or services to an organization.
Feasibility Study
Requirement(s) Attribute
Supplier
System
30. A prototype that is continuously modified and updated in response to feedback from users.
Elicitation
Business Need(s)
Evolutionary Prototype
Product
31. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Interview
Metric
Use Case
Process Map
32. 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.
Requirements Allocation
Domain Subject Matter Expert (SME)
Feasibility Study
Enterprise
33. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Work Breakdown Structure (WBS)
Swimlane
Inspection
34. Metadata related to a requirement used to assist with requirements development and management.
Objective
Requirement(s) Attribute
Temporal Event
Context Diagram
35. A practitioner of business analysis.
Data Entity
Business Analyst
Business Analysis
Knowledge Area
36. 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) Attribute
Document Analysis
User Acceptance Test
Work Breakdown Structure (WBS)
37. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
User Requirements Document
System
Transition Requirement(s)
Inspection
38. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Business Goal
Gap Analysis
Solution
Vision Statement (product vision statement)
39. A use case composed of a common set of steps used by multiple use cases.
Stakeholder
Business Goal
Data Entity
Included Use Cases
40. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Product Backlog
Service
Business Goal
41. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Class
Validation
Methodology
Monitoring
42. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Event
Organizational Readiness Assessment
Deliverable
Focus Group
43. Any effort undertaken with a defined goal or objective.
Data Flow Diagram (DFD)
Interview
Organization Modeling
Initiative
44. 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
Return on Investment
User
Quality Attributes
45. An actor who participates in but does not initiate a use case.
Secondary Actor
Association
Project Manager
Activity Diagram
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.
Regulator
Gap Analysis
Requirements Management Plan
Decision Analysis
47. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Organizational Unit
Return on Investment
Glossary
Interview
48. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.
Organization
Stated Requirements
Checklist
Interoperability
49. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine
Business Architecture
Project Charter
Impact Analysis
Observation
50. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Metadata
Swimlane
Decision Tree
Implementation Subject Matter Expert (SME)