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 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.
Verified Requirements
Evaluation
Checklist
Gap Analysis
2. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Business Architecture
SWOT Analysis
Methodology
3. A fixed period of time to accomplish a desired outcome.
Root Cause Analysis
Timebox
Use Case
Indicator
4. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Document Analysis
Methodology
Business Requirements Document
Requirements Trace Matrix
5. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Optionality
Use Case
Non-functional Requirement(s)
6. A state or condition the business must satisfy to reach its vision.
Technical Constraint(s)
Business Analyst
Business Goal
Event
7. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Association
Requirements Management
Requirements Trace Matrix
System
8. Ability of systems to communicate by exchanging data or services.
Methodology
Exploratory Prototype
Interoperability
Capability
9. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Assumption
Scope Model
Enterprise Architecture
10. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Customer
Analyst
Baseline
Project Manager
11. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Document Analysis
External Interfaces
Relationship
Sponsor
12. 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.
Elicitation
Cost Benefit Analysis
Supplier
Business Need(s)
13. 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.
Analyst
Model(s)
Checklist
Technique
14. A structured examination of an identified problem to understand the underlying causes.
Timebox
Domain
Project Manager
Root Cause Analysis
15. 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
Stakeholder
Horizontal Prototype
Commercial-off-the-Shelf Software (COTS)
Stakeholder Requirement
16. An actor who participates in but does not initiate a use case.
Glossary
Defect
Secondary Actor
Transition Requirement(s)
17. Any unique and verifiable work product or service that a party has agreed to deliver.
End User
Domain Subject Matter Expert (SME)
Deliverable
Business Case
18. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
User Story
Decision Tree
Work Breakdown Structure (WBS)
Product
19. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Plan-driven Methodology
User Story
Business Policy
Model(s)
20. 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
Black Box Tests
Timebox
Business Analysis Plan
21. Any recognized association of people in the context of an organization or enterprise.
Subject Matter Expert (SME)
Organizational Readiness Assessment
Organizational Unit
Business Analysis Plan
22. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Requirements Management
Model(s)
Requirements Iteration
Process Model
23. 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
Product
Requirements Verification
Change Control Board (CCB)
Business Domain Model
24. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Design Constraints
Project Manager
Software/Systems Requirements Specification
Observation
25. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
User Story
Exploratory Prototype
SWOT Analysis
Business Process
26. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Business Analysis Approach
Technique
Work Product
Plan-driven Methodology
27. 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 Risk Mitigation Strategy
Design Constraints
Requirements Signoff
Requirements Model
28. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Requirements Verification
Work Product
Checklist
Operative Rule(s)
29. Software requirements that limit the options available to the system designer.
Business Requirements Document
Design Constraints
Brainstorming
Work Product
30. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Supplier
Business Analysis Approach
Temporal Event
Business Requirements Document
31. 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
Lessons Learned Process
Requirements Model
Desired Outcome
Actor(s)
32. 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
Objective
Business Process
Decision Analysis
Quality Attributes
33. A person with specific expertise in an area or domain under investigation.
Domain Subject Matter Expert (SME)
Feasibility Study
Attribute
Lessons Learned Process
34. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Risk
Fishbone Diagram
Optionality
Business Analysis Plan
35. An informal solicitation of proposals from vendors.
Solution
Attribute
Desired Outcome
Request For Quote (RFQ)
36. 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.
Business Need(s)
Business Analysis Approach
Walkthrough
Implementation Subject Matter Expert (SME)
37. 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
Product
Requirements Validation
Quality Attributes
38. 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
Organizational Readiness Assessment
Requirements Iteration
Inspection
Requirement(s) Defect
39. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Code
Focus Group
Impact Analysis
Document Analysis
40. A system trigger that is initiated by time.
Requirement
Temporal Event
Business Analyst
Repository
41. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Opportunity Analysis
Code
Document Analysis
Repository
42. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
Context Diagram
Baseline
System
Dialog Hierarchy
43. 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.
Included Use Cases
Focus Group
Requirement
Dialog Map
44. The quality attributes design and implementation constraints and external interfaces that the product must have.
Decision Tables
Entity-Relationship Diagram
Non-functional Requirement(s)
Requirements Validation
45. The area covered by a particular activity or topic of interest.
Included Use Cases
Scope
Requirements Model
Monitoring
46. A description of the requirements management process.
Event
Solution Scope
Business Architecture
Requirements Management Plan
47. 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.
Business Analysis Communication Plan
Evaluation
Lessons Learned Process
Functional Requirement(s)
48. A link between two elements or objects in a diagram.
Glossary
Tester
Requirements Validation
Association
49. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Business Analysis Plan
Data Dictionary
Functional Requirement(s)
50. A prototype developed to explore or verify requirements.
Use Case
Business Policy
Technique
Exploratory Prototype