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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Requirements Allocation
Timebox
Lessons Learned Process
Service
2. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Vertical Prototype
Attribute
Data Dictionary
Variance Analysis
3. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
End User
Solution
Elicitation
Brainstorming
4. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Requirements Risk Mitigation Strategy
Functional Requirement(s)
Force Field Analysis
5. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Business Case
Benchmarking
Structured Walkthrough
Data Entity
6. A stakeholder who provides products or services to an organization.
Request For Information (RFI)
Supplier
Incremental Delivery
Focus Group
7. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Solution
Implementation Subject Matter Expert (SME)
Prioritization
Process Map
8. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Context Diagram
Requirements Package
Regulator
Stakeholder List
9. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Feature
Sponsor
Customer
Model(s)
10. 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
Checklist
Inspection
Project Manager
11. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Scope Model
Operative Rule(s)
Supplier
Elicitation
12. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Model(s)
Entity-Relationship Diagram
Document Analysis
Stakeholder Analysis
13. 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.
Impact Analysis
Root Cause Analysis
Business Goal
Stated Requirements
14. The product capabilities or things the product must do for its users.
Functional Requirement(s)
Request For Proposal (RFP)
Project Manager
Attribute
15. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Data Flow Diagram (DFD)
Organization
Software/Systems Requirements Specification
Solution Requirement
16. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Requirements Management
Requirements Allocation
System
SWOT Analysis
17. An analysis model showing the life cycle of a data entity or class.
Optionality
State Diagram
Entity-Relationship Diagram
Capability
18. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Business Architecture
Assumption
Force Field Analysis
Interview
19. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Organization Modeling
Analyst
Service
20. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Class
Force Field Analysis
Defect
Class Model
21. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Entity-Relationship Diagram
Decision Tables
Requirement(s) Defect
Inspection
22. A fixed period of time to accomplish a desired outcome.
Stakeholder Requirement
Sponsor
Commercial-off-the-Shelf Software (COTS)
Timebox
23. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Requirements Package
Subject Matter Expert (SME)
Focus Group
24. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Requirements Traceability
Vertical Prototype
Document Analysis
Impact Analysis
25. Any recognized association of people in the context of an organization or enterprise.
Technique
Process Model
Risk
Organizational Unit
26. 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
Technical Constraint(s)
Document Analysis
Transition Requirement(s)
Process Map
27. 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.
Constraint
Stakeholder Requirement
Throw-away Prototype
Fishbone Diagram
28. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Temporal Event
Stakeholder Analysis
Business Constraint(s)
Domain Subject Matter Expert (SME)
29. 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 Workshop
Requirement
Stated Requirements
Customer
30. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Fishbone Diagram
Elicitation
Quality Assurance
31. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Cost Benefit Analysis
Requirements Management
Functional Requirement(s)
Product Backlog
32. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Assumption
Risk
Project
Process Map
33. 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.
Fishbone Diagram
Analyst
Organization
Benchmarking
34. 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.
Variance Analysis
Problem Statement
Business Analysis Plan
Business Goal
35. 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.
Requirements Traceability
End User
Validation
Opportunity Analysis
36. An analysis model describing the data structures and attributes needed by the system.
Product
Problem Statement
Data Dictionary
Brainstorming
37. 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
Business Constraint(s)
Temporal Event
Vertical Prototype
Solution Scope
38. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Walkthrough
Black Box Tests
Project
39. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Project Manager
Organizational Process Asset
Gap Analysis
Request For Information (RFI)
40. The set of capabilities a solution must deliver in order to meet the business need.
Service
Requirement(s) Attribute
Timebox
Solution Scope
41. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti
Class
Use Case Diagram
Feature
Scope Model
42. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Peer Review
Code
Dialog Map
Requirements Workshop
43. Ability of systems to communicate by exchanging data or services.
Business Case
Feature
Horizontal Prototype
Interoperability
44. 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
Requirements Management Plan
Validated Requirements
Lessons Learned Process
Requirement
45. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
Data Entity
Business Need(s)
Feature
End User
46. An assessment of the costs and benefits associated with a proposed initiative.
Requirements Management Tool
Business Case
Return on Investment
Gap Analysis
47. 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.
Analyst
Business Analysis Communication Plan
Change Control Board (CCB)
Relationship
48. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Process Map
Entity-Relationship Diagram
User Story
Developer
49. Creating working software in multiple releases so the entire product is delivered in portions over time.
Incremental Delivery
End User
Requirements Management Plan
Cost Benefit Analysis
50. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Business Process
Regulator
Association
Business Case