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 specific actionable testable directive that is under the control of the business and supports a business policy.
Requirements Validation
Business Rule(s)
Business Requirements Document
Business Domain Model
2. 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.
Requirements Management Tool
Software/Systems Requirements Specification
Decision Analysis
Work Breakdown Structure (WBS)
3. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Request For Information (RFI)
Requirements Verification
Structured Walkthrough
Code
4. Ability of systems to communicate by exchanging data or services.
State Diagram
Class Model
Interoperability
Requirements Risk Mitigation Strategy
5. The number of employees a manger is directly (or indirectly) responsible for.
Process Model
Business Goal
Association
Span of Control
6. Something that occurs to which an organizational unit system or process must respond.
Repository
Feature
Event
Requirement(s) Attribute
7. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Feasibility Study
Indicator
Sponsor
Feature
8. Any unique and verifiable work product or service that a party has agreed to deliver.
Deliverable
Business Requirements Document
Knowledge Area
User
9. A type of data model that depicts information groups as classes.
Variance Analysis
Class Model
Requirements Risk Mitigation Strategy
Requirements Package
10. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
Enterprise Architecture
Implementation Subject Matter Expert (SME)
Software/Systems Requirements Specification
Brainstorming
11. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Prototype
Requirements Allocation
System
Optionality
12. 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
Object Oriented Modeling
Force Field Analysis
Stakeholder Analysis
Operational Support
13. A stakeholder person device or system that directly or indirectly accesses a system.
User
Monitoring
Gap Analysis
Technical Constraint(s)
14. 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.
Organizational Unit
Walkthrough
Actor(s)
Prototype
15. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.
Stated Requirements
Objective
Evolutionary Prototype
Change-driven Methodology
16. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Objective
Stakeholder
Business Event
Developer
17. 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
Developer
Baseline
Requirements Package
18. 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
Requirements Verification
Sponsor
Organizational Readiness Assessment
Stakeholder Requirement
19. A person with specific expertise in an area or domain under investigation.
Requirements Risk Mitigation Strategy
Domain Subject Matter Expert (SME)
Product Backlog
Requirement
20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
User
Elicitation
Object Oriented Modeling
21. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Subject Matter Expert (SME)
SWOT Analysis
Scope
Gap Analysis
22. 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.
Domain
Exploratory Prototype
Organization
Analyst
23. 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 Requirement
Business Analysis Communication Plan
Activity Diagram
Enterprise
24. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Cost Benefit Analysis
Quality
Included Use Cases
25. 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.
Validated Requirements
Class Model
Focus Group
Vertical Prototype
26. 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
Requirements Signoff
Span of Control
Product
Business Architecture
27. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Objective
Requirements Iteration
Repository
Walkthrough
28. 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.
Request For Quote (RFQ)
Interface
Work Breakdown Structure (WBS)
Validation
29. Formal approval of a set of requirements by a sponsor or other decision maker.
Technique
Stakeholder Requirement
Domain Subject Matter Expert (SME)
Requirements Signoff
30. A function of an organization that enables it to achieve a business goal or objective.
Quality Assurance
Supplier
Entity-Relationship Diagram
Capability
31. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Prioritization
Iteration
Operative Rule(s)
Business Policy
32. Metadata related to a requirement used to assist with requirements development and management.
Tester
Structural Rule
Interview
Requirement(s) Attribute
33. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Observation
Objective
Quality
34. 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
Competitive Analysis
Deliverable
Model(s)
35. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Competitive Analysis
Walkthrough
Business Analysis Communication Plan
External Interfaces
36. Any effort undertaken with a defined goal or objective.
Initiative
Project
Class Model
Business Rule(s)
37. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Organizational Process Asset
Non-functional Requirement(s)
Use Case
Scenario
38. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.
Verified Requirements
Brainstorming
Iteration
Constraint
39. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Domain Subject Matter Expert (SME)
Subject Matter Expert (SME)
Initiative
Stakeholder Requirement
40. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Span of Control
Metric
Quality Assurance
Verified Requirements
41. 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.
Project
Organizational Unit
Dialog Map
Checklist
42. A link between two elements or objects in a diagram.
Requirement
Return on Investment
Association
Developer
43. A system of programming statements symbols and rules used to represent instructions to a computer.
Product Scope
Desired Outcome
Monitoring
Code
44. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Survey
Request For Information (RFI)
Stated Requirements
Prioritization
45. A prototype developed to explore or verify requirements.
Regulator
User Story
Deliverable
Exploratory Prototype
46. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
Decision Tables
Request For Information (RFI)
Validated Requirements
Change-driven Methodology
47. A unit of work performed as part of an initiative or process.
Activity
Requirements Verification
Project Manager
Association
48. A stakeholder with legal or governance authority over the solution or the process used to develop it.
User Story
Regulator
Benchmarking
Brainstorming
49. 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.
Requirement(s) Defect
Requirement
Work Breakdown Structure (WBS)
Capability
50. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Verified Requirements
Requirements Management Tool
Scenario