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 graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Vertical Prototype
End User
Entity-Relationship Diagram
Document Analysis
2. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Technique
Use Case Diagram
Scenario
Requirements Trace Matrix
3. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Constraint(s)
Technique
Business Requirement
Enterprise Architecture
4. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Risk
Dialog Hierarchy
Sequence Diagram
Requirements Iteration
5. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
Glossary
Stated Requirements
Peer Review
6. Creating working software in multiple releases so the entire product is delivered in portions over time.
Data Dictionary
Incremental Delivery
Event
Activity Diagram
7. A stakeholder person device or system that directly or indirectly accesses a system.
Business Domain Model
Gap Analysis
User
Requirements Signoff
8. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Structural Rule
Peer Review
Change Control Board (CCB)
User Acceptance Test
9. The product capabilities or things the product must do for its users.
Decomposition
Functional Requirement(s)
User
Customer
10. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Organizational Unit
Operative Rule(s)
Stakeholder Analysis
Metric
11. Software developed and sold for a particular market.
Business Analysis Communication Plan
Requirements Trace Matrix
External Interfaces
Commercial-off-the-Shelf Software (COTS)
12. 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
Change Control Board (CCB)
Requirements Management Tool
Activity Diagram
13. 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
Design Constraints
Association
Project Charter
Business Process
14. A temporary endeavor undertaken to create a unique product service or result.
Project
Code
Technical Constraint(s)
Horizontal Prototype
15. The area covered by a particular activity or topic of interest.
External Interfaces
Scope
Activity
Verified Requirements
16. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Impact Analysis
Service
Variance Analysis
Throw-away Prototype
17. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Iteration
Problem Statement
Product Backlog
Request For Information (RFI)
18. A stakeholder who provides products or services to an organization.
Supplier
Business Policy
Object Oriented Modeling
Business Analysis Plan
19. A prototype developed to explore or verify requirements.
Secondary Actor
Exploratory Prototype
Return on Investment
Incremental Delivery
20. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
Prioritization
External Interfaces
Business Analysis Approach
User Acceptance Test
21. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Requirements Verification
Fishbone Diagram
Glossary
Quality Assurance
22. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Plan-driven Methodology
Requirement
Organizational Readiness Assessment
Knowledge Area
23. 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.
Business Event
Stakeholder List
Fishbone Diagram
Requirements Risk Mitigation Strategy
24. A link between two elements or objects in a diagram.
Interface
Work Breakdown Structure (WBS)
Business Event
Association
25. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Organizational Process Asset
Prototype
Peer Review
26. An actor who participates in but does not initiate a use case.
Cost Benefit Analysis
Secondary Actor
Decomposition
Organization Modeling
27. A person with specific expertise in an area or domain under investigation.
Requirements Risk Mitigation Strategy
Tester
Domain Subject Matter Expert (SME)
Baseline
28. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Vision Statement (product vision statement)
Commercial-off-the-Shelf Software (COTS)
Implementation Subject Matter Expert (SME)
Data Entity
29. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Monitoring
Prototype
Decision Tree
Regulator
30. 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.
End User
Process Model
Validation
Variance Analysis
31. 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.
Functional Requirement(s)
Requirements Validation
Force Field Analysis
Requirements Iteration
32. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Organizational Process Asset
Cardinality
Assumption
Domain Subject Matter Expert (SME)
33. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Business Need(s)
Association
Desired Outcome
Data Entity
34. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Cost Benefit Analysis
Requirements Allocation
Sequence Diagram
Analyst
35. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a
Object Oriented Modeling
Requirements Trace Matrix
Enterprise
Relationship
36. 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).
Project
Objective
Data Flow Diagram (DFD)
Cardinality
37. 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.
Product Scope
Tester
Interview
Business Requirements Document
38. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Inspection
Observation
Attribute
Change Control Board (CCB)
39. 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.
Process Map
Requirement(s) Attribute
Throw-away Prototype
Interface
40. The work that must be performed to deliver a product service or result with the specified features and functions.
Cost Benefit Analysis
Project Scope
Data Model
Implementation Subject Matter Expert (SME)
41. 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.
Organizational Process Asset
Change-driven Methodology
Event Response Table
System
42. 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 Analyst
Data Dictionary
Decision Tables
Use Case
43. The human and nonhuman roles that interact with the system.
Actor(s)
Checklist
Desired Outcome
Business Analysis Plan
44. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Work Breakdown Structure (WBS)
Domain
Request For Proposal (RFP)
Supplier
45. A group of related tasks that support a key function of business analysis.
Decision Tables
Model(s)
Observation
Knowledge Area
46. 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.
Product
Work Breakdown Structure (WBS)
Requirements Traceability
Project Scope
47. 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.
Iteration
Sequence Diagram
Business Analysis Communication Plan
Structural Rule
48. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Repository
Request For Information (RFI)
Scenario
Project Charter
49. A specific actionable testable directive that is under the control of the business and supports a business policy.
Requirement
Business Rule(s)
Dialog Hierarchy
User Acceptance Test
50. Something that occurs to which an organizational unit system or process must respond.
Event
Cardinality
Organizational Process Asset
Elicitation