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. An analysis model describing the data structures and attributes needed by the system.
Objective
Quality
Data Dictionary
Event Response Table
2. The work that must be performed to deliver a product service or result with the specified features and functions.
Business Event
Project Scope
Interface
Class Model
3. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Throw-away Prototype
Class
Metadata
4. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Domain Subject Matter Expert (SME)
Context Diagram
Business Analysis
Operative Rule(s)
5. The human and nonhuman roles that interact with the system.
Actor(s)
Organizational Readiness Assessment
Scope
Work Product
6. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
SWOT Analysis
Business Goal
Assumption
7. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
End User
Methodology
Project Manager
Business Goal
8. 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 Signoff
Stakeholder Requirement
Work Breakdown Structure (WBS)
Organization
9. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Quality Assurance
Swimlane
Requirement(s) Defect
Decision Tree
10. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Structured Walkthrough
Solution Requirement
Stakeholder Analysis
Organization
11. 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
Glossary
Object Oriented Modeling
Design Constraints
Analyst
12. An informal solicitation of proposals from vendors.
User
Stakeholder List
Inspection
Request For Quote (RFQ)
13. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Business Analysis Plan
Optionality
Defect
Business Architecture
14. A group of related tasks that support a key function of business analysis.
Evolutionary Prototype
Risk
Technique
Knowledge Area
15. A unit of work performed as part of an initiative or process.
Activity
Verification
Supplier
Peer Review
16. 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.
Requirements Traceability
Quality Assurance
Software/Systems Requirements Specification
Stakeholder Analysis
17. Limitations on the design of a solution that derive from the technology used in its implementation.
Lessons Learned Process
Business Analysis Communication Plan
Technical Constraint(s)
Design Constraints
18. A practitioner of business analysis.
Optionality
Business Constraint(s)
Glossary
Business Analyst
19. A data element with a specified data type that describes information associated with a concept or entity.
Analyst
Lessons Learned Process
Business Goal
Attribute
20. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Stakeholder Requirement
Data Model
Product
Competitive Analysis
21. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Quality Attributes
Validation
Organizational Readiness Assessment
Interoperability
22. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Solution Scope
Business Architecture
Scenario
Business Goal
23. A stakeholder who uses products or services delivered by an organization.
Model(s)
Knowledge Area
Cost Benefit Analysis
Customer
24. A model that defines the boundaries of a business domain or solution.
Scope Model
Stakeholder Analysis
Stated Requirements
Supplier
25. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Functional Requirement(s)
Plan-driven Methodology
Lessons Learned Process
Desired Outcome
26. The quality attributes design and implementation constraints and external interfaces that the product must have.
Monitoring
User Requirements Document
Non-functional Requirement(s)
Lessons Learned Process
27. A structured examination of an identified problem to understand the underlying causes.
Included Use Cases
Impact Analysis
Enterprise Architecture
Root Cause Analysis
28. 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.
Business Analysis Communication Plan
Optionality
Project
Benchmarking
29. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Request For Proposal (RFP)
Business Requirements Document
Decision Tree
Class
30. A measure of the profitability of a project or investment.
Project Manager
Return on Investment
Inspection
Object Oriented Modeling
31. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
Requirements Management Tool
Cardinality
Requirements Iteration
End User
32. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Product Backlog
Included Use Cases
Business Requirements Document
Software/Systems Requirements Specification
33. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Elicitation
Monitoring
Competitive Analysis
Requirements Model
34. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Prioritization
Stakeholder List
Project Manager
Stated Requirements
35. 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.
Tester
SWOT Analysis
Force Field Analysis
Model(s)
36. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Monitoring
Sponsor
Plan-driven Methodology
Variance Analysis
37. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
User Acceptance Test
Feature
Organizational Readiness Assessment
Software/Systems Requirements Specification
38. 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.
Verification
Horizontal Prototype
Tester
Requirements Management Tool
39. A state or condition the business must satisfy to reach its vision.
Horizontal Prototype
Swimlane
Business Goal
Enterprise
40. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Black Box Tests
Requirement
Domain Subject Matter Expert (SME)
Verified Requirements
41. The area covered by a particular activity or topic of interest.
Requirements Trace Matrix
Glossary
Commercial-off-the-Shelf Software (COTS)
Scope
42. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Software/Systems Requirements Specification
Unified Modeling Language (UML)
Requirement(s) Attribute
Observation
43. 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.
Walkthrough
Requirements Workshop
Focus Group
Horizontal Prototype
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.
Request For Quote (RFQ)
Feasibility Study
Context Diagram
Requirements Package
45. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Class Model
Relationship Map
Event Response Table
Event
46. A description of the requirements management process.
Requirements Management Plan
Metadata
Decision Tree
Business Requirement
47. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Project Charter
Decision Tables
Change-driven Methodology
48. 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.
Operational Support
Relationship Map
Inspection
Customer
49. 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.
Work Product
User Requirements Document
Desired Outcome
Verified Requirements
50. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Subject Matter Expert (SME)
Developer
Assumption
Service