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. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Verification
Impact Analysis
Observation
Indicator
2. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Sponsor
Regulator
Business Analyst
3. A link between two elements or objects in a diagram.
Association
Change-driven Methodology
Use Case
Timebox
4. A non-actionable directive that supports a business goal.
Plan-driven Methodology
Lessons Learned Process
Business Policy
Business Analyst
5. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Quality Attributes
Functional Requirement(s)
Requirement
User
6. 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
Stated Requirements
Problem Statement
Stakeholder Requirement
Defect
7. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Regulator
Constraint
Assumption
Dialog Map
8. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Inspection
Metadata
Tester
Monitoring
9. 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.
End User
Metadata
Objective
Business Analysis Communication Plan
10. A practitioner of business analysis.
Focus Group
Stakeholder Requirement
Business Analyst
Variance Analysis
11. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Peer Review
External Interfaces
Stakeholder Analysis
12. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Requirements Package
Functional Requirement(s)
System
13. 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
Domain
Survey
Business Architecture
Risk
14. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Requirements Traceability
Supplier
Secondary Actor
Baseline
15. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Supplier
Work Product
Customer
Requirements Allocation
16. 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.
Model(s)
Document Analysis
Requirements Management Plan
Walkthrough
17. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
System
Risk
Requirements Trace Matrix
Throw-away Prototype
18. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Business Analysis
Project
Force Field Analysis
Evolutionary Prototype
19. A system trigger that is initiated by time.
Plan-driven Methodology
Technical Constraint(s)
Non-functional Requirement(s)
Temporal Event
20. The quality attributes design and implementation constraints and external interfaces that the product must have.
Business Analysis Plan
Non-functional Requirement(s)
Gap Analysis
Implementation Subject Matter Expert (SME)
21. A description of the requirements management process.
Validation
Technique
Requirements Management Plan
User
22. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Attribute
Code
Brainstorming
Business Event
23. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Validation
Requirements Model
Process Model
Requirements Signoff
24. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Service
Event Response Table
Commercial-off-the-Shelf Software (COTS)
25. The human and nonhuman roles that interact with the system.
Solution Requirement
Project Charter
Validation
Actor(s)
26. A stakeholder who uses products or services delivered by an organization.
Solution
Relationship Map
Structural Rule
Customer
27. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Business Analysis Plan
Feature
Checklist
28. A type of data model that depicts information groups as classes.
Class Model
Class
Business Domain Model
System
29. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Tester
Initiative
Data Flow Diagram (DFD)
Non-functional Requirement(s)
30. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Elicitation
Interoperability
Commercial-off-the-Shelf Software (COTS)
Business Need(s)
31. A group of related tasks that support a key function of business analysis.
Knowledge Area
Transition Requirement(s)
Stated Requirements
User Acceptance Test
32. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Relationship
Request For Quote (RFQ)
Requirements Verification
33. 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
Relationship Map
End User
Lessons Learned Process
Organization
34. 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.
Use Case Diagram
Validation
Product Backlog
Requirements Risk Mitigation Strategy
35. Formal approval of a set of requirements by a sponsor or other decision maker.
Scenario
Activity
Requirements Verification
Requirements Signoff
36. Metadata related to a requirement used to assist with requirements development and management.
Structural Rule
Business Requirement
Business Domain Model
Requirement(s) Attribute
37. A group or person who has interests that may be affected by an initiative or influence over it.
Requirement
Stakeholder
Observation
Context Diagram
38. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
Change Control Board (CCB)
Customer
External Interfaces
39. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Actor(s)
Customer
Requirements Package
Capability
40. An assessment of the costs and benefits associated with a proposed initiative.
Solution Scope
Software/Systems Requirements Specification
Business Case
Solution Requirement
41. An informal solicitation of proposals from vendors.
Span of Control
Attribute
Request For Quote (RFQ)
Optionality
42. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Root Cause Analysis
Requirements Management Plan
Association
Process Model
43. 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
Stakeholder Requirement
Variance Analysis
Walkthrough
44. A stakeholder who provides products or services to an organization.
Supplier
Lessons Learned Process
Business Architecture
Optionality
45. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Requirements Management
Product
Iteration
Association
46. A specific actionable testable directive that is under the control of the business and supports a business policy.
Impact Analysis
Requirements Trace Matrix
Objective
Business Rule(s)
47. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Work Breakdown Structure (WBS)
Methodology
Elicitation
Benchmarking
48. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Organization
Interview
Requirements Management Plan
Developer
49. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Regulator
Requirements Trace Matrix
Prioritization
Business Policy
50. A use case composed of a common set of steps used by multiple use cases.
Process Model
Included Use Cases
Brainstorming
Requirements Management Tool