SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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 specific actionable testable directive that is under the control of the business and supports a business policy.
Methodology
Requirements Iteration
Business Rule(s)
Cardinality
2. Any recognized association of people in the context of an organization or enterprise.
Glossary
Business Requirement
Baseline
Organizational Unit
3. A person with specific expertise in an area or domain under investigation.
Domain
Baseline
Customer
Domain Subject Matter Expert (SME)
4. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Validation
Vertical Prototype
Cost Benefit Analysis
Prioritization
5. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Organizational Readiness Assessment
Horizontal Prototype
Design Constraints
Dialog Hierarchy
6. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Interoperability
Desired Outcome
Objective
7. Ability of systems to communicate by exchanging data or services.
Activity
Requirement
Temporal Event
Interoperability
8. 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.
Unified Modeling Language (UML)
Requirement
Observation
SWOT Analysis
9. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Sponsor
Horizontal Prototype
Subject Matter Expert (SME)
Requirements Package
10. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Product Backlog
Transition Requirement(s)
Quality Attributes
Solution
11. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Work Product
Enterprise Architecture
Brainstorming
Sequence Diagram
12. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Business Analysis
Solution
Constraint
Black Box Tests
13. The quality attributes design and implementation constraints and external interfaces that the product must have.
Operational Support
Peer Review
Non-functional Requirement(s)
Event
14. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Business Analyst
Stakeholder
Quality Assurance
Decision Tables
15. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Product Backlog
Checklist
Competitive Analysis
Swimlane
16. 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
Work Product
Requirements Signoff
Requirements Verification
System
17. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Code
Business Analysis Approach
Validated Requirements
Data Dictionary
18. A partial or preliminary version of the system.
Class Model
Prototype
Defect
Throw-away Prototype
19. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Iteration
Vision Statement (product vision statement)
Use Case Diagram
Product Scope
20. 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
Document Analysis
Data Flow Diagram (DFD)
Focus Group
21. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Requirements Risk Mitigation Strategy
Survey
Work Product
Focus Group
22. 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.
Monitoring
Regulator
Operative Rule(s)
Change-driven Methodology
23. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Quality
Validation
Business Event
Requirements Management
24. 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 Architecture
Work Breakdown Structure (WBS)
Requirements Model
25. A group or person who has interests that may be affected by an initiative or influence over it.
Deliverable
Domain
Stakeholder
Return on Investment
26. A fixed period of time to accomplish a desired outcome.
Process Map
Timebox
Class
Optionality
27. 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.
Benchmarking
Methodology
Business Case
Stated Requirements
28. A model that defines the boundaries of a business domain or solution.
Use Case
Scope Model
Prototype
Enterprise Architecture
29. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Product
Peer Review
Operative Rule(s)
Cost Benefit Analysis
30. All materials used by groups within an organization to define tailor implement and maintain their processes.
Requirements Verification
Inspection
Request For Quote (RFQ)
Organizational Process Asset
31. A state or condition the business must satisfy to reach its vision.
Project Charter
Business Policy
Secondary Actor
Business Goal
32. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Business Analysis Plan
Requirements Model
Data Entity
33. 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 Model
Brainstorming
Non-functional Requirement(s)
34. A shared boundary between any two persons and/or systems through which information is communicated.
Interface
Scenario
Constraint
Quality Assurance
35. 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.
Stakeholder Analysis
Vision Statement (product vision statement)
Decision Analysis
Throw-away Prototype
36. A stakeholder who provides products or services to an organization.
Supplier
Structured Walkthrough
Methodology
Data Model
37. 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.
Verified Requirements
Code
Requirements Traceability
Solution
38. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Quality
Requirement
Baseline
Benchmarking
39. 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
Focus Group
Unified Modeling Language (UML)
Business Analyst
Lessons Learned Process
40. 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.
State Diagram
User Requirements Document
Work Breakdown Structure (WBS)
Stakeholder List
41. A system trigger that is initiated by humans.
Lessons Learned Process
Transition Requirement(s)
Business Requirements Document
Business Event
42. 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
Technique
Transition Requirement(s)
Requirements Risk Mitigation Strategy
Plan-driven Methodology
43. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder List
Stakeholder Analysis
Risk
Document Analysis
44. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Stakeholder Analysis
SWOT Analysis
Black Box Tests
Observation
45. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Monitoring
Included Use Cases
Relationship
Work Product
46. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Black Box Tests
External Interfaces
Process Model
Activity Diagram
47. 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.
Return on Investment
Requirements Allocation
Business Analysis Plan
Stakeholder List
48. The features and functions that characterize a product service or result.
Analyst
Dialog Hierarchy
Change-driven Methodology
Product Scope
49. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Business Constraint(s)
Business Domain Model
Peer Review
Timebox
50. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Stakeholder Analysis
Data Dictionary
Business Constraint(s)