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 set of processes templates and activities that will be used to perform business analysis in a specific context.
Requirements Validation
Business Analysis Approach
Problem Statement
Scope
2. 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.
Customer
Software/Systems Requirements Specification
Use Case
Checklist
3. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Quality Attributes
Verified Requirements
Constraint
4. 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.
System
Entity-Relationship Diagram
Implementation Subject Matter Expert (SME)
Evolutionary Prototype
5. 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.
Regulator
Requirements Allocation
Product Scope
Business Analysis Communication Plan
6. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Decision Analysis
Glossary
Capability
Request For Quote (RFQ)
7. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Business Analyst
Interoperability
Metric
Lessons Learned Process
8. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Solution Requirement
Interview
Focus Group
Cost Benefit Analysis
9. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
System
Requirements Management Tool
Decomposition
Stakeholder Analysis
10. 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.
Business Process
Cost Benefit Analysis
Customer
Evaluation
11. A person with specific expertise in an area or domain under investigation.
Domain Subject Matter Expert (SME)
Business Policy
Requirement(s) Defect
Requirements Model
12. The degree to which a set of inherent characteristics fulfills requirements.
Incremental Delivery
Commercial-off-the-Shelf Software (COTS)
Throw-away Prototype
Quality
13. 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.
Requirement
Business Constraint(s)
Change-driven Methodology
Validation
14. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Solution
Activity
Defect
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
Data Flow Diagram (DFD)
Business Constraint(s)
Quality
Change-driven Methodology
16. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Initiative
Business Domain Model
Indicator
17. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Data Model
Subject Matter Expert (SME)
Use Case Diagram
18. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Sponsor
Interoperability
Use Case Diagram
Scenario
19. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Monitoring
Glossary
End User
Organization
20. A system trigger that is initiated by time.
Temporal Event
Requirements Package
Monitoring
Requirements Workshop
21. 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
Solution Scope
Baseline
Software/Systems Requirements Specification
Transition Requirement(s)
22. A model that defines the boundaries of a business domain or solution.
Exploratory Prototype
Scope Model
Verified Requirements
Quality Attributes
23. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Plan-driven Methodology
Requirements Validation
Request For Quote (RFQ)
Business Requirements Document
24. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Feasibility Study
Vertical Prototype
Vision Statement (product vision statement)
Tester
25. Any recognized association of people in the context of an organization or enterprise.
Event Response Table
Business Analysis Communication Plan
Organizational Readiness Assessment
Organizational Unit
26. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Fishbone Diagram
Design Constraints
User Story
27. An analysis model describing the data structures and attributes needed by the system.
Organization
Data Dictionary
Interoperability
Timebox
28. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Requirements Trace Matrix
Technique
Process Model
Technical Constraint(s)
29. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Business Analysis Plan
Optionality
Plan-driven Methodology
Exploratory Prototype
30. 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.
Business Analysis Plan
Secondary Actor
Developer
Requirements Allocation
31. 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.
User
Requirements Workshop
Quality Assurance
Stakeholder Requirement
32. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Use Case Diagram
Swimlane
Supplier
33. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Focus Group
Association
Requirements Trace Matrix
34. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Data Flow Diagram (DFD)
Context Diagram
Prioritization
Stakeholder
35. A measure of the profitability of a project or investment.
Interoperability
Root Cause Analysis
Return on Investment
Impact Analysis
36. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Capability
Deliverable
Business Event
Quality Attributes
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
Product
Requirements Validation
Requirements Iteration
Data Model
38. An analysis model showing the life cycle of a data entity or class.
Regulator
State Diagram
Gap Analysis
Knowledge Area
39. Any effort undertaken with a defined goal or objective.
Requirements Trace Matrix
Initiative
Tester
Prioritization
40. 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.
Service
Requirement
Solution
Indicator
41. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Gap Analysis
Structural Rule
Walkthrough
Business Architecture
42. A shared boundary between any two persons and/or systems through which information is communicated.
Interview
Interface
Decision Analysis
Dialog Hierarchy
43. A fixed period of time to accomplish a desired outcome.
Operative Rule(s)
Model(s)
Data Flow Diagram (DFD)
Timebox
44. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Requirements Validation
Product Backlog
Decomposition
Prototype
45. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Assumption
Functional Requirement(s)
Requirement
Plan-driven Methodology
46. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Requirements Management Plan
Incremental Delivery
Defect
Repository
47. The number of employees a manger is directly (or indirectly) responsible for.
Data Entity
Business Goal
Span of Control
Decision Tree
48. 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.
Business Event
Request For Quote (RFQ)
Temporal Event
Elicitation
49. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Business Event
Software/Systems Requirements Specification
Unified Modeling Language (UML)
Business Requirement
50. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Organization Modeling
Developer
Interface
Peer Review