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 software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Lessons Learned Process
Requirements Management Tool
Assumption
Root Cause Analysis
2. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Interoperability
Brainstorming
Exploratory Prototype
Object Oriented Modeling
3. Something that occurs to which an organizational unit system or process must respond.
Project Charter
Event
Business Requirements Document
Business Case
4. 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.
State Diagram
Requirement(s) Attribute
Decision Tables
Regulator
5. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Defect
State Diagram
Requirements Management Plan
6. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Quality Attributes
Root Cause Analysis
Secondary Actor
Variance Analysis
7. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
Subject Matter Expert (SME)
Enterprise
Process Model
Request For Information (RFI)
8. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Capability
Process Model
Vertical Prototype
9. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Commercial-off-the-Shelf Software (COTS)
Organizational Process Asset
Change Control Board (CCB)
Stakeholder Requirement
10. Software developed and sold for a particular market.
Process Model
Commercial-off-the-Shelf Software (COTS)
Temporal Event
End User
11. 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.
Unified Modeling Language (UML)
Validation
Stakeholder
Business Architecture
12. 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.
Sponsor
Process Map
Activity
Requirement
13. Metadata related to a requirement used to assist with requirements development and management.
Checklist
Requirement(s) Attribute
Swimlane
Business Event
14. All materials used by groups within an organization to define tailor implement and maintain their processes.
Business Constraint(s)
Regulator
Association
Organizational Process Asset
15. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Product Backlog
Opportunity Analysis
Object Oriented Modeling
Brainstorming
16. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Non-functional Requirement(s)
Decision Tables
Scenario
Document Analysis
17. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Impact Analysis
Model(s)
Business Process
Stakeholder Requirement
18. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Business Requirement
Requirement(s) Attribute
Business Architecture
Sequence Diagram
19. 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
Business Policy
Product Scope
Class
Peer Review
20. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Metadata
Competitive Analysis
Force Field Analysis
Requirements Package
21. A description of the requirements management process.
Requirement
Scope
Requirements Management Plan
Data Dictionary
22. A shared boundary between any two persons and/or systems through which information is communicated.
Prioritization
Business Case
Domain
Interface
23. A stakeholder who provides products or services to an organization.
Metric
Use Case Diagram
Business Need(s)
Supplier
24. A prototype developed to explore or verify requirements.
Peer Review
Exploratory Prototype
Business Constraint(s)
User
25. 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.
Business Policy
Activity Diagram
Business Case
Evaluation
26. A model that defines the boundaries of a business domain or solution.
Temporal Event
Requirements Management Plan
Scope Model
Survey
27. The work that must be performed to deliver a product service or result with the specified features and functions.
Data Flow Diagram (DFD)
Requirements Allocation
Incremental Delivery
Project Scope
28. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Horizontal Prototype
Included Use Cases
Business Need(s)
Business Architecture
29. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Observation
System
Lessons Learned Process
Business Analyst
30. 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.
Problem Statement
Document Analysis
Change-driven Methodology
Vertical Prototype
31. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Requirement(s) Defect
Iteration
Scenario
Tester
32. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Work Product
Activity Diagram
Business Requirements Document
Project Scope
33. 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.
Optionality
Business Policy
Variance Analysis
Analyst
34. A practitioner of business analysis.
Business Analyst
Software/Systems Requirements Specification
Business Requirements Document
Validation
35. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Exploratory Prototype
Non-functional Requirement(s)
Data Flow Diagram (DFD)
Use Case Diagram
36. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Interview
Requirements Allocation
Elicitation
Business Need(s)
37. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Business Requirement
Iteration
Competitive Analysis
38. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Attribute
Business Case
Context Diagram
Glossary
39. 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.
Requirements Iteration
Data Flow Diagram (DFD)
Verified Requirements
Business Analysis Communication Plan
40. A partial or preliminary version of the system.
SWOT Analysis
Operational Support
Prototype
Requirements Validation
41. The human and nonhuman roles that interact with the system.
Actor(s)
Business Domain Model
Repository
Commercial-off-the-Shelf Software (COTS)
42. 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
Requirement
Verification
Business Architecture
Transition Requirement(s)
43. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
Product
Focus Group
Operational Support
Glossary
44. 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.
Event Response Table
Business Analyst
Swimlane
Feasibility Study
45. An analysis model describing the data structures and attributes needed by the system.
Requirements Management Plan
Non-functional Requirement(s)
User
Data Dictionary
46. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Prototype
Relationship
Decision Tree
Peer Review
47. 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
User Story
Activity
Walkthrough
48. The problem area undergoing analysis.
Domain
Requirement
Lessons Learned Process
Impact Analysis
49. Work carried out or on behalf of others.
Service
Request For Proposal (RFP)
Business Domain Model
Business Goal
50. A link between two elements or objects in a diagram.
Project
Association
Structured Walkthrough
Competitive Analysis