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 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
Project Manager
Business Goal
Solution Scope
Business Process
2. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Horizontal Prototype
Subject Matter Expert (SME)
Request For Proposal (RFP)
Repository
3. 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).
External Interfaces
Elicitation
Constraint
Cardinality
4. 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.
Enterprise Architecture
Analyst
Methodology
State Diagram
5. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Tester
Request For Proposal (RFP)
Organization
Prioritization
6. 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.
Verification
Product
Implementation Subject Matter Expert (SME)
Transition Requirement(s)
7. A shared boundary between any two persons and/or systems through which information is communicated.
Solution Requirement
Interface
Requirements Verification
Business Goal
8. A data element with a specified data type that describes information associated with a concept or entity.
Organizational Unit
Attribute
Dialog Hierarchy
Product Backlog
9. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Validation
User
Business Analysis Approach
Black Box Tests
10. 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
Stakeholder Requirement
Black Box Tests
Subject Matter Expert (SME)
Object Oriented Modeling
11. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Activity Diagram
Business Case
System
Requirement(s) Defect
12. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Vision Statement (product vision statement)
Plan-driven Methodology
Project
13. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Observation
Metric
Commercial-off-the-Shelf Software (COTS)
Tester
14. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Sequence Diagram
Vision Statement (product vision statement)
Non-functional Requirement(s)
Interview
15. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Risk
Service
Business Constraint(s)
Business Analysis Communication Plan
16. 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
Structural Rule
Class Model
Requirements Allocation
17. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Quality
Regulator
Solution Scope
Survey
18. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Decision Tables
Entity-Relationship Diagram
Optionality
Technique
19. An informal solicitation of proposals from vendors.
Request For Quote (RFQ)
Requirements Workshop
Business Analyst
Transition Requirement(s)
20. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirement
Decision Analysis
Requirements Signoff
Business Analysis Plan
21. Information that is used to understand the context and validity of information recorded in a system.
Requirements Management Tool
Horizontal Prototype
Metadata
Domain
22. A link between two elements or objects in a diagram.
Variance Analysis
Scope
Association
Business Requirements Document
23. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Optionality
Request For Quote (RFQ)
Requirements Risk Mitigation Strategy
Capability
24. 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.
Unified Modeling Language (UML)
Association
Supplier
Work Breakdown Structure (WBS)
25. Ability of systems to communicate by exchanging data or services.
Interview
Business Domain Model
Methodology
Interoperability
26. A state or condition the business must satisfy to reach its vision.
Relationship Map
Business Goal
Verification
Project Charter
27. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Actor(s)
Software/Systems Requirements Specification
Observation
Use Case Diagram
28. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality
Business Constraint(s)
Quality Assurance
Use Case
29. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
System
Requirement(s) Attribute
Organizational Process Asset
Fishbone Diagram
30. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Checklist
Domain
Requirements Iteration
Impact Analysis
31. 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
Organization
Fishbone Diagram
End User
Defect
32. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Gap Analysis
Defect
Cost Benefit Analysis
Requirements Package
33. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Product Backlog
Context Diagram
Operational Support
34. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Metadata
Project Manager
Gap Analysis
Scope Model
35. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Trace Matrix
Business Architecture
Requirements Package
Association
36. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Span of Control
Requirements Verification
Process Model
Glossary
37. All materials used by groups within an organization to define tailor implement and maintain their processes.
Business Architecture
Organizational Process Asset
Swimlane
Competitive Analysis
38. A group of related tasks that support a key function of business analysis.
Evolutionary Prototype
Event
Event Response Table
Knowledge Area
39. 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
End User
Decision Analysis
User Story
Structural Rule
40. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Cost Benefit Analysis
Peer Review
Work Product
Requirements Allocation
41. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.
Scope Model
Decision Tree
Event
Event Response Table
42. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Service
Work Product
Requirement(s) Attribute
Supplier
43. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Incremental Delivery
Prototype
User Requirements Document
Plan-driven Methodology
44. 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
Object Oriented Modeling
Span of Control
Organization
User
45. Any unique and verifiable work product or service that a party has agreed to deliver.
Stakeholder List
Entity-Relationship Diagram
Deliverable
Change Control Board (CCB)
46. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
State Diagram
Scope
Swimlane
Data Flow Diagram (DFD)
47. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Model(s)
Decision Analysis
Requirement
Verified Requirements
48. Any effort undertaken with a defined goal or objective.
Organizational Process Asset
Initiative
Use Case
Variance Analysis
49. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Knowledge Area
Decision Tree
Regulator
Problem Statement
50. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Business Analysis
Data Entity
State Diagram
End User