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. 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.
Focus Group
Desired Outcome
Business Analysis Plan
Context Diagram
2. A fixed period of time to accomplish a desired outcome.
Subject Matter Expert (SME)
Metadata
Incremental Delivery
Timebox
3. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Customer
Cardinality
Scope Model
Project Charter
4. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
Requirements Workshop
Throw-away Prototype
Verification
Sponsor
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
Root Cause Analysis
Relationship Map
Class
Assumption
6. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Data Flow Diagram (DFD)
Metric
Project Scope
Implementation Subject Matter Expert (SME)
7. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
Requirements Iteration
Fishbone Diagram
Requirements Management Tool
Change-driven Methodology
8. 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.
Actor(s)
Analyst
Subject Matter Expert (SME)
Throw-away Prototype
9. The problem area undergoing analysis.
Stakeholder Analysis
Domain
Interoperability
Stakeholder
10. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Actor(s)
Assumption
Process Map
Stakeholder
11. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Project Scope
Validation
Sponsor
Solution Requirement
12. 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.
Evaluation
Verification
Enterprise Architecture
Non-functional Requirement(s)
13. 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.
Benchmarking
Competitive Analysis
Impact Analysis
User Acceptance Test
14. A person with specific expertise in an area or domain under investigation.
Technical Constraint(s)
Functional Requirement(s)
Vision Statement (product vision statement)
Domain Subject Matter Expert (SME)
15. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Risk
Event
Business Analysis Plan
Repository
16. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Requirements Workshop
Model(s)
User Requirements Document
Decomposition
17. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Elicitation
Evolutionary Prototype
Business Requirements Document
Verified Requirements
18. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Risk
Activity
Organizational Readiness Assessment
19. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Cost Benefit Analysis
Cardinality
Business Architecture
Business Requirement
20. The number of employees a manger is directly (or indirectly) responsible for.
Span of Control
SWOT Analysis
Business Constraint(s)
Deliverable
21. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Subject Matter Expert (SME)
Feasibility Study
Requirements Validation
Requirements Management Tool
22. 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.
Request For Information (RFI)
Interview
Activity
Enterprise Architecture
23. A system trigger that is initiated by humans.
Business Event
Requirements Package
Quality Assurance
Desired Outcome
24. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Included Use Cases
Business Rule(s)
Data Dictionary
25. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Business Goal
Cost Benefit Analysis
Assumption
Relationship Map
26. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Business Goal
Requirement
Business Policy
Project Manager
27. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Brainstorming
Dialog Hierarchy
Deliverable
Relationship Map
28. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Process Model
Defect
Requirements Trace Matrix
Project Charter
29. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Problem Statement
Monitoring
Design Constraints
Requirements Risk Mitigation Strategy
30. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Design Constraints
Span of Control
Work Breakdown Structure (WBS)
Technique
31. The human and nonhuman roles that interact with the system.
Feature
Actor(s)
Software/Systems Requirements Specification
Horizontal Prototype
32. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Product Scope
Requirement
Business Domain Model
Requirements Package
33. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Business Case
Relationship Map
Decomposition
Competitive Analysis
34. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Data Flow Diagram (DFD)
Stakeholder List
Throw-away Prototype
Vertical Prototype
35. The features and functions that characterize a product service or result.
Sponsor
Product Scope
Technique
Technical Constraint(s)
36. A prototype that dives into the details of the interface functionality or both.
Unified Modeling Language (UML)
Repository
Vertical Prototype
Analyst
37. 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
Force Field Analysis
Business Constraint(s)
User Requirements Document
Variance Analysis
38. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Business Domain Model
Requirements Verification
Solution Scope
39. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Product Scope
Transition Requirement(s)
Business Need(s)
Survey
40. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Flow Diagram (DFD)
Requirements Management Plan
Throw-away Prototype
Validated Requirements
41. A type of data model that depicts information groups as classes.
External Interfaces
Requirements Signoff
Impact Analysis
Class Model
42. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Use Case
Verification
Requirements Verification
Relationship
43. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various
Decision Tables
Association
Stakeholder Requirement
Optionality
44. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Project Manager
Desired Outcome
Capability
Monitoring
45. 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.
End User
Regulator
Design Constraints
Business Analysis
46. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Structured Walkthrough
Feasibility Study
Organization
Unified Modeling Language (UML)
47. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Requirements Management
Baseline
Organization Modeling
Unified Modeling Language (UML)
48. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Code
Constraint
Deliverable
Product
49. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Feature
Vision Statement (product vision statement)
Change Control Board (CCB)
Business Process
50. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Business Analysis Plan
Quality Assurance
Scenario
Structured Walkthrough