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. A shared boundary between any two persons and/or systems through which information is communicated.
Checklist
Business Requirements Document
Interface
Software/Systems Requirements Specification
2. A partial or preliminary version of the system.
Secondary Actor
Fishbone Diagram
Prototype
Implementation Subject Matter Expert (SME)
3. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Exploratory Prototype
Business Requirement
Competitive Analysis
Solution
4. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Unified Modeling Language (UML)
Requirement
Glossary
Stakeholder List
5. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Repository
Variance Analysis
Opportunity Analysis
Decision Tree
6. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Relationship Map
Impact Analysis
Object Oriented Modeling
7. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Business Event
Change-driven Methodology
Prototype
8. 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.
Relationship Map
Business Need(s)
Business Requirement
Elicitation
9. A solution or component of a solution that is the result of a project.
Product
Requirements Iteration
Force Field Analysis
Timebox
10. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Product Backlog
Deliverable
Vision Statement (product vision statement)
Change Control Board (CCB)
11. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme
User Story
Relationship Map
Entity-Relationship Diagram
Secondary Actor
12. 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.
Work Product
Code
Prototype
Walkthrough
13. A function of an organization that enables it to achieve a business goal or objective.
Evaluation
Plan-driven Methodology
Capability
Business Analyst
14. The degree to which a set of inherent characteristics fulfills requirements.
Vertical Prototype
Root Cause Analysis
Entity-Relationship Diagram
Quality
15. An analysis model describing the data structures and attributes needed by the system.
Class Model
Data Dictionary
Feature
Validated Requirements
16. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Solution Requirement
Organizational Unit
Inspection
17. The work that must be performed to deliver a product service or result with the specified features and functions.
Scope Model
Request For Proposal (RFP)
Project Scope
Defect
18. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Cost Benefit Analysis
Deliverable
Inspection
Constraint
19. A person with specific expertise in an area or domain under investigation.
Focus Group
Iteration
Quality Assurance
Domain Subject Matter Expert (SME)
20. 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
Business Architecture
Requirements Management Tool
Entity-Relationship Diagram
Initiative
21. 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 Architecture
Lessons Learned Process
Organizational Unit
Project
22. The quality attributes design and implementation constraints and external interfaces that the product must have.
Stakeholder Analysis
Elicitation
Non-functional Requirement(s)
Lessons Learned Process
23. A prototype that dives into the details of the interface functionality or both.
Stated Requirements
Non-functional Requirement(s)
Vertical Prototype
Incremental Delivery
24. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
Software/Systems Requirements Specification
Activity Diagram
Included Use Cases
25. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Regulator
Business Rule(s)
Stakeholder Analysis
Iteration
26. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Organization
Process Model
Class
Baseline
27. A stakeholder who uses products or services delivered by an organization.
Cost Benefit Analysis
Customer
Peer Review
Quality
28. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Change Control Board (CCB)
Problem Statement
Business Goal
Objective
29. An actor who participates in but does not initiate a use case.
Secondary Actor
Requirements Management Tool
Requirements Allocation
Glossary
30. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Requirement(s) Defect
Work Product
Objective
Unified Modeling Language (UML)
31. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Stakeholder List
Peer Review
Requirements Model
Prototype
32. 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.
Cost Benefit Analysis
Decomposition
Request For Proposal (RFP)
Checklist
33. The set of capabilities a solution must deliver in order to meet the business need.
Feature
Solution Scope
Peer Review
Operational Support
34. All materials used by groups within an organization to define tailor implement and maintain their processes.
Organizational Process Asset
Requirements Workshop
Inspection
Requirements Management
35. A prototype developed to explore or verify requirements.
Exploratory Prototype
Domain
Tester
Scope Model
36. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Domain Subject Matter Expert (SME)
Requirements Management Plan
Business Event
Organization Modeling
37. A data element with a specified data type that describes information associated with a concept or entity.
Project Charter
Business Need(s)
Competitive Analysis
Attribute
38. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Event
Document Analysis
Implementation Subject Matter Expert (SME)
39. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Quality Attributes
Product Backlog
Requirement(s) Defect
Functional Requirement(s)
40. 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.
Quality Attributes
Benchmarking
Stakeholder List
Change-driven Methodology
41. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Business Case
Requirements Validation
Context Diagram
42. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Initiative
Capability
Benchmarking
Use Case Diagram
43. 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.
Requirements Validation
Activity Diagram
Service
Feature
44. A prototype that is continuously modified and updated in response to feedback from users.
Verified Requirements
Business Constraint(s)
Benchmarking
Evolutionary Prototype
45. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Business Case
Requirement
Peer Review
Stakeholder
46. A system trigger that is initiated by humans.
Secondary Actor
Work Breakdown Structure (WBS)
Stakeholder Analysis
Business Event
47. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Baseline
Span of Control
Requirements Trace Matrix
Business Analysis Approach
48. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
Requirements Risk Mitigation Strategy
Enterprise
Stakeholder Analysis
Vision Statement (product vision statement)
49. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Survey
Fishbone Diagram
Variance Analysis
Interface
50. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Process Model
Decision Tree
Work Product
Sponsor