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 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.
Activity
Stakeholder List
Evaluation
Data Model
2. The number of employees a manger is directly (or indirectly) responsible for.
Incremental Delivery
Span of Control
Project
Requirement(s) Attribute
3. 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
Stakeholder Requirement
Capability
Quality
Span of Control
4. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Vision Statement (product vision statement)
Request For Information (RFI)
External Interfaces
Evaluation
5. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Structured Walkthrough
Organizational Unit
Technical Constraint(s)
Variance Analysis
6. The human and nonhuman roles that interact with the system.
Actor(s)
Stakeholder
Interview
Requirements Risk Mitigation Strategy
7. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Business Requirements Document
Entity-Relationship Diagram
Business Constraint(s)
8. 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
End User
Software/Systems Requirements Specification
Business Constraint(s)
Decision Analysis
9. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Requirements Model
Developer
Activity Diagram
Business Need(s)
10. 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 Workshop
Requirements Traceability
Inspection
Business Requirement
11. 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.
Scope Model
Verification
Scope
Business Domain Model
12. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Code
Impact Analysis
Business Requirements Document
Scope Model
13. A stakeholder person device or system that directly or indirectly accesses a system.
Association
User
Horizontal Prototype
Constraint
14. 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.
Black Box Tests
Stakeholder List
Analyst
Requirement(s) Defect
15. An analysis model showing the life cycle of a data entity or class.
Object Oriented Modeling
Requirements Verification
State Diagram
User
16. The product capabilities or things the product must do for its users.
Data Flow Diagram (DFD)
Functional Requirement(s)
Included Use Cases
Vision Statement (product vision statement)
17. The area covered by a particular activity or topic of interest.
Competitive Analysis
Business Analysis
Scope
Stakeholder Analysis
18. An analysis model that shows user interface dialogs arranged as hierarchies.
Functional Requirement(s)
Dialog Hierarchy
Baseline
System
19. Software developed and sold for a particular market.
Business Analysis Communication Plan
Regulator
Commercial-off-the-Shelf Software (COTS)
User Requirements Document
20. 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
Requirement
Tester
Exploratory Prototype
Requirements Verification
21. 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
Business Process
Non-functional Requirement(s)
Requirement
22. A structured examination of an identified problem to understand the underlying causes.
Gap Analysis
Root Cause Analysis
Swimlane
User
23. 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.
Business Analysis Communication Plan
Tester
Sponsor
Plan-driven Methodology
24. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Return on Investment
Entity-Relationship Diagram
Regulator
25. A prototype that is continuously modified and updated in response to feedback from users.
Data Entity
Evolutionary Prototype
Feature
Business Analysis Approach
26. 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.
Operative Rule(s)
Scope Model
Feasibility Study
Horizontal Prototype
27. Work carried out or on behalf of others.
Feature
Focus Group
Service
Attribute
28. 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
Requirement
Repository
Request For Information (RFI)
Decision Tree
29. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Work Breakdown Structure (WBS)
Unified Modeling Language (UML)
Objective
Scope Model
30. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Organizational Readiness Assessment
Document Analysis
Requirements Trace Matrix
Supplier
31. 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
Organizational Unit
Organization
Quality Attributes
Gap Analysis
32. An informal solicitation of proposals from vendors.
Request For Quote (RFQ)
Benchmarking
Brainstorming
Black Box Tests
33. 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.
State Diagram
Requirements Traceability
Stated Requirements
Decision Tables
34. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Model(s)
Iteration
Business Architecture
Gap Analysis
35. A group of related tasks that support a key function of business analysis.
User Requirements Document
Knowledge Area
Indicator
Product Scope
36. A system trigger that is initiated by humans.
Business Event
Functional Requirement(s)
Inspection
Actor(s)
37. 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
Requirements Signoff
Business Analysis Plan
Request For Proposal (RFP)
38. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
SWOT Analysis
Request For Quote (RFQ)
Requirements Workshop
Observation
39. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Product
Operational Support
Deliverable
40. 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.
Structured Walkthrough
Project Manager
Scope
Validation
41. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Business Analysis Approach
Fishbone Diagram
Lessons Learned Process
Enterprise Architecture
42. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Solution Scope
SWOT Analysis
Product Backlog
Class
43. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Domain Subject Matter Expert (SME)
Enterprise
Organizational Process Asset
Survey
44. 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.
Stakeholder List
Feature
Feasibility Study
Return on Investment
45. 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.
Business Domain Model
Secondary Actor
Vision Statement (product vision statement)
Enterprise
46. A person with specific expertise in an area or domain under investigation.
Domain Subject Matter Expert (SME)
Use Case
Horizontal Prototype
User Requirements Document
47. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User Requirements Document
Quality
Operational Support
Force Field Analysis
48. A stakeholder who provides products or services to an organization.
Supplier
Implementation Subject Matter Expert (SME)
Business Analysis Plan
Dialog Map
49. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Evaluation
Solution
Black Box Tests
Fishbone Diagram
50. 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.
Inspection
Return on Investment
Throw-away Prototype
Requirement