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 structured examination of an identified problem to understand the underlying causes.
Subject Matter Expert (SME)
Root Cause Analysis
Secondary Actor
Risk
2. 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
Cost Benefit Analysis
Temporal Event
User Story
Vertical Prototype
3. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Business Case
Stakeholder
Inspection
Enterprise Architecture
4. The number of employees a manger is directly (or indirectly) responsible for.
Unified Modeling Language (UML)
Object Oriented Modeling
Activity
Span of Control
5. Creating working software in multiple releases so the entire product is delivered in portions over time.
Incremental Delivery
Stakeholder Requirement
Plan-driven Methodology
Change Control Board (CCB)
6. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Request For Information (RFI)
Walkthrough
Event
Unified Modeling Language (UML)
7. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Design Constraints
SWOT Analysis
External Interfaces
End User
8. The features and functions that characterize a product service or result.
Context Diagram
Product Scope
Data Model
Focus Group
9. A link between two elements or objects in a diagram.
End User
Requirements Package
Cost Benefit Analysis
Association
10. A unit of work performed as part of an initiative or process.
Activity
Plan-driven Methodology
Non-functional Requirement(s)
Fishbone Diagram
11. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Business Policy
Problem Statement
Constraint
Scope
12. A stakeholder who uses products or services delivered by an organization.
Organization
Customer
Constraint
Unified Modeling Language (UML)
13. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Incremental Delivery
Regulator
Work Product
Risk
14. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Structural Rule
Stated Requirements
Included Use Cases
Elicitation
15. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Relationship
Activity
Force Field Analysis
Constraint
16. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Decision Tables
Iteration
Lessons Learned Process
Requirement
17. A model that defines the boundaries of a business domain or solution.
Scope Model
Stated Requirements
Requirements Signoff
Risk
18. The product capabilities or things the product must do for its users.
Functional Requirement(s)
Context Diagram
Monitoring
Actor(s)
19. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Analyst
Activity Diagram
Object Oriented Modeling
Requirements Management
20. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Requirements Model
Feature
Product Backlog
21. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Dialog Map
Repository
Change-driven Methodology
22. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Return on Investment
Requirements Package
Requirements Management Plan
Use Case Diagram
23. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Supplier
Organization Modeling
Plan-driven Methodology
24. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Business Need(s)
Exploratory Prototype
Interface
Black Box Tests
25. The human and nonhuman roles that interact with the system.
Structural Rule
Actor(s)
Focus Group
Activity Diagram
26. 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.
Data Model
Requirements Allocation
State Diagram
Plan-driven Methodology
27. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Data Flow Diagram (DFD)
Indicator
User
Requirements Package
28. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
Validated Requirements
Monitoring
Walkthrough
Enterprise
29. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Signoff
Change Control Board (CCB)
Force Field Analysis
Change-driven Methodology
30. 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.
Structured Walkthrough
State Diagram
Data Dictionary
Force Field Analysis
31. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various
Stakeholder Requirement
Gap Analysis
Sequence Diagram
Operative Rule(s)
32. A description of the requirements management process.
Decision Tables
Project Scope
Requirements Management
Requirements Management Plan
33. A group of related tasks that support a key function of business analysis.
Request For Information (RFI)
Span of Control
Knowledge Area
Monitoring
34. 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
Structural Rule
Organization Modeling
Defect
Requirements Verification
35. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
Gap Analysis
Evaluation
Work Breakdown Structure (WBS)
Business Architecture
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).
Business Need(s)
Interview
Cardinality
Regulator
37. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Requirement(s) Attribute
Commercial-off-the-Shelf Software (COTS)
Technique
Subject Matter Expert (SME)
38. A stakeholder person device or system that directly or indirectly accesses a system.
Process Map
Domain
User
Interoperability
39. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Work Breakdown Structure (WBS)
Metric
Structural Rule
Lessons Learned Process
40. A function of an organization that enables it to achieve a business goal or objective.
Defect
Incremental Delivery
Monitoring
Capability
41. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
Product
Context Diagram
Class Model
Solution Scope
42. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Quality
Context Diagram
Focus Group
Prototype
43. Something that occurs to which an organizational unit system or process must respond.
Cost Benefit Analysis
Event
Business Case
Checklist
44. A partial or preliminary version of the system.
Technique
Business Policy
Decomposition
Prototype
45. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Implementation Subject Matter Expert (SME)
Indicator
Methodology
Request For Quote (RFQ)
46. 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
Implementation Subject Matter Expert (SME)
Requirements Iteration
Domain Subject Matter Expert (SME)
47. 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.
Business Policy
Included Use Cases
Stakeholder
Horizontal Prototype
48. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Business Event
Risk
Prioritization
Requirements Management Tool
49. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Organizational Readiness Assessment
Feasibility Study
Domain Subject Matter Expert (SME)
Change Control Board (CCB)
50. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Checklist
Scope
Attribute
Business Analysis