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 that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Problem Statement
Lessons Learned Process
Context Diagram
Horizontal Prototype
2. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Business Goal
External Interfaces
Structured Walkthrough
Code
3. A prototype that is continuously modified and updated in response to feedback from users.
Evolutionary Prototype
Deliverable
Document Analysis
Business Analysis
4. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Iteration
Process Map
Requirements Allocation
Solution
5. 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
Organizational Readiness Assessment
Iteration
Requirements Signoff
6. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Temporal Event
Black Box Tests
Technique
Requirements Model
7. Creating working software in multiple releases so the entire product is delivered in portions over time.
Timebox
Solution Scope
Incremental Delivery
Organization Modeling
8. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Event Response Table
Change-driven Methodology
Objective
SWOT Analysis
9. Software requirements that limit the options available to the system designer.
Association
Design Constraints
Requirement(s) Attribute
Scope Model
10. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Business Analysis Plan
Model(s)
Decomposition
Survey
11. The product capabilities or things the product must do for its users.
Organization Modeling
Domain
Functional Requirement(s)
Organizational Readiness Assessment
12. An informal solicitation of proposals from vendors.
Variance Analysis
Subject Matter Expert (SME)
Actor(s)
Request For Quote (RFQ)
13. A link between two elements or objects in a diagram.
Use Case
Competitive Analysis
Requirements Iteration
Association
14. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Structural Rule
Class Model
Solution Requirement
Software/Systems Requirements Specification
15. A non-actionable directive that supports a business goal.
Business Policy
Assumption
Cardinality
Business Analysis
16. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Requirements Management
External Interfaces
Fishbone Diagram
Metric
17. 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
Project Manager
Objective
Metadata
18. 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.
Change-driven Methodology
Business Analysis Plan
Baseline
Event
19. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Assumption
Tester
Force Field Analysis
Event Response Table
20. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Business Requirement
Black Box Tests
Functional Requirement(s)
Model(s)
21. A unit of work performed as part of an initiative or process.
Customer
Inspection
Activity
Requirements Management Plan
22. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Problem Statement
User Story
Opportunity Analysis
Project Charter
23. 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.
Evaluation
Requirements Management Tool
Business Analysis Plan
Stakeholder Requirement
24. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Actor(s)
Monitoring
Elicitation
Business Requirements Document
25. 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
Work Breakdown Structure (WBS)
Business Constraint(s)
Objective
Stakeholder Requirement
26. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Business Need(s)
Product
Document Analysis
Peer Review
27. 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
Survey
Problem Statement
User Story
Business Goal
28. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Variance Analysis
Model(s)
Metadata
Metric
29. A state or condition the business must satisfy to reach its vision.
Event Response Table
Cardinality
Business Goal
Business Analysis Plan
30. A group or person who has interests that may be affected by an initiative or influence over it.
Requirements Signoff
Risk
Stakeholder
Data Model
31. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Decision Tree
Subject Matter Expert (SME)
Requirements Validation
Business Event
32. 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.
Knowledge Area
Inspection
Enterprise
Throw-away Prototype
33. 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
Business Domain Model
Elicitation
User Acceptance Test
Requirements Iteration
34. 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
Capability
Black Box Tests
Object Oriented Modeling
End User
35. Any effort undertaken with a defined goal or objective.
Requirements Verification
Capability
Initiative
Domain Subject Matter Expert (SME)
36. Information that is used to understand the context and validity of information recorded in a system.
Focus Group
Metadata
Requirements Risk Mitigation Strategy
Project Manager
37. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Repository
Class Model
Developer
Quality Attributes
38. A solution or component of a solution that is the result of a project.
Domain Subject Matter Expert (SME)
Product
Horizontal Prototype
User Acceptance Test
39. A description of the requirements management process.
Request For Information (RFI)
Enterprise Architecture
Requirements Management Plan
Requirements Traceability
40. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Business Goal
Requirement
Solution
Software/Systems Requirements Specification
41. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Incremental Delivery
Business Policy
Validated Requirements
Structural Rule
42. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Verification
Requirements Trace Matrix
Business Constraint(s)
Glossary
43. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Fishbone Diagram
Repository
Stakeholder Requirement
Competitive Analysis
44. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Data Model
Unified Modeling Language (UML)
Span of Control
Validated Requirements
45. 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.
Force Field Analysis
Risk
Business Analysis
Structured Walkthrough
46. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Stated Requirements
Requirements Model
Quality Attributes
Data Flow Diagram (DFD)
47. 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.
Vertical Prototype
Feasibility Study
Enterprise
Monitoring
48. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
System
Problem Statement
Business Requirements Document
Requirement(s) Defect
49. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Organizational Readiness Assessment
Variance Analysis
Dialog Hierarchy
Request For Information (RFI)
50. 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.
Requirements Management Tool
Requirement
Request For Information (RFI)
Transition Requirement(s)