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 uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Assumption
Decision Tables
Risk
Request For Information (RFI)
2. A type of data model that depicts information groups as classes.
Class Model
Relationship
External Interfaces
Project Scope
3. A structured examination of an identified problem to understand the underlying causes.
Stakeholder
Requirement
Business Need(s)
Root Cause Analysis
4. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Business Process
Domain Subject Matter Expert (SME)
Project Charter
Benchmarking
5. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.
Functional Requirement(s)
Walkthrough
Temporal Event
Validation
6. Software requirements that limit the options available to the system designer.
Solution Requirement
Transition Requirement(s)
Iteration
Design Constraints
7. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
Evaluation
Inspection
Incremental Delivery
Vertical Prototype
8. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Requirements Iteration
Organizational Unit
Project
Business Analysis Approach
9. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Organizational Readiness Assessment
Requirements Model
SWOT Analysis
Organizational Process Asset
10. 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
Business Requirement
Competitive Analysis
Organization
Product
11. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Requirement(s) Attribute
Optionality
Quality Assurance
Methodology
12. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Enterprise
Interview
Gap Analysis
Metric
13. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Exploratory Prototype
Operational Support
Data Entity
Solution Requirement
14. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Repository
Gap Analysis
Activity
End User
15. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Enterprise
Prioritization
Scenario
Assumption
16. 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).
Metadata
Enterprise
Operational Support
Requirements Allocation
17. 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.
Business Event
Verified Requirements
Sponsor
Throw-away Prototype
18. 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.
Customer
Use Case Diagram
Implementation Subject Matter Expert (SME)
Competitive Analysis
19. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Optionality
Interface
Requirements Allocation
Fishbone Diagram
20. A function of an organization that enables it to achieve a business goal or objective.
Operational Support
Root Cause Analysis
Capability
Glossary
21. A stakeholder who uses products or services delivered by an organization.
Change-driven Methodology
Customer
Business Analysis Approach
User Requirements Document
22. A use case composed of a common set of steps used by multiple use cases.
Technique
Included Use Cases
Baseline
Vertical Prototype
23. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Indicator
Timebox
Work Product
24. 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 Trace Matrix
Domain
Brainstorming
Requirements Workshop
25. Ability of systems to communicate by exchanging data or services.
Vision Statement (product vision statement)
Class
Interoperability
Secondary Actor
26. 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.
Benchmarking
Scope Model
Process Map
Lessons Learned Process
27. 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
Dialog Hierarchy
Non-functional Requirement(s)
Business Domain Model
Requirements Allocation
28. The features and functions that characterize a product service or result.
Competitive Analysis
Evaluation
Association
Product Scope
29. 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.
Observation
Interview
Activity
Decision Tables
30. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Quality
Impact Analysis
Repository
Feasibility Study
31. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Vision Statement (product vision statement)
Indicator
Iteration
Commercial-off-the-Shelf Software (COTS)
32. 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
Request For Quote (RFQ)
Business Requirements Document
Metadata
33. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Elicitation
Unified Modeling Language (UML)
Cardinality
34. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Enterprise Architecture
Variance Analysis
Desired Outcome
Business Analysis Communication Plan
35. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Interoperability
Process Model
Enterprise Architecture
Change-driven Methodology
36. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Objective
Survey
User
37. 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
Focus Group
Metadata
Dialog Hierarchy
Operative Rule(s)
38. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Opportunity Analysis
SWOT Analysis
Relationship
39. 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
Monitoring
Business Architecture
Capability
Technical Constraint(s)
40. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Requirements Risk Mitigation Strategy
External Interfaces
Organization
Attribute
41. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Functional Requirement(s)
Brainstorming
Feature
End User
42. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Customer
SWOT Analysis
Observation
Optionality
43. 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
Regulator
User Story
Return on Investment
Business Need(s)
44. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Object Oriented Modeling
Requirement
Activity Diagram
45. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Cost Benefit Analysis
Decomposition
Activity
Risk
46. An analysis model showing the life cycle of a data entity or class.
Validation
State Diagram
Brainstorming
Project Manager
47. Creating working software in multiple releases so the entire product is delivered in portions over time.
Incremental Delivery
Work Breakdown Structure (WBS)
Interface
Validation
48. 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
Stakeholder List
Organizational Process Asset
Business Requirements Document
Requirements Iteration
49. 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.
Regulator
Stated Requirements
Organizational Readiness Assessment
Event
50. A stakeholder person device or system that directly or indirectly accesses a system.
Non-functional Requirement(s)
Business Policy
Indicator
User