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 work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stated Requirements
Customer
Technique
Stakeholder Analysis
2. 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
Cost Benefit Analysis
Project
Elicitation
3. A prototype that is continuously modified and updated in response to feedback from users.
Commercial-off-the-Shelf Software (COTS)
Temporal Event
Evolutionary Prototype
Objective
4. 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
Requirements Management Plan
Verified Requirements
Span of Control
5. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Business Analysis Communication Plan
Event
Decision Tree
Model(s)
6. 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
Data Entity
Desired Outcome
Requirements Workshop
Request For Proposal (RFP)
7. A state or condition the business must satisfy to reach its vision.
Requirements Model
Feature
Business Goal
Peer Review
8. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Attribute
Operative Rule(s)
Quality
SWOT Analysis
9. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Work Product
Prioritization
Brainstorming
10. An actor who participates in but does not initiate a use case.
Secondary Actor
Deliverable
Process Map
User Story
11. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
User Requirements Document
Business Requirements Document
Business Policy
Context Diagram
12. Something that occurs to which an organizational unit system or process must respond.
Horizontal Prototype
Analyst
Event
Work Breakdown Structure (WBS)
13. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Event Response Table
Business Constraint(s)
Technical Constraint(s)
Metadata
14. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Cardinality
Relationship
Project Scope
Stakeholder Requirement
15. A fixed period of time to accomplish a desired outcome.
Business Analyst
Timebox
Class Model
Sequence Diagram
16. Ability of systems to communicate by exchanging data or services.
Gap Analysis
Interoperability
Timebox
Analyst
17. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Validated Requirements
Functional Requirement(s)
External Interfaces
Secondary Actor
18. Metadata related to a requirement used to assist with requirements development and management.
User Requirements Document
Requirement(s) Attribute
Organization
Dialog Hierarchy
19. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Survey
Throw-away Prototype
Analyst
Desired Outcome
20. An analysis model showing the life cycle of a data entity or class.
Risk
Requirements Package
State Diagram
Metadata
21. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Variance Analysis
Functional Requirement(s)
Implementation Subject Matter Expert (SME)
22. 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
Request For Information (RFI)
Constraint
Evolutionary Prototype
Solution
23. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Business Analysis
Developer
Assumption
Model(s)
24. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Scope
Sponsor
Requirements Package
Software/Systems Requirements Specification
25. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Project
Process Map
Use Case Diagram
Optionality
26. 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
Project
Object Oriented Modeling
Benchmarking
Stakeholder
27. Any recognized association of people in the context of an organization or enterprise.
Project Scope
Optionality
Customer
Organizational Unit
28. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Feature
Transition Requirement(s)
Sponsor
Object Oriented Modeling
29. 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.
Interoperability
Requirements Traceability
Business Analysis Approach
Requirements Management Tool
30. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Requirements Allocation
Solution Requirement
Competitive Analysis
Business Event
31. 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
Use Case Diagram
Project Manager
Dialog Map
32. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Organizational Readiness Assessment
Plan-driven Methodology
Interview
User Story
33. A function of an organization that enables it to achieve a business goal or objective.
Activity Diagram
Capability
Business Analysis Communication Plan
Requirements Validation
34. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Swimlane
End User
Cardinality
Relationship Map
35. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Developer
Data Flow Diagram (DFD)
Return on Investment
36. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Defect
Peer Review
Developer
Interview
37. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Data Model
Subject Matter Expert (SME)
User
Business Process
38. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Metric
Dialog Map
Entity-Relationship Diagram
Business Analysis
39. 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.
Interface
Operational Support
Stated Requirements
Repository
40. 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.
Requirements Package
Work Breakdown Structure (WBS)
Benchmarking
End User
41. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Domain Subject Matter Expert (SME)
Business Analysis Communication Plan
Transition Requirement(s)
Observation
42. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Tester
Verification
Exploratory Prototype
Organizational Process Asset
43. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Business Process
User Requirements Document
Functional Requirement(s)
Problem Statement
44. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Business Domain Model
Requirements Trace Matrix
Objective
Model(s)
45. The process of examining new business opportunities to improve organizational performance.
Feature
Design Constraints
Opportunity Analysis
Black Box Tests
46. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Desired Outcome
Decision Tree
Data Entity
User Acceptance Test
47. 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.
Activity Diagram
Structural Rule
Business Architecture
Work Breakdown Structure (WBS)
48. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Stakeholder
Tester
Methodology
External Interfaces
49. 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.
Repository
Interview
Iteration
Activity
50. 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
Walkthrough
Impact Analysis
Class
Organizational Readiness Assessment