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 condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Non-functional Requirement(s)
State Diagram
Request For Quote (RFQ)
Requirement
2. The human and nonhuman roles that interact with the system.
Dialog Map
Business Requirement
Actor(s)
Requirements Iteration
3. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Scenario
Operational Support
Knowledge Area
Work Product
4. The set of capabilities a solution must deliver in order to meet the business need.
Entity-Relationship Diagram
Business Analysis Plan
Solution Scope
Work Product
5. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Business Requirement
Quality Attributes
Assumption
Business Analysis
6. An analysis model showing the life cycle of a data entity or class.
Monitoring
Business Analysis Approach
State Diagram
Throw-away Prototype
7. 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.
Variance Analysis
Force Field Analysis
Brainstorming
Scope
8. 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.
Vertical Prototype
Deliverable
Developer
Validation
9. An assessment of the costs and benefits associated with a proposed initiative.
Dialog Map
Business Case
Requirements Validation
User Story
10. 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.
Verified Requirements
Design Constraints
Request For Quote (RFQ)
Domain Subject Matter Expert (SME)
11. Creating working software in multiple releases so the entire product is delivered in portions over time.
Knowledge Area
Quality Assurance
Incremental Delivery
Attribute
12. A type of data model that depicts information groups as classes.
Business Analysis Approach
Class Model
Requirements Workshop
Transition Requirement(s)
13. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Optionality
Business Requirement
Association
Included Use Cases
14. 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
Relationship Map
Requirements Management Plan
Decision Analysis
Class
15. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Event Response Table
Requirements Risk Mitigation Strategy
Requirements Management
Observation
16. A partial or preliminary version of the system.
Cost Benefit Analysis
Project Manager
Prototype
Business Analysis
17. 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
Data Flow Diagram (DFD)
Included Use Cases
Business Process
Glossary
18. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Association
Operative Rule(s)
Implementation Subject Matter Expert (SME)
Business Domain Model
19. 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(s) Defect
Work Product
Requirements Verification
Data Flow Diagram (DFD)
20. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Object Oriented Modeling
Vision Statement (product vision statement)
Work Breakdown Structure (WBS)
Unified Modeling Language (UML)
21. 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
Product Backlog
Request For Information (RFI)
Process Model
Prototype
22. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Metric
Business Policy
Problem Statement
Structural Rule
23. A system trigger that is initiated by humans.
Use Case
Business Policy
Business Event
Unified Modeling Language (UML)
24. 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
Indicator
Verification
Regulator
25. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Elicitation
Organizational Readiness Assessment
Requirement(s) Defect
Vision Statement (product vision statement)
26. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
End User
Benchmarking
Initiative
Evaluation
27. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Requirement(s) Defect
SWOT Analysis
Object Oriented Modeling
Organizational Process Asset
28. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Cost Benefit Analysis
Structural Rule
Request For Quote (RFQ)
29. Limitations on the design of a solution that derive from the technology used in its implementation.
Stakeholder
Methodology
Enterprise
Technical Constraint(s)
30. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Change-driven Methodology
Methodology
Domain
User
31. A system of programming statements symbols and rules used to represent instructions to a computer.
Business Analysis Approach
Code
Decision Tree
Work Breakdown Structure (WBS)
32. An analysis model that shows user interface dialogs arranged as hierarchies.
Risk
Decision Tree
Dialog Hierarchy
Operational Support
33. 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
Project
Implementation Subject Matter Expert (SME)
Process Map
User Story
34. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Context Diagram
User
Validated Requirements
Business Analysis Approach
35. 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
Class
Business Architecture
Change Control Board (CCB)
Stakeholder Requirement
36. A prototype that is continuously modified and updated in response to feedback from users.
Evolutionary Prototype
Problem Statement
Desired Outcome
Prioritization
37. A shared boundary between any two persons and/or systems through which information is communicated.
Throw-away Prototype
Interface
Prioritization
Requirements Trace Matrix
38. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Request For Proposal (RFP)
Project Charter
Regulator
39. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.
Attribute
System
Requirement
Request For Proposal (RFP)
40. An informal solicitation of proposals from vendors.
User Acceptance Test
Request For Quote (RFQ)
Requirements Management Tool
Requirement
41. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Knowledge Area
Entity-Relationship Diagram
Class
42. 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.
Solution Scope
Gap Analysis
Change-driven Methodology
Competitive Analysis
43. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Repository
Decision Tree
Data Entity
Product Backlog
44. A state or condition the business must satisfy to reach its vision.
Decision Tables
Business Goal
Project Scope
Request For Quote (RFQ)
45. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Work Product
Process Model
Prioritization
Regulator
46. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Functional Requirement(s)
Association
Quality
Cardinality
47. 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
SWOT Analysis
Transition Requirement(s)
Interview
Structural Rule
48. Work carried out or on behalf of others.
Service
Benchmarking
Glossary
Work Product
49. A structured examination of an identified problem to understand the underlying causes.
Attribute
Root Cause Analysis
Business Need(s)
Association
50. All materials used by groups within an organization to define tailor implement and maintain their processes.
Organizational Process Asset
Supplier
Business Analysis
User Requirements Document