SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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 work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Scope
Requirements Model
Structured Walkthrough
2. 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.
Problem Statement
Repository
Focus Group
Design Constraints
3. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Sequence Diagram
Peer Review
Secondary Actor
Lessons Learned Process
4. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Decomposition
Requirements Management Tool
User Story
Entity-Relationship Diagram
5. A data element with a specified data type that describes information associated with a concept or entity.
Attribute
Business Architecture
Domain Subject Matter Expert (SME)
Business Need(s)
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.
Benchmarking
Requirement
Requirements Risk Mitigation Strategy
Code
7. 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.
Business Constraint(s)
Prioritization
Iteration
Work Breakdown Structure (WBS)
8. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Relationship
Request For Proposal (RFP)
Checklist
Stated Requirements
9. 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.
Analyst
Stakeholder List
End User
Requirements Workshop
10. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
User Requirements Document
Requirement
Stated Requirements
Actor(s)
11. 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.
Project Scope
Walkthrough
Swimlane
Requirement(s) Attribute
12. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Operational Support
Enterprise Architecture
Requirements Validation
Software/Systems Requirements Specification
13. 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
Secondary Actor
Organization Modeling
Business Analysis Plan
14. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Timebox
Plan-driven Methodology
Data Flow Diagram (DFD)
Solution Requirement
15. 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.
Document Analysis
Requirements Traceability
Commercial-off-the-Shelf Software (COTS)
Requirement
16. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Requirements Management Tool
Solution Requirement
Quality Assurance
Vision Statement (product vision statement)
17. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Requirements Model
SWOT Analysis
Work Product
Project Manager
18. A model that defines the boundaries of a business domain or solution.
Developer
Scope Model
Elicitation
Decomposition
19. The quality attributes design and implementation constraints and external interfaces that the product must have.
Event Response Table
Stakeholder Requirement
Non-functional Requirement(s)
Process Map
20. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Quality
Business Architecture
Monitoring
Data Entity
21. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Requirements Iteration
Requirements Allocation
Actor(s)
Use Case Diagram
22. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Domain
Requirements Management Tool
Business Analysis Communication Plan
23. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Requirements Package
Activity Diagram
Prototype
State Diagram
24. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Requirements Signoff
Business Requirements Document
Service
Checklist
25. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Indicator
User Requirements Document
Requirements Management
Association
26. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Span of Control
Baseline
Project Scope
27. 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
Model(s)
Survey
Functional Requirement(s)
Business Process
28. The set of capabilities a solution must deliver in order to meet the business need.
Enterprise
Organizational Process Asset
Solution Scope
Requirements Risk Mitigation Strategy
29. 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
Customer
Prototype
Object Oriented Modeling
Incremental Delivery
30. An assessment of the costs and benefits associated with a proposed initiative.
Association
Product Backlog
Survey
Business Case
31. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Requirements Allocation
Vision Statement (product vision statement)
Software/Systems Requirements Specification
Exploratory Prototype
32. A system trigger that is initiated by time.
Business Architecture
Enterprise Architecture
Document Analysis
Temporal Event
33. 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
Interface
Checklist
Business Policy
34. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Product Backlog
User Story
Requirements Trace Matrix
Quality
35. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Benchmarking
Checklist
Assumption
Feasibility Study
36. The product capabilities or things the product must do for its users.
Validated Requirements
Functional Requirement(s)
Business Analysis Approach
Stakeholder List
37. Something that occurs to which an organizational unit system or process must respond.
Technique
Event
Gap Analysis
Requirements Model
38. A function of an organization that enables it to achieve a business goal or objective.
Capability
Survey
Implementation Subject Matter Expert (SME)
External Interfaces
39. 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.
Observation
Stakeholder Analysis
Iteration
Requirements Traceability
40. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Project Charter
Document Analysis
Variance Analysis
Solution
41. A unit of work performed as part of an initiative or process.
Stakeholder
Activity
Change-driven Methodology
Business Architecture
42. 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
Design Constraints
Business Process
Swimlane
Stakeholder Requirement
43. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Validation
Lessons Learned Process
Desired Outcome
External Interfaces
44. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Change Control Board (CCB)
Defect
Tester
Opportunity Analysis
45. 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.
Plan-driven Methodology
Assumption
Checklist
Stakeholder
46. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Context Diagram
Methodology
Requirements Workshop
Cost Benefit Analysis
47. 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 Need(s)
Product
Enterprise Architecture
Business Analysis Plan
48. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Business Domain Model
Evolutionary Prototype
Request For Quote (RFQ)
Glossary
49. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Context Diagram
Code
Business Constraint(s)
Quality Assurance
50. The number of employees a manger is directly (or indirectly) responsible for.
Span of Control
Checklist
Enterprise Architecture
Scope