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 non-actionable directive that supports a business goal.
Business Policy
Validated Requirements
Structured Walkthrough
Constraint
2. The problem area undergoing analysis.
Interface
Functional Requirement(s)
Domain
User Acceptance Test
3. 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.
Validation
State Diagram
Prioritization
Code
4. A use case composed of a common set of steps used by multiple use cases.
Brainstorming
Included Use Cases
Vision Statement (product vision statement)
Business Process
5. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Functional Requirement(s)
Business Requirements Document
Commercial-off-the-Shelf Software (COTS)
Solution
6. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
SWOT Analysis
Business Requirements Document
Span of Control
Requirements Validation
7. A shared boundary between any two persons and/or systems through which information is communicated.
Commercial-off-the-Shelf Software (COTS)
Checklist
Interface
Assumption
8. A stakeholder who uses products or services delivered by an organization.
Business Analysis Communication Plan
Business Requirement
Customer
Transition Requirement(s)
9. A group or person who has interests that may be affected by an initiative or influence over it.
Stakeholder
Customer
Decomposition
Assumption
10. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Requirements Traceability
Domain Subject Matter Expert (SME)
Solution
Constraint
11. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Relationship
Business Analysis Plan
Scenario
Business Domain Model
12. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Stakeholder
Vision Statement (product vision statement)
Opportunity Analysis
Repository
13. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Metric
Design Constraints
Developer
Activity Diagram
14. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Defect
Elicitation
Tester
Black Box Tests
15. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Requirement
Verified Requirements
User Story
Relationship Map
16. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Root Cause Analysis
Swimlane
Peer Review
Model(s)
17. The number of employees a manger is directly (or indirectly) responsible for.
Requirement
Span of Control
Business Constraint(s)
Decomposition
18. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Checklist
Requirements Management Plan
Developer
Event
19. 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
Swimlane
Validation
Evolutionary Prototype
Business Architecture
20. A prototype developed to explore or verify requirements.
Project Charter
Requirements Package
Exploratory Prototype
Root Cause Analysis
21. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Customer
Requirements Allocation
Walkthrough
22. Any unique and verifiable work product or service that a party has agreed to deliver.
Business Analysis Communication Plan
Scope
Project Scope
Deliverable
23. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Plan-driven Methodology
Decision Analysis
Service
Product Backlog
24. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Software/Systems Requirements Specification
Elicitation
Capability
Request For Quote (RFQ)
25. 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.
Methodology
Requirements Trace Matrix
Activity
Stakeholder List
26. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Requirement
Observation
Sponsor
Assumption
27. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Validated Requirements
Quality
Dialog Hierarchy
Structural Rule
28. 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.
Force Field Analysis
Objective
Business Analysis Plan
Requirements Validation
29. The work that must be performed to deliver a product service or result with the specified features and functions.
Quality
Implementation Subject Matter Expert (SME)
User
Project Scope
30. 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.
Unified Modeling Language (UML)
Requirements Management Plan
Analyst
Business Analysis Communication Plan
31. 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.
Interview
Enterprise
Stakeholder Requirement
Deliverable
32. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Data Entity
Monitoring
Business Analysis Approach
Relationship
33. 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
Operative Rule(s)
Business Requirements Document
Elicitation
Request For Information (RFI)
34. A model that defines the boundaries of a business domain or solution.
Prototype
Force Field Analysis
Scope Model
Quality Assurance
35. 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.
Project
Feasibility Study
State Diagram
Methodology
36. 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.
Feature
Analyst
Deliverable
Throw-away Prototype
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)
Black Box Tests
Monitoring
Data Entity
38. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Process Map
Metric
Model(s)
Requirements Model
39. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Business Case
Black Box Tests
Decision Tables
Structural Rule
40. 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.
Plan-driven Methodology
Exploratory Prototype
Project Manager
Force Field Analysis
41. 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
Monitoring
Code
Entity-Relationship Diagram
Organization
42. 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
Inspection
Dialog Map
Monitoring
Requirements Verification
43. An analysis model showing the life cycle of a data entity or class.
Business Event
Monitoring
State Diagram
External Interfaces
44. Formal approval of a set of requirements by a sponsor or other decision maker.
Work Breakdown Structure (WBS)
Requirements Signoff
Sequence Diagram
Scope
45. A stakeholder person device or system that directly or indirectly accesses a system.
Gap Analysis
User
Organizational Unit
Requirements Traceability
46. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Request For Proposal (RFP)
System
Included Use Cases
Baseline
47. Work carried out or on behalf of others.
Requirements Traceability
Business Process
Work Breakdown Structure (WBS)
Service
48. A temporary endeavor undertaken to create a unique product service or result.
Evolutionary Prototype
Return on Investment
Project
Non-functional Requirement(s)
49. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Brainstorming
Defect
SWOT Analysis
Dialog Map
50. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Project Scope
Organizational Unit
Vertical Prototype