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. Work carried out or on behalf of others.
Operative Rule(s)
Business Requirement
Service
Cost Benefit Analysis
2. 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.
Solution Scope
Event Response Table
Structured Walkthrough
Elicitation
3. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Feature
Requirements Model
Stakeholder Requirement
Checklist
4. A non-actionable directive that supports a business goal.
Request For Proposal (RFP)
Enterprise
Business Policy
Baseline
5. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Objective
Business Analysis Approach
Benchmarking
Cost Benefit Analysis
6. 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.
User Acceptance Test
Model(s)
Subject Matter Expert (SME)
Benchmarking
7. 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.
Observation
Gap Analysis
Checklist
Activity
8. An analysis model showing the life cycle of a data entity or class.
State Diagram
Business Analysis
Requirement(s) Defect
Iteration
9. A stakeholder who provides products or services to an organization.
Span of Control
Supplier
Exploratory Prototype
Opportunity Analysis
10. 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
Vertical Prototype
Relationship Map
Interoperability
11. 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.
End User
Cost Benefit Analysis
Force Field Analysis
Use Case Diagram
12. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
Relationship
User
Span of Control
13. The work that must be performed to deliver a product service or result with the specified features and functions.
Defect
Quality Attributes
Model(s)
Project Scope
14. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
System
Sequence Diagram
Requirements Trace Matrix
Impact Analysis
15. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Product Backlog
Process Model
Data Dictionary
16. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Structured Walkthrough
Class Model
Baseline
External Interfaces
17. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Metric
Scope Model
Elicitation
18. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Commercial-off-the-Shelf Software (COTS)
Developer
Sponsor
Business Event
19. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Unified Modeling Language (UML)
Use Case
Requirements Risk Mitigation Strategy
20. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Entity-Relationship Diagram
Requirements Trace Matrix
Tester
Technical Constraint(s)
21. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Monitoring
Enterprise
Validated Requirements
User Acceptance Test
22. A prototype developed to explore or verify requirements.
Exploratory Prototype
Tester
Metadata
Organization Modeling
23. A fixed period of time to accomplish a desired outcome.
Timebox
Attribute
Opportunity Analysis
Incremental Delivery
24. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
State Diagram
Methodology
Requirements Workshop
Evolutionary Prototype
25. An informal solicitation of proposals from vendors.
Requirements Signoff
Request For Quote (RFQ)
Methodology
Evaluation
26. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
User Requirements Document
Desired Outcome
Business Analysis Approach
End User
27. Ability of systems to communicate by exchanging data or services.
Interview
Project Charter
Stakeholder Requirement
Interoperability
28. 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
Requirements Workshop
Project Scope
Cardinality
Business Architecture
29. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Organizational Readiness Assessment
Event Response Table
Interoperability
Dialog Map
30. 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
Quality
Throw-away Prototype
Event Response Table
31. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Plan-driven Methodology
Knowledge Area
Request For Quote (RFQ)
32. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
External Interfaces
Gap Analysis
Scope
Baseline
33. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Association
Quality Assurance
Solution Requirement
Customer
34. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Dialog Map
Risk
Elicitation
Evolutionary Prototype
35. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Quality
Requirements Risk Mitigation Strategy
End User
Change-driven Methodology
36. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
Monitoring
Timebox
User Acceptance Test
Class
37. A function of an organization that enables it to achieve a business goal or objective.
Request For Quote (RFQ)
Event
Prototype
Capability
38. A stakeholder person device or system that directly or indirectly accesses a system.
Organizational Process Asset
Impact Analysis
User
Included Use Cases
39. The quality attributes design and implementation constraints and external interfaces that the product must have.
Deliverable
Request For Quote (RFQ)
Non-functional Requirement(s)
User Story
40. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Knowledge Area
Requirements Model
Benchmarking
Evolutionary Prototype
41. 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.
Developer
Business Analysis Communication Plan
Requirement
Event
42. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Force Field Analysis
Organization Modeling
Business Goal
Repository
43. 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.
Desired Outcome
Software/Systems Requirements Specification
Evaluation
Sponsor
44. 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.
Temporal Event
Lessons Learned Process
Unified Modeling Language (UML)
Walkthrough
45. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
User
Vision Statement (product vision statement)
Force Field Analysis
Walkthrough
46. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Repository
Regulator
Relationship Map
Process Map
47. 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.
Technical Constraint(s)
Non-functional Requirement(s)
Implementation Subject Matter Expert (SME)
Repository
48. A link between two elements or objects in a diagram.
Requirements Management Plan
Variance Analysis
Association
User
49. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Peer Review
Document Analysis
Requirement
Domain
50. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Validation
Requirements Trace Matrix
Work Product
Scope