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 set of processes templates and activities that will be used to perform business analysis in a specific context.
Methodology
Business Analysis Approach
Focus Group
Business Analyst
2. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Fishbone Diagram
Decision Tables
Defect
Requirement(s) Attribute
3. A shared boundary between any two persons and/or systems through which information is communicated.
Interface
Business Analysis
Technical Constraint(s)
User
4. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Horizontal Prototype
Peer Review
Quality Attributes
Non-functional Requirement(s)
5. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode
Project Manager
Optionality
Data Model
Business Domain Model
6. Metadata related to a requirement used to assist with requirements development and management.
Class Model
Peer Review
Data Model
Requirement(s) Attribute
7. A unit of work performed as part of an initiative or process.
Iteration
Domain
Activity
Business Process
8. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
Operational Support
Project Charter
Optionality
Swimlane
9. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Return on Investment
Requirements Validation
Quality Attributes
Business Analysis Approach
10. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Interview
Data Dictionary
Methodology
Use Case Diagram
11. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Cardinality
Desired Outcome
Requirement
Methodology
12. Any effort undertaken with a defined goal or objective.
Dialog Map
Lessons Learned Process
Initiative
Throw-away Prototype
13. The area covered by a particular activity or topic of interest.
Scope
Vision Statement (product vision statement)
Non-functional Requirement(s)
Implementation Subject Matter Expert (SME)
14. A model that defines the boundaries of a business domain or solution.
Scope Model
Decomposition
Incremental Delivery
Document Analysis
15. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Initiative
Organizational Readiness Assessment
Quality Assurance
16. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Root Cause Analysis
Business Requirement
Business Analysis Plan
Assumption
17. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Benchmarking
Solution Scope
Work Product
Request For Information (RFI)
18. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Structured Walkthrough
Requirements Model
Walkthrough
Constraint
19. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Organizational Process Asset
Business Need(s)
Data Dictionary
Vertical Prototype
20. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Verification
Activity Diagram
Enterprise Architecture
21. A data element with a specified data type that describes information associated with a concept or entity.
End User
Attribute
External Interfaces
Dialog Hierarchy
22. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Requirement(s) Defect
Business Policy
Work Breakdown Structure (WBS)
Lessons Learned Process
23. 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.
Change Control Board (CCB)
Defect
Business Analysis Plan
Work Product
24. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Knowledge Area
Quality Attributes
Throw-away Prototype
Process Map
25. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.
Work Product
Use Case
Software/Systems Requirements Specification
Technique
26. An actor who participates in but does not initiate a use case.
Secondary Actor
Competitive Analysis
Activity
Solution Scope
27. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Relationship Map
Decision Tree
Model(s)
28. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Regulator
Vision Statement (product vision statement)
Organization
Included Use Cases
29. A function of an organization that enables it to achieve a business goal or objective.
Change-driven Methodology
Event
Capability
Use Case Diagram
30. 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.
Temporal Event
Capability
Feature
Supplier
31. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Commercial-off-the-Shelf Software (COTS)
Enterprise Architecture
Requirements Trace Matrix
Checklist
32. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Enterprise Architecture
Requirements Signoff
Change Control Board (CCB)
33. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Organizational Unit
Business Requirement
Activity Diagram
Assumption
34. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Activity
Dialog Hierarchy
Process Model
Cardinality
35. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Solution Requirement
Feasibility Study
Stakeholder Analysis
Code
36. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Metadata
Business Requirements Document
Requirement(s) Attribute
Operational Support
37. A prototype that dives into the details of the interface functionality or both.
Subject Matter Expert (SME)
Vertical Prototype
Document Analysis
Prototype
38. A system trigger that is initiated by humans.
Class
Exploratory Prototype
Baseline
Business Event
39. A stakeholder person device or system that directly or indirectly accesses a system.
Stated Requirements
Project Scope
Cost Benefit Analysis
User
40. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Solution Requirement
Change Control Board (CCB)
Entity-Relationship Diagram
Business Requirement
41. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Requirements Verification
Quality
Class
Model(s)
42. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Iteration
Technique
Product Scope
Business Constraint(s)
43. 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.
Class
Data Model
Monitoring
Walkthrough
44. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Focus Group
Work Product
Dialog Map
Customer
45. A system trigger that is initiated by time.
Temporal Event
Span of Control
Project Scope
Project Manager
46. 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
Return on Investment
Business Process
Enterprise Architecture
Software/Systems Requirements Specification
47. An analysis model showing the life cycle of a data entity or class.
State Diagram
Business Goal
Risk
Quality
48. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Baseline
Competitive Analysis
Requirement(s) Defect
Data Flow Diagram (DFD)
49. 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
Lessons Learned Process
Desired Outcome
Requirement(s) Attribute
50. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Variance Analysis
Attribute
Request For Information (RFI)
Business Constraint(s)