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 prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Business Analysis Communication Plan
Decision Analysis
Throw-away Prototype
Requirement
2. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Requirements Traceability
Design Constraints
Relationship Map
3. A measure of the profitability of a project or investment.
Return on Investment
Subject Matter Expert (SME)
Stated Requirements
Requirements Workshop
4. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Business Process
Domain
Requirements Management Tool
Secondary Actor
5. A structured examination of an identified problem to understand the underlying causes.
Organization
Event
Peer Review
Root Cause Analysis
6. Information that is used to understand the context and validity of information recorded in a system.
Indicator
Metadata
Process Model
Business Constraint(s)
7. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Relationship
Interface
Data Entity
Indicator
8. The work that must be performed to deliver a product service or result with the specified features and functions.
Walkthrough
Tester
Brainstorming
Project Scope
9. An actor who participates in but does not initiate a use case.
Requirements Workshop
Verified Requirements
Secondary Actor
Functional Requirement(s)
10. 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
Class
Scenario
Requirements Verification
External Interfaces
11. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Opportunity Analysis
Model(s)
Prototype
Monitoring
12. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Business Analyst
Enterprise
Decision Analysis
Technique
13. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Stakeholder
Business Rule(s)
Product Backlog
System
14. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Horizontal Prototype
Observation
Sponsor
15. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Requirements Model
Requirements Iteration
Data Model
Solution Scope
16. An informal solicitation of proposals from vendors.
Project Charter
Decision Tables
Operational Support
Request For Quote (RFQ)
17. 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.
Product Backlog
Requirements Signoff
Relationship
Business Analysis
18. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Requirements Verification
Constraint
Indicator
Requirements Management Plan
19. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Business Event
Walkthrough
Requirements Workshop
20. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Metadata
Decomposition
Requirements Management Tool
Business Process
21. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Lessons Learned Process
Technique
Business Domain Model
22. A use case composed of a common set of steps used by multiple use cases.
Business Need(s)
Included Use Cases
Gap Analysis
Methodology
23. A model that defines the boundaries of a business domain or solution.
Business Policy
Business Rule(s)
Business Need(s)
Scope Model
24. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Class Model
Technique
Use Case Diagram
Organizational Readiness Assessment
25. A system trigger that is initiated by humans.
User Story
Data Dictionary
Business Event
Checklist
26. 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
Relationship
Sequence Diagram
Object Oriented Modeling
Regulator
27. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Business Analysis Plan
Requirements Allocation
Observation
Stakeholder Requirement
28. 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.
Enterprise Architecture
Solution
Context Diagram
Technique
29. The problem area undergoing analysis.
Survey
Domain
Evolutionary Prototype
Change-driven Methodology
30. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Methodology
Organization Modeling
Benchmarking
Sponsor
31. 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.
User Acceptance Test
Walkthrough
Supplier
Organization
32. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Requirements Verification
Business Architecture
Data Dictionary
Business Constraint(s)
33. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Domain
Code
Technique
Decision Tables
34. A set of requirements grouped together in a document or presentation for communication to stakeholders.
External Interfaces
Attribute
Verification
Requirements Package
35. A shared boundary between any two persons and/or systems through which information is communicated.
Design Constraints
Customer
Interface
System
36. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Competitive Analysis
Analyst
Scenario
Prototype
37. Something that occurs to which an organizational unit system or process must respond.
Benchmarking
Event
Knowledge Area
Business Analysis Plan
38. A stakeholder who provides products or services to an organization.
Business Event
Entity-Relationship Diagram
Supplier
Requirement(s) Attribute
39. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Vision Statement (product vision statement)
Document Analysis
Decision Analysis
Data Model
40. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Stakeholder
Business Constraint(s)
User
Structured Walkthrough
41. An analysis model showing the life cycle of a data entity or class.
Business Goal
Event
State Diagram
Business Process
42. A temporary endeavor undertaken to create a unique product service or result.
Assumption
Span of Control
Project
Included Use Cases
43. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Scope Model
Cost Benefit Analysis
Survey
Quality Assurance
44. 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.
Work Breakdown Structure (WBS)
Scope Model
Elicitation
Prototype
45. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Trace Matrix
Requirements Package
Solution
Structured Walkthrough
46. Ability of systems to communicate by exchanging data or services.
Verified Requirements
Relationship Map
Interoperability
Checklist
47. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Risk
Requirement(s) Attribute
Business Need(s)
Project Manager
48. An analysis model that illustrates the architecture of the system's user interface.
Class
Dialog Map
Requirements Allocation
Evolutionary Prototype
49. An analysis model describing the data structures and attributes needed by the system.
Quality Assurance
Data Dictionary
Relationship Map
Process Map
50. 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
Request For Proposal (RFP)
Requirements Model
Return on Investment
Business Goal