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 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).
Project Charter
Focus Group
Constraint
Operational Support
2. Work carried out or on behalf of others.
Solution Scope
Service
State Diagram
Cost Benefit Analysis
3. A description of the requirements management process.
Deliverable
User Story
Object Oriented Modeling
Requirements Management Plan
4. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Feasibility Study
Change-driven Methodology
Unified Modeling Language (UML)
Structural Rule
5. A prototype that dives into the details of the interface functionality or both.
User Acceptance Test
Vertical Prototype
Business Analysis Approach
Impact Analysis
6. 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.
Incremental Delivery
Requirements Management
Requirements Traceability
Cost Benefit Analysis
7. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Use Case
Problem Statement
Work Product
Event
8. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Exploratory Prototype
Methodology
Desired Outcome
Dialog Map
9. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Scope
Impact Analysis
User Story
Requirements Model
10. 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
Document Analysis
Object Oriented Modeling
Stakeholder
Glossary
11. Creating working software in multiple releases so the entire product is delivered in portions over time.
Incremental Delivery
Objective
Event Response Table
Benchmarking
12. The degree to which a set of inherent characteristics fulfills requirements.
Attribute
Evolutionary Prototype
Quality
User Acceptance Test
13. An assessment of the costs and benefits associated with a proposed initiative.
Class Model
Business Case
End User
Project Charter
14. The number of employees a manger is directly (or indirectly) responsible for.
Feasibility Study
Decision Tables
Requirements Verification
Span of Control
15. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Work Breakdown Structure (WBS)
Validated Requirements
Stakeholder Requirement
Elicitation
16. 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.
Commercial-off-the-Shelf Software (COTS)
Throw-away Prototype
Relationship Map
Product
17. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Timebox
Non-functional Requirement(s)
Class
18. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Change-driven Methodology
Scope
Functional Requirement(s)
Requirements Risk Mitigation Strategy
19. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Data Model
Requirements Management Plan
Optionality
Requirements Allocation
20. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Software/Systems Requirements Specification
Fishbone Diagram
Organizational Unit
Assumption
21. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Functional Requirement(s)
Project Manager
Stakeholder
Business Requirements Document
22. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Impact Analysis
Vision Statement (product vision statement)
Transition Requirement(s)
Black Box Tests
23. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Data Dictionary
Business Process
Business Event
Checklist
24. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Functional Requirement(s)
Objective
User
Problem Statement
25. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Project Charter
Activity Diagram
Cost Benefit Analysis
Enterprise
26. 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.
Unified Modeling Language (UML)
Stakeholder Analysis
Structured Walkthrough
Stated Requirements
27. 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.
Temporal Event
Functional Requirement(s)
Use Case Diagram
Decision Tables
28. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Black Box Tests
Business Constraint(s)
Technical Constraint(s)
Solution
29. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Request For Information (RFI)
Software/Systems Requirements Specification
Product
Survey
30. A function of an organization that enables it to achieve a business goal or objective.
Capability
Fishbone Diagram
Stated Requirements
Actor(s)
31. 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
Elicitation
Requirements Iteration
Business Analysis Plan
Request For Information (RFI)
32. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme
User Story
Lessons Learned Process
Requirements Verification
Project
33. 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.
Subject Matter Expert (SME)
Business Analysis Communication Plan
Business Domain Model
Work Breakdown Structure (WBS)
34. The problem area undergoing analysis.
Capability
Technique
External Interfaces
Domain
35. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Class
Iteration
Evaluation
36. 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.
Capability
Quality Assurance
Data Entity
Business Analysis Communication Plan
37. 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
Organization Modeling
Requirements Iteration
Swimlane
Class Model
38. 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
Solution Scope
Requirements Package
Project
39. The work that must be performed to deliver a product service or result with the specified features and functions.
Work Breakdown Structure (WBS)
Requirement(s) Attribute
Temporal Event
Project Scope
40. Formal approval of a set of requirements by a sponsor or other decision maker.
Metric
Validated Requirements
Metadata
Requirements Signoff
41. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Requirements Package
Business Analysis Plan
Requirements Validation
Change Control Board (CCB)
42. Any unique and verifiable work product or service that a party has agreed to deliver.
Constraint
User Story
Deliverable
Validation
43. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
System
Enterprise Architecture
Enterprise
Glossary
44. Ability of systems to communicate by exchanging data or services.
Iteration
Process Model
Requirement
Interoperability
45. 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
Change Control Board (CCB)
Non-functional Requirement(s)
Project Manager
46. A system of programming statements symbols and rules used to represent instructions to a computer.
Regulator
Root Cause Analysis
Tester
Code
47. 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.
Business Policy
User Acceptance Test
Requirements Management
Subject Matter Expert (SME)
48. 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.
Process Map
Vision Statement (product vision statement)
Business Goal
Brainstorming
49. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Vision Statement (product vision statement)
Dialog Map
Dialog Hierarchy
50. 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.
Requirements Package
Design Constraints
Implementation Subject Matter Expert (SME)
Data Model