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 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.
End User
Sequence Diagram
Validation
Solution
2. A fixed period of time to accomplish a desired outcome.
Timebox
Feature
Request For Proposal (RFP)
Context Diagram
3. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Plan-driven Methodology
Solution Scope
Solution Requirement
Baseline
4. 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
Class
Verification
Process Map
Transition Requirement(s)
5. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Defect
Prototype
Technique
6. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Assumption
Vision Statement (product vision statement)
Sponsor
Enterprise Architecture
7. 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.
Requirements Signoff
Business Process
Business Analysis Communication Plan
Cost Benefit Analysis
8. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Business Analyst
Competitive Analysis
Business Domain Model
Unified Modeling Language (UML)
9. 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
Impact Analysis
Change-driven Methodology
Business Requirements Document
10. A solution or component of a solution that is the result of a project.
Enterprise
Product
Requirements Management Plan
Requirements Management Tool
11. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Supplier
Decision Analysis
Requirements Risk Mitigation Strategy
12. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Change Control Board (CCB)
Business Analyst
Stakeholder List
Organizational Unit
13. 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.
Attribute
Validation
Product
Cost Benefit Analysis
14. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Observation
Swimlane
Business Analysis
Relationship
15. 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
Initiative
Request For Proposal (RFP)
Operative Rule(s)
Business Constraint(s)
16. 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.
Opportunity Analysis
Business Analysis Plan
Variance Analysis
Vertical Prototype
17. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Stakeholder Requirement
Methodology
Structured Walkthrough
Force Field Analysis
18. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Customer
Enterprise
Survey
Tester
19. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Objective
Brainstorming
Defect
Business Analyst
20. A state or condition the business must satisfy to reach its vision.
Implementation Subject Matter Expert (SME)
Business Goal
Stated Requirements
Business Analysis Plan
21. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Enterprise
Decision Tables
Temporal Event
22. A prototype developed to explore or verify requirements.
Quality Attributes
Organizational Readiness Assessment
Competitive Analysis
Exploratory Prototype
23. 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
Organization Modeling
Project Charter
Optionality
24. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Lessons Learned Process
Event Response Table
Customer
25. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Glossary
Request For Information (RFI)
Organizational Readiness Assessment
26. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Model(s)
Peer Review
Document Analysis
Use Case Diagram
27. The number of employees a manger is directly (or indirectly) responsible for.
Requirements Signoff
Project Manager
Stakeholder Analysis
Span of Control
28. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Feasibility Study
Verified Requirements
Scope Model
Request For Proposal (RFP)
29. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Verified Requirements
System
Secondary Actor
Brainstorming
30. An analysis model describing the data structures and attributes needed by the system.
Data Dictionary
Work Product
Business Analyst
Risk
31. 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
Exploratory Prototype
Requirements Package
Requirements Iteration
32. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Decision Tree
Implementation Subject Matter Expert (SME)
Unified Modeling Language (UML)
33. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Regulator
Subject Matter Expert (SME)
Change-driven Methodology
Class Model
34. A function of an organization that enables it to achieve a business goal or objective.
Plan-driven Methodology
Capability
User Requirements Document
Quality Attributes
35. The features and functions that characterize a product service or result.
Business Process
Requirements Iteration
Product Scope
Inspection
36. A unit of work performed as part of an initiative or process.
Decision Analysis
Requirements Verification
Activity
Request For Information (RFI)
37. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Data Flow Diagram (DFD)
Swimlane
Lessons Learned Process
38. 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.
Desired Outcome
Requirements Traceability
Developer
Vision Statement (product vision statement)
39. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Requirements Verification
Document Analysis
Evolutionary Prototype
Metadata
40. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Business Goal
Attribute
Developer
Structural Rule
41. 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
Structural Rule
Requirements Management Plan
Business Event
Object Oriented Modeling
42. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Solution Requirement
Project Charter
Request For Information (RFI)
Validated Requirements
43. 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.
Relationship
Requirements Validation
Validation
Process Map
44. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Temporal Event
Developer
Request For Proposal (RFP)
Business Requirements Document
45. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Class
Verified Requirements
Capability
46. Any recognized association of people in the context of an organization or enterprise.
Entity-Relationship Diagram
Solution
Organizational Unit
Request For Information (RFI)
47. A link between two elements or objects in a diagram.
Requirements Signoff
Association
Decomposition
Scope Model
48. A description of the requirements management process.
Exploratory Prototype
Prioritization
Requirements Management Plan
Requirements Management Tool
49. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Force Field Analysis
Inspection
Association
Requirements Management Tool
50. A group or person who has interests that may be affected by an initiative or influence over it.
Domain
Requirements Verification
Stakeholder
Prioritization