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 number of employees a manger is directly (or indirectly) responsible for.
Business Case
Span of Control
User Story
Vision Statement (product vision statement)
2. A measure of the profitability of a project or investment.
Business Domain Model
Project
Object Oriented Modeling
Return on Investment
3. A person with specific expertise in an area or domain under investigation.
Business Goal
Domain Subject Matter Expert (SME)
Organizational Process Asset
Work Breakdown Structure (WBS)
4. 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
State Diagram
Organizational Unit
Model(s)
Object Oriented Modeling
5. A type of data model that depicts information groups as classes.
Class Model
Throw-away Prototype
Business Need(s)
Metric
6. An informal solicitation of proposals from vendors.
Stakeholder Requirement
Requirements Workshop
Organization Modeling
Request For Quote (RFQ)
7. 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
Black Box Tests
Requirements Verification
Code
Brainstorming
8. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Flow Diagram (DFD)
Requirement
Cost Benefit Analysis
Gap Analysis
9. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.
Requirement(s) Attribute
Verification
Secondary Actor
Stakeholder List
10. 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.
Enterprise Architecture
Context Diagram
Stakeholder List
Requirement
11. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Verification
Prioritization
Dialog Map
Document Analysis
12. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Stated Requirements
Prioritization
Interview
Organization
13. A specific actionable testable directive that is under the control of the business and supports a business policy.
Metadata
Business Rule(s)
Black Box Tests
Regulator
14. 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
Business Domain Model
Verified Requirements
Organization Modeling
Span of Control
15. 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.
Root Cause Analysis
End User
Walkthrough
SWOT Analysis
16. Limitations on the design of a solution that derive from the technology used in its implementation.
Enterprise
Competitive Analysis
Domain
Technical Constraint(s)
17. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Requirement
Cost Benefit Analysis
Service
Data Entity
18. A non-actionable directive that supports a business goal.
Business Policy
Decision Analysis
Feature
Business Rule(s)
19. The features and functions that characterize a product service or result.
Knowledge Area
Code
Business Need(s)
Product Scope
20. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Validated Requirements
Software/Systems Requirements Specification
Constraint
Defect
21. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Project
Organization
Prioritization
Included Use Cases
22. 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.
Requirement(s) Defect
Business Need(s)
Change-driven Methodology
Object Oriented Modeling
23. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Assumption
Inspection
Verification
Requirements Traceability
24. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Solution Scope
Scope
Regulator
Scenario
25. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Work Breakdown Structure (WBS)
Commercial-off-the-Shelf Software (COTS)
Use Case Diagram
Peer Review
26. 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.
Lessons Learned Process
Horizontal Prototype
Business Analysis Communication Plan
Project Charter
27. 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.
Requirement
Interview
Work Breakdown Structure (WBS)
External Interfaces
28. 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.
Model(s)
Project Manager
Event Response Table
Requirements Allocation
29. A state or condition the business must satisfy to reach its vision.
Return on Investment
Business Goal
Objective
Regulator
30. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Deliverable
User Story
Optionality
Competitive Analysis
31. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Defect
Checklist
Included Use Cases
Data Model
32. A fixed period of time to accomplish a desired outcome.
Request For Proposal (RFP)
Validated Requirements
Timebox
Metric
33. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Analyst
Event Response Table
Constraint
Observation
34. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Software/Systems Requirements Specification
Structural Rule
Business Need(s)
Technique
35. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Relationship
Structured Walkthrough
Process Model
Data Model
36. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Lessons Learned Process
Scenario
Solution Requirement
Work Product
37. 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
Code
Data Dictionary
Vision Statement (product vision statement)
38. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Class Model
Feature
Elicitation
39. 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
Organizational Readiness Assessment
Request For Quote (RFQ)
Inspection
40. 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.
Timebox
Business Case
Lessons Learned Process
Throw-away Prototype
41. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Software/Systems Requirements Specification
Observation
Enterprise
Solution Requirement
42. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Product Backlog
Desired Outcome
Incremental Delivery
Technique
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
Evolutionary Prototype
Requirements Management Tool
Transition Requirement(s)
Business Constraint(s)
44. 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.
Change-driven Methodology
Prioritization
SWOT Analysis
Validation
45. A stakeholder who uses products or services delivered by an organization.
User
Customer
Monitoring
Peer Review
46. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Use Case
Model(s)
Association
47. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Operative Rule(s)
Technical Constraint(s)
Objective
Brainstorming
48. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Decision Analysis
Survey
Black Box Tests
Risk
49. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Defect
Product Scope
Sponsor
Checklist
50. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Object Oriented Modeling
Business Policy
Project
Requirements Risk Mitigation Strategy