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 quality attributes design and implementation constraints and external interfaces that the product must have.
SWOT Analysis
Operative Rule(s)
Non-functional Requirement(s)
Incremental Delivery
2. 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.
Business Goal
Checklist
Operative Rule(s)
Baseline
3. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Benchmarking
Throw-away Prototype
Stated Requirements
Monitoring
4. A stakeholder who provides products or services to an organization.
Supplier
Project Charter
Quality Attributes
Change-driven Methodology
5. The process of examining new business opportunities to improve organizational performance.
Dialog Hierarchy
Business Goal
Opportunity Analysis
Inspection
6. 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
Prototype
Transition Requirement(s)
Data Model
Desired Outcome
7. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Requirements Management
Vision Statement (product vision statement)
Activity
Stakeholder Analysis
8. A unit of work performed as part of an initiative or process.
Plan-driven Methodology
Activity
Decision Tables
Business Event
9. A group of related tasks that support a key function of business analysis.
Knowledge Area
Temporal Event
Benchmarking
Stakeholder List
10. A person with specific expertise in an area or domain under investigation.
Class Model
Domain Subject Matter Expert (SME)
Prioritization
Enterprise
11. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Model(s)
Requirement
Implementation Subject Matter Expert (SME)
Dialog Hierarchy
12. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Scenario
Competitive Analysis
Requirement(s) Defect
Elicitation
13. 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.
Requirements Workshop
Decision Analysis
Business Process
Business Analysis
14. A practitioner of business analysis.
Work Breakdown Structure (WBS)
Business Analyst
Project Charter
Quality Attributes
15. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Event
Developer
SWOT Analysis
Brainstorming
16. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Business Requirement
Data Model
Object Oriented Modeling
Requirements Traceability
17. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Gap Analysis
Requirements Risk Mitigation Strategy
Change-driven Methodology
Scope Model
18. 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.
Requirements Trace Matrix
Business Domain Model
Project Scope
Evaluation
19. An analysis model that shows user interface dialogs arranged as hierarchies.
Walkthrough
Dialog Hierarchy
Requirements Trace Matrix
Requirement(s) Defect
20. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Management
Requirements Package
Interface
Business Constraint(s)
21. A shared boundary between any two persons and/or systems through which information is communicated.
Requirements Package
Interface
Baseline
Attribute
22. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Requirements Management Plan
Business Constraint(s)
Sequence Diagram
Desired Outcome
23. A function of an organization that enables it to achieve a business goal or objective.
Capability
Business Constraint(s)
Requirements Verification
Business Rule(s)
24. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Span of Control
Requirements Validation
Subject Matter Expert (SME)
Unified Modeling Language (UML)
25. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Technique
Structured Walkthrough
Activity
Elicitation
26. A use case composed of a common set of steps used by multiple use cases.
Change-driven Methodology
Dialog Hierarchy
Black Box Tests
Included Use Cases
27. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Product Scope
External Interfaces
Project Scope
Requirements Traceability
28. 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
Business Analysis Approach
Sponsor
User Acceptance Test
Class
29. 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.
Benchmarking
Capability
Defect
Context Diagram
30. 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.
Project Charter
Customer
Analyst
Structured Walkthrough
31. A group or person who has interests that may be affected by an initiative or influence over it.
Requirements Verification
Business Analysis Communication Plan
Checklist
Stakeholder
32. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Code
Requirement(s) Attribute
Requirements Package
33. The problem area undergoing analysis.
Feature
Included Use Cases
Domain
Root Cause Analysis
34. 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.
Activity
Span of Control
Requirement
Repository
35. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Code
Decision Analysis
Exploratory Prototype
Metadata
36. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Organization
Business Analysis Approach
Lessons Learned Process
Business Requirement
37. Any effort undertaken with a defined goal or objective.
Initiative
Secondary Actor
Requirements Management
Requirements Package
38. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Data Dictionary
Observation
Validated Requirements
Business Requirements Document
39. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Secondary Actor
Solution Requirement
Brainstorming
Operative Rule(s)
40. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Organizational Readiness Assessment
Business Analyst
Fishbone Diagram
Vision Statement (product vision statement)
41. The area covered by a particular activity or topic of interest.
Scope
Scope Model
Implementation Subject Matter Expert (SME)
User Requirements Document
42. 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.
Business Analysis
Operative Rule(s)
Benchmarking
Use Case
43. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Document Analysis
Request For Proposal (RFP)
Data Model
44. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Metric
Black Box Tests
Process Model
Data Dictionary
45. 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.
Plan-driven Methodology
Initiative
Non-functional Requirement(s)
Requirements Traceability
46. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Tester
Data Entity
Evaluation
Lessons Learned Process
47. An analysis model that illustrates the architecture of the system's user interface.
Domain Subject Matter Expert (SME)
Business Event
Non-functional Requirement(s)
Dialog Map
48. A model that defines the boundaries of a business domain or solution.
Scope Model
Requirements Management Plan
Requirements Package
Quality Attributes
49. A fixed period of time to accomplish a desired outcome.
Checklist
Timebox
Solution Requirement
Requirements Model
50. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Organizational Readiness Assessment
Requirements Management Plan
Gap Analysis
Relationship Map