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. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Decomposition
Use Case
Organizational Readiness Assessment
Structured Walkthrough
2. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Activity
Design Constraints
Document Analysis
Work Product
3. 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.
Interface
Stated Requirements
Iteration
Cardinality
4. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Relationship
Evolutionary Prototype
Implementation Subject Matter Expert (SME)
Business Requirements Document
5. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Lessons Learned Process
Verified Requirements
Process Model
Assumption
6. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Analyst
Requirements Risk Mitigation Strategy
Incremental Delivery
Feature
7. 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.
Vision Statement (product vision statement)
Decision Analysis
Capability
Business Requirement
8. 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
Operative Rule(s)
Opportunity Analysis
Object Oriented Modeling
Repository
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.
Observation
Walkthrough
Business Process
Plan-driven Methodology
10. All materials used by groups within an organization to define tailor implement and maintain their processes.
Requirements Management
Plan-driven Methodology
Organizational Process Asset
Use Case Diagram
11. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Class Model
Tester
Business Analyst
Problem Statement
12. 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.
Attribute
Cardinality
Baseline
Force Field Analysis
13. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
State Diagram
Lessons Learned Process
Design Constraints
Metric
14. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Metadata
Business Domain Model
Requirements Traceability
15. A system of programming statements symbols and rules used to represent instructions to a computer.
Code
Iteration
Business Analyst
User Requirements Document
16. The quality attributes design and implementation constraints and external interfaces that the product must have.
Requirements Management Tool
Non-functional Requirement(s)
Relationship
Product Scope
17. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Event
Peer Review
Organization
Elicitation
18. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Stakeholder
Model(s)
Business Rule(s)
19. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Domain Subject Matter Expert (SME)
Organizational Process Asset
Unified Modeling Language (UML)
Requirement
20. 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.
Horizontal Prototype
Product
Risk
Organization Modeling
21. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Change Control Board (CCB)
Peer Review
Structured Walkthrough
Baseline
22. 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.
Assumption
Feature
Prioritization
Data Model
23. Metadata related to a requirement used to assist with requirements development and management.
Solution Requirement
Constraint
Requirement(s) Attribute
Opportunity Analysis
24. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Stakeholder List
Survey
Event
Regulator
25. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Vision Statement (product vision statement)
Change-driven Methodology
Sponsor
26. 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.
Return on Investment
Subject Matter Expert (SME)
End User
Requirements Management Tool
27. 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.
Requirements Management
Process Map
Domain
Requirement(s) Attribute
28. 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
Cardinality
Exploratory Prototype
Relationship
29. The problem area undergoing analysis.
Domain
Business Event
Data Flow Diagram (DFD)
Risk
30. A prototype developed to explore or verify requirements.
Exploratory Prototype
Decision Tree
Vertical Prototype
Process Model
31. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Glossary
Organization Modeling
Cardinality
Business Requirement
32. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Quality
Quality Attributes
Use Case
33. A non-actionable directive that supports a business goal.
Business Policy
Change-driven Methodology
State Diagram
Interface
34. A solution or component of a solution that is the result of a project.
Dialog Map
Product
Metric
Business Analysis Communication Plan
35. 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.
Business Need(s)
Quality Assurance
Methodology
Business Analysis Approach
36. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Implementation Subject Matter Expert (SME)
Business Case
Requirements Management Plan
37. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Quality Attributes
Business Need(s)
Structured Walkthrough
Document Analysis
38. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Customer
Commercial-off-the-Shelf Software (COTS)
Business Policy
39. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Black Box Tests
Class
Structured Walkthrough
40. Any effort undertaken with a defined goal or objective.
Initiative
Implementation Subject Matter Expert (SME)
Incremental Delivery
Inspection
41. Information that is used to understand the context and validity of information recorded in a system.
Project Scope
Stated Requirements
Metadata
Work Breakdown Structure (WBS)
42. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Verified Requirements
Operative Rule(s)
Requirements Management
Requirements Package
43. 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
Focus Group
Requirements Management
Business Rule(s)
44. 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).
Data Model
Cardinality
Technical Constraint(s)
Fishbone Diagram
45. 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
Requirements Allocation
Business Analysis
Prototype
46. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Plan-driven Methodology
User Story
Impact Analysis
Functional Requirement(s)
47. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Incremental Delivery
Decision Tree
Defect
Domain Subject Matter Expert (SME)
48. The area covered by a particular activity or topic of interest.
Interoperability
Requirements Allocation
Scope
Decomposition
49. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Request For Information (RFI)
Sponsor
Problem Statement
Use Case
50. A state or condition the business must satisfy to reach its vision.
SWOT Analysis
Service
User Story
Business Goal