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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
System
Span of Control
Black Box Tests
Domain Subject Matter Expert (SME)
2. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.
Use Case
Decomposition
Product Backlog
Problem Statement
3. Any unique and verifiable work product or service that a party has agreed to deliver.
Organizational Process Asset
Decision Analysis
Interface
Deliverable
4. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Stakeholder
Decision Analysis
Business Goal
Variance Analysis
5. A fixed period of time to accomplish a desired outcome.
Timebox
Entity-Relationship Diagram
Solution
Structured Walkthrough
6. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Problem Statement
Desired Outcome
Opportunity Analysis
Knowledge Area
7. 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
Methodology
Business Domain Model
Requirements Verification
Regulator
8. 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.
Requirements Signoff
Benchmarking
Process Model
User Story
9. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Enterprise
Business Requirement
Request For Information (RFI)
Change-driven Methodology
10. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Decision Tables
Relationship
Solution
Metric
11. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Cost Benefit Analysis
Scenario
Elicitation
Business Process
12. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Knowledge Area
Opportunity Analysis
Regulator
Temporal Event
13. The degree to which a set of inherent characteristics fulfills requirements.
Business Case
Assumption
Business Requirements Document
Quality
14. A non-actionable directive that supports a business goal.
Gap Analysis
Incremental Delivery
Business Policy
Verification
15. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Verified Requirements
Quality Attributes
Defect
Implementation Subject Matter Expert (SME)
16. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Model(s)
Requirements Management
Baseline
Validation
17. Creating working software in multiple releases so the entire product is delivered in portions over time.
System
Use Case Diagram
Event
Incremental Delivery
18. Software developed and sold for a particular market.
Commercial-off-the-Shelf Software (COTS)
Verification
Feature
Constraint
19. A unit of work performed as part of an initiative or process.
Activity
Methodology
Developer
Secondary Actor
20. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Project
Business Policy
Relationship Map
Requirement
21. 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
Implementation Subject Matter Expert (SME)
Deliverable
Stakeholder Requirement
Business Analysis
22. 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
Decision Tables
Unified Modeling Language (UML)
Class Model
23. The product capabilities or things the product must do for its users.
Elicitation
Interview
Functional Requirement(s)
Project Scope
24. A prototype developed to explore or verify requirements.
Exploratory Prototype
Data Model
Metric
Actor(s)
25. A stakeholder who provides products or services to an organization.
Supplier
Requirements Allocation
Glossary
Risk
26. 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.
Peer Review
Requirements Management
Force Field Analysis
Analyst
27. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Indicator
Validated Requirements
Span of Control
Change Control Board (CCB)
28. An analysis model showing the life cycle of a data entity or class.
Enterprise Architecture
Decision Analysis
State Diagram
Solution Scope
29. A group of related tasks that support a key function of business analysis.
State Diagram
Business Rule(s)
Impact Analysis
Knowledge Area
30. An assessment of the costs and benefits associated with a proposed initiative.
Business Case
Request For Information (RFI)
Verified Requirements
Included Use Cases
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 Story
Exploratory Prototype
Fishbone Diagram
Walkthrough
32. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
System
Organizational Readiness Assessment
Use Case
Business Process
33. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
External Interfaces
Data Entity
Survey
Request For Proposal (RFP)
34. 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.
Baseline
Context Diagram
Model(s)
Business Analysis Approach
35. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Business Analysis Approach
Variance Analysis
Business Policy
36. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Requirements Management Tool
Transition Requirement(s)
Quality Assurance
Business Requirements Document
37. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Variance Analysis
Requirement(s) Attribute
Use Case Diagram
Work Product
38. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Stakeholder Analysis
Relationship Map
Glossary
Attribute
39. A data element with a specified data type that describes information associated with a concept or entity.
Attribute
Customer
Analyst
Change-driven Methodology
40. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
End User
Code
External Interfaces
Domain Subject Matter Expert (SME)
41. 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.
Implementation Subject Matter Expert (SME)
Service
Temporal Event
Document Analysis
42. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.
Event Response Table
Temporal Event
Product
Context Diagram
43. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Transition Requirement(s)
Interoperability
Glossary
Metric
44. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Service
Event
Process Model
45. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Force Field Analysis
Objective
Optionality
Business Need(s)
46. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
Feature
Structural Rule
Requirements Traceability
47. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Service
Business Constraint(s)
System
Implementation Subject Matter Expert (SME)
48. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Benchmarking
Organizational Readiness Assessment
Business Need(s)
49. 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 Verification
Context Diagram
Constraint
50. 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.
Capability
Decision Tables
Business Rule(s)
Prioritization