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.
Entity-Relationship Diagram
Business Analyst
Throw-away Prototype
Scope Model
2. The product capabilities or things the product must do for its users.
Functional Requirement(s)
Impact Analysis
Data Flow Diagram (DFD)
Constraint
3. A unit of work performed as part of an initiative or process.
End User
Lessons Learned Process
Business Analysis Communication Plan
Activity
4. The area covered by a particular activity or topic of interest.
Capability
Scope
Validation
Scenario
5. 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.
Observation
Requirements Traceability
Cost Benefit Analysis
Business Analysis
6. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Analysis Approach
Activity Diagram
Force Field Analysis
Requirements Iteration
7. A partial or preliminary version of the system.
Requirement
Prototype
Desired Outcome
Metadata
8. Metadata related to a requirement used to assist with requirements development and management.
Problem Statement
Requirement(s) Attribute
Desired Outcome
Constraint
9. 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.
Feature
Vertical Prototype
Business Case
Organizational Unit
10. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Relationship Map
Requirements Traceability
Variance Analysis
Request For Proposal (RFP)
11. 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.
Requirements Iteration
Metadata
Business Analysis
Decomposition
12. A group or person who has interests that may be affected by an initiative or influence over it.
Interview
Stakeholder
Plan-driven Methodology
Knowledge Area
13. 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.
Event Response Table
Document Analysis
Requirement
Peer Review
14. 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.
External Interfaces
Implementation Subject Matter Expert (SME)
Return on Investment
Project Charter
15. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Sponsor
Unified Modeling Language (UML)
Operative Rule(s)
Stakeholder
16. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
System
Product Backlog
Requirement(s) Attribute
Brainstorming
17. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Force Field Analysis
Business Requirement
Decomposition
Request For Quote (RFQ)
18. Creating working software in multiple releases so the entire product is delivered in portions over time.
Incremental Delivery
Stakeholder
Quality
Domain Subject Matter Expert (SME)
19. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Data Dictionary
Feasibility Study
External Interfaces
Requirements Allocation
20. 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).
Cardinality
Project
Requirement
Event Response Table
21. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Dialog Map
Quality Attributes
Knowledge Area
Solution Scope
22. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Swimlane
Non-functional Requirement(s)
Event Response Table
Repository
23. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Project
Stakeholder Analysis
User Story
24. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Interview
Organization
Request For Information (RFI)
SWOT Analysis
25. All materials used by groups within an organization to define tailor implement and maintain their processes.
Commercial-off-the-Shelf Software (COTS)
Organizational Process Asset
Organizational Unit
Analyst
26. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Quality Attributes
Change Control Board (CCB)
Organization
Service
27. 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.
Swimlane
Temporal Event
Model(s)
End User
28. Any unique and verifiable work product or service that a party has agreed to deliver.
Organization Modeling
Business Process
Deliverable
Prototype
29. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Timebox
Requirements Signoff
Inspection
Subject Matter Expert (SME)
30. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User Requirements Document
Cost Benefit Analysis
Solution Scope
Quality
31. An analysis model that shows user interface dialogs arranged as hierarchies.
Project
Dialog Hierarchy
Cardinality
Product Backlog
32. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Stakeholder List
Objective
Project Scope
Document Analysis
33. 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.
Peer Review
Relationship Map
Evaluation
Business Need(s)
34. A use case composed of a common set of steps used by multiple use cases.
Stakeholder Requirement
Request For Proposal (RFP)
Included Use Cases
Business Analysis Approach
35. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Incremental Delivery
Analyst
Operative Rule(s)
36. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Business Goal
Force Field Analysis
Regulator
Requirement
37. 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
Stated Requirements
Force Field Analysis
38. The process of examining new business opportunities to improve organizational performance.
End User
Opportunity Analysis
Operational Support
Request For Information (RFI)
39. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Business Requirement
Scenario
Assumption
Operational Support
40. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Business Requirements Document
Business Analyst
System
Validated Requirements
41. A stakeholder who uses products or services delivered by an organization.
Requirements Validation
Cost Benefit Analysis
Business Architecture
Customer
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.
Fishbone Diagram
Methodology
Transition Requirement(s)
Solution
43. The number of employees a manger is directly (or indirectly) responsible for.
Subject Matter Expert (SME)
Data Dictionary
Data Flow Diagram (DFD)
Span of Control
44. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Verified Requirements
Non-functional Requirement(s)
Unified Modeling Language (UML)
Work Breakdown Structure (WBS)
45. Any effort undertaken with a defined goal or objective.
Initiative
Work Breakdown Structure (WBS)
Secondary Actor
Sequence Diagram
46. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Sponsor
Enterprise Architecture
Competitive Analysis
Included Use Cases
47. A solution or component of a solution that is the result of a project.
Horizontal Prototype
Product Scope
Product Backlog
Product
48. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Document Analysis
Business Event
Technique
Requirements Verification
49. A measure of the profitability of a project or investment.
Force Field Analysis
Design Constraints
Survey
Return on Investment
50. A prototype developed to explore or verify requirements.
Exploratory Prototype
Class
State Diagram
Enterprise