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 comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Service
Deliverable
Gap Analysis
Benchmarking
2. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Focus Group
Prioritization
Actor(s)
Regulator
3. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Implementation Subject Matter Expert (SME)
Checklist
Sequence Diagram
Business Goal
4. The area covered by a particular activity or topic of interest.
Activity Diagram
Scope
Software/Systems Requirements Specification
User Acceptance Test
5. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Benchmarking
Unified Modeling Language (UML)
Data Entity
Exploratory Prototype
6. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Span of Control
Stakeholder Requirement
Requirements Management
7. 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.
Relationship
Knowledge Area
Business Analysis Plan
Methodology
8. 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
Requirement(s) Defect
Activity
Vision Statement (product vision statement)
9. 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.
Metric
Design Constraints
Walkthrough
Business Requirements Document
10. 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 Breakdown Structure (WBS)
Requirements Verification
Opportunity Analysis
Scope
11. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.
Scope Model
Event Response Table
Customer
Decision Tree
12. The features and functions that characterize a product service or result.
Service
Project Scope
Operational Support
Product Scope
13. Software requirements that limit the options available to the system designer.
Design Constraints
Work Product
SWOT Analysis
Feature
14. 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.
Validated Requirements
Objective
Cardinality
End User
15. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
Business Requirement
Domain
Competitive Analysis
Decision Tables
16. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Temporal Event
Enterprise
Data Model
Requirements Management Tool
17. A practitioner of business analysis.
Requirements Validation
Business Analyst
Stated Requirements
Requirements Management
18. 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.
Cost Benefit Analysis
Evolutionary Prototype
Functional Requirement(s)
Quality Assurance
19. 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.
Change-driven Methodology
Throw-away Prototype
Subject Matter Expert (SME)
Walkthrough
20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Business Analyst
Business Constraint(s)
Stakeholder Analysis
Project Scope
21. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Business Analysis Approach
State Diagram
Technique
Business Goal
22. An analysis model that shows user interface dialogs arranged as hierarchies.
Constraint
Dialog Hierarchy
Requirements Management Tool
Methodology
23. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Incremental Delivery
Organizational Unit
Business Architecture
24. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Stakeholder Analysis
Document Analysis
System
Relationship
25. 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.
Class
Business Analysis Plan
Decision Analysis
User Story
26. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Secondary Actor
Software/Systems Requirements Specification
Unified Modeling Language (UML)
Walkthrough
27. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
Prototype
Requirements Management Plan
Organizational Unit
28. Formal approval of a set of requirements by a sponsor or other decision maker.
Activity
Requirements Signoff
Impact Analysis
Regulator
29. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Competitive Analysis
Interface
External Interfaces
Requirements Package
30. A use case composed of a common set of steps used by multiple use cases.
Attribute
Scope
Interoperability
Included Use Cases
31. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Trace Matrix
Product Scope
Business Analysis
Code
32. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.
Business Analysis Communication Plan
Business Analysis
Solution Requirement
Quality Attributes
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.
Organizational Process Asset
Stated Requirements
Stakeholder
Use Case Diagram
34. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
System
Glossary
Variance Analysis
Software/Systems Requirements Specification
35. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Competitive Analysis
Fishbone Diagram
Glossary
Vision Statement (product vision statement)
36. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Sequence Diagram
Requirements Management Tool
Requirements Management
Business Rule(s)
37. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Quality Attributes
Relationship
Organizational Process Asset
Span of Control
38. Any unique and verifiable work product or service that a party has agreed to deliver.
Stakeholder List
Project Charter
Evaluation
Deliverable
39. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Data Model
Change Control Board (CCB)
Organization
Constraint
40. 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.
Solution
Use Case Diagram
Feature
Interview
41. A state or condition the business must satisfy to reach its vision.
Baseline
Lessons Learned Process
Requirement
Business Goal
42. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Request For Proposal (RFP)
Sponsor
Activity
Fishbone Diagram
43. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Swimlane
Organization
Developer
User Acceptance Test
44. Work carried out or on behalf of others.
Business Requirements Document
Service
Business Process
Event Response Table
45. A measure of the profitability of a project or investment.
Organization
Context Diagram
Monitoring
Return on Investment
46. 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
Requirements Management Plan
Business Requirements Document
User Story
Context Diagram
47. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Requirements Traceability
Solution
Interface
Monitoring
48. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Solution Scope
External Interfaces
Root Cause Analysis
49. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Requirement
Black Box Tests
Incremental Delivery
Stated Requirements
50. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
SWOT Analysis
Sponsor
Requirements Allocation
Validated Requirements