Cbap Prep For Babok V2.0

Front 1

Acceptance Criteria

Back 1

The minimal set of requirements that must be met in order for a particular solution to be worth implementing.

Key

Front 2

Activity

Back 2

A unit of work performed as part of an initiative or process

Front 3

Actor

Back 3

A human and nonhuman roles that interact with the system

Front 4

Actor, Secondary

Back 4

An actor who participates but does not initiate a use case

Front 5

Allocation

Back 5

The forward traceabilily or lineage of of a requirement (in the direction of a solution).

Front 6

Approach

Back 6

A set of processes, templates, and activities that will be used to perform a task.

Front 7

Association

Back 7

A link between elements or objects in a diagram or between actors in a use case

Front 8

Assumption

Back 8

Influencing factors that are believed to be true but have not been confirmed to be accurate

Front 9

Asynchronous message (signal)

Back 9

Allows the object in a Sequence Diagram to continue with its own processing after sending the signal

Front 10

Average Rate of Return

Back 10

Estimate of rate of return on an investment

Front 11

Baseline

Back 11

A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development

Front 12

Black Box Test

Back 12

Test written without regard to how the software is implemented

Front 13

Budgeting

Back 13

Prioritize requirements, using a fixed number of units of money

Task-Specific

Front 14

Business Analysis

Back 14

A 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 to recommend solutions that enable the organization to achieve its goals.

Front 15

Business Case

Back 15

An assessment of the costs, benefits, and risks associated with a proposed initiative

Front 16

Business Goal

Back 16

A state or condition that must be satisfied to reach a vision. Longer-term, ongoing, and qualitative statements of a state or condition that the organization is seeking to establish and maintain.

Front 17

Business Need

Back 17

A type of business requirement that is a statement of a business objective or an impact the solution should have on its environment. It defines the problem for which the business analyst is trying to find a solution.

Front 18

Business Policy

Back 18

A non-actionable directive that supports a goal

Front 19

Business Rule

Back 19

A specific, actionable, testable directive that is under the control of an organization and that supports a business policy

Key

Front 20

Business Rule, Operative

Back 20

A business rule an organization chooses to enforce as a matter of policy. Example: “An order must not be placed when the billing address provided by the customer does not match the address on file with the credit card provider.”

Front 21

Business Rule, Structural

Back 21

Intended to help determine when something is or is not true, or when things fall into a specific category, or a calculation. Example: “An order must have one and only one associated payment method.”

Front 22

Cardinality

Back 22

The number of occurances of one entity in a data model that are linked to a second entity

Front 23

Constraint, Business

Back 23

Reflects time/budget/resource restrictions

Front 24

Constraint, Technical

Back 24

Architectural constraints

Front 25

Context Diagram

Back 25

A top-level data flow diagram that models the scope of a solution.

Front 26

Customer

Back 26

External stakeholder who make use of the products or services

Front 27

Data Dictionary

Back 27

Standard definitions of data elements, their meanings, and allowable values

Key

Front 28

Data Entity

Back 28

A group of related information to be stored by the system.

Front 29

Data Flow Diagram

Back 29

A visual representation of how information is moved through a system

Key

Front 30

Data Model

Back 30

Describes the concepts relevant to a domain, the relationships between those concepts, and information associated with them.

Key

Front 31

Decision Tree

Back 31

An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence

Front 32

Defect

Back 32

A deficiency in a produce or service that reduces its quality

Front 33

Derivation

Back 33

The backwards lineage of a requirement (toward the business goals)

Front 34

Desired Outcome

Back 34

The business benefits that will result from meeting the business need and the end states desired by stakeholders

Front 35

Diagram

Back 35

A graphical model

Front 36

Discounted cash flow

Back 36

Future value on a specific data

Front 37

Domain

Back 37

An area undergoing analysis

Front 38

Domaine SME

Back 38

Stakeholder with in-depth knowledge of a topic relevant to the business need or solution scope

Front 39

End User

Back 39

Stakeholder who directly interacts with the solution

Front 40

Enterprise

Back 40

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.

Front 41

Enterprise Architecture

Back 41

A description of an organization's business processes, IT software and hardware, people, operations, and projects, and the relationship between them.

Front 42

Estimation, Analogous

Back 42

Use a similar project as basis. Top-down estimate.

Front 43

Estimation

Back 43

Forecast the possible range of costs and effort associated with any initiative

Front 44

Estimation, Bottom Up

Back 44

Break down into smaller items, estimate those, then aggregate.

Front 45

Estimation, Historic Analysis

Back 45

Use history. Similar to analogous but can be more granular

Front 46

Estimation, Parametric

Back 46

Use parameters.

Front 47

Estimation, Rolling Wave

Back 47

Iterative

Front 48

Estimation, Three Point

Back 48

Use most optimistic, most pessimistic, and most likely

Front 49

Evaluation

Back 49

The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time

Front 50

Evaluation Criteria

Back 50

The set of requirements that will be used to choose between multiple solutions.

Key

Front 51

Event

Back 51

Something that occurs to which an organizational unit, system, or process must respond

Front 52

Expected Value

Back 52

The probability-weighted average of all possible values

Front 53

Extend

Back 53

Stereotype in which one use case inserts additional behavior into another. The extended use case does not need to be a complete use case

Front 54

Feature

Back 54

A cohesive bundle of externally visible functionality

Front 55

Fishbone Diagram

Back 55

A diagramming technique used in root cause analysis. Also called an Ishikawa or cause-effect diagram.

Front 56

Five Whys

Back 56

A model used in root cause analysis. One iteratively asks why until you reach the root (may or may not be five iterations)

Front 57

Force Field Analysis

Back 57

A graphical model for depicting the forces that support and oppose a change.

Front 58

Functional Decomposition

Back 58

Decompose processes, functional areas, or deliverables into their component parts and allow each part to be analyzed independently

Front 59

Gap Analysis

Back 59

A comparison of the current state and desired future state in order to identify differences that need to be addressed

Front 60

Glossary

Back 60

Documents terms unique to the domain

Key

Front 61

Impact Analysis

Back 61

Assesses the effects that a proposed change will have on a stakeholder, group, project, or system

Front 62

Implementation SME

Back 62

Stakeholder responsible for designing and implementing potential solutions

Front 63

Include

Back 63

Stereotype in which one use case makes use of the behavior of another. The included use case does not need to be a complete use case

Front 64

Inspection

Back 64

A formal type of peer review that utilizes a pre-defined and documented process, specific participant roles, and the capture of defect and process metrics

Front 65

Internal Rate of Return

Back 65

The interest rate (or discount) when the net present value is equal to zero

Front 66

Intiative

Back 66

An effort undertaken with a defined goal or objective

Front 67

Key Performance Indicator

Back 67

A metric that measures progress towards a strategic goal or objective.

Key

Front 68

Lifeline

Back 68

A line in a sequence diagram that shows when an object is created or destroyed.

Front 69

Methodology

Back 69

An approach that is used over time

Front 70

Metrics

Back 70

A quantifiable indicator that measures progress

Key

Front 71

Model

Back 71

Any simplified representation of a more complex reality

Front 72

Monitoring

Back 72

A continuous process of collecting data

Front 73

MuSCoW Analysis

Back 73

Prioritize requirements, using MUST, SHOULD, COULD, WOULD

Task-Specific

Front 74

Net present value

Back 74

Future view of costs and benefits converted to today’s value

Front 75

Objective

Back 75

A target or metric that a person or organization seeks to meet in order to progress toward a goal

Front 76

Operational Support

Back 76

Stakeholder who will provide support for the solution once released

Front 77

Organization

Back 77

An autonomous unit within an enterprise under the management of a single individual or board

Front 78

Pay Back Period

Back 78

The amount of time it takes for an investment to pay for itself

Front 79

Process Map

Back 79

A model that shows business process in terms of input, output, and steps

Front 80

Process Modeling

Back 80

A process describes how multiple people or groups collaborate over a period of time to perform work.

Key

Front 81

Product

Back 81

A solution or solution component that is a result of a project

Front 82

Project

Back 82

A temporary endeavor undertaken to create a unique product, service, or result

Front 83

Project Charter

Back 83

A document issues by the sponsor that formally authorizes the existence of a project

Front 84

Project Manager

Back 84

Stakeholder who manages the work required to deliver the solution

Front 85

Prototype

Back 85

A visual interface model, a partial or preliminary version of the system

Front 86

Prototype, Evolutionary versus Exploratory

Back 86

Also known as Functional versus Throw-Away. Evolutionary is continuously improved and Exploratory is developed to explore or verify requirements and then thrown away.

Front 87

Prototype, Horizontal versus Vertical

Back 87

Horizontal shows a shallow and possibly wide view of the system's functionality. Vertical is deep, usually a narrow slice of the entire system's functionality.

Front 88

Quality

Back 88

The degree to which a set of inherent characteristics fulfills requirements

Front 89

Regulator

Back 89

Stakeholder responsible for the definition and enforcement of standards

Front 90

Request for Information (RFI) v.

Request for Proposal (RFP) v.

Request for Quote (RFQ)

Back 90

All requirements documents issued to solicit vendor input.

RFI: Used when seeking different alternatives or when uncertain regarding available options.

RFP: Organization seeking formal proposal

RFQ: Less formal seeking proposals

Front 91

Requirement

Back 91

1. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.

2. A condition or capability that must be met or possessed by a solution to satisfy a contract, standard, specification, or other formally imposed documents.

3. A documented representation of a condition or capability as in (1) or (2).

Front 92

Requirement, Business

Back 92

A higher-level statement of goals, objectives, or needs of the enterprise. Developed through enterprise analysis.

Front 93

Requirement, Functional

Back 93

Solution requirement that describes behavior

Front 94

Requirement, Non-functional

Back 94

Solution requirement that describes a condition that does not directly relate to behavior. "Quality of Service"

Front 95

Requirement, Solution

Back 95

Describes the characteristics of a solution that meet business requirements and stakeholder requirements. Developed through requirements analysis.

Front 96

Requirement, Stakeholder

Back 96

A statement of the needs of a particular stakeholder of class of stakeholders. Developed through requirements analysis.

Front 97

Requirement, Transition

Back 97

Capabilities that the solution must have in order to facilitate transition from the current to a desired future state. Developed through solution assessment and validation.

Front 98

Requirement Attribute

Back 98

Metadata related to a requirement

Front 99

Requirement Relationship: Cover

Back 99

A requirement relationship that exists when one requirement fully includes another requirement. This is a special case of subset, where the top-level requirement is the sum of the sub-requirements

Front 100

Requirement Relationship: Effort

Back 100

A requirement relationship that exists when a requirement is easier to implement if a related requirement is also implemented.

Front 101

Requirement Relationship: Necessity

Back 101

A requirement relationship that exists when one requirement is only necessary if another is implemented. Unidirectional or bidirectional.

Front 102

Requirement Relationship: Subset

Back 102

A requirement relationship that exists when a requirement is the decomposed outcome of another requirement

Front 103

Requirement Relationship: Value

Back 103

A requirement relationship that exists when including a requirement affects the desirability of a related requirement

Front 104

Requirements Management

Back 104

The activities that control requirements development, including change control, definition, and traceability

Front 105

Requirements Workshop

Back 105

A productive focused event attended by carefully selected key stakeholders and subject matter experts for a short, intensive period to elicit requirements.

Key

Front 106

Return on Investment

Back 106

A measure of profitability

Front 107

Risk

Back 107

An uncertain event or condition that, if it occurs, will effect the goals or objectives of a proposed change

Front 108

Scenario

Back 108

One way that an actor can accomplish a particular goal

Key

Front 109

Scope, Project

Back 109

The work that must be performed to deliver a product, service, or result

Front 110

Scope, Solution

Back 110

The set of capabilities a solution must deliver in order to meet a business need.

Front 111

Service

Back 111

Work carried out on behalf of others

Front 112

Sequence Diagram

Back 112

A sequence diagram shows how classes and objects interact during a scenario. The sequence diagram shows how objects used in the scenario interact but not how they are related to one another.

Front 113

Solution

Back 113

Meets a business need

Front 114

Span of Control

Back 114

The number of employees a manager is directly or indirectly responsible for

Front 115

Sponsor

Back 115

Stakeholder who Initiates the effort, authorizes work, controls the budget

Front 116

Stakeholder

Back 116

A person who has interests that may be affected by an initiative or influence over it.

Front 117

State Diagram

Back 117

An analysis model showing the life cycle of a data entity or class

Front 118

Stereotype

Back 118

A relationship between use cases

Front 119

Stimulus

Back 119

A message in a Sequence Diagram that flows between objects, resulting in an event

Front 120

Structured Walkthrough

Back 120

A peer review of a deliverable

Front 121

Supplier

Back 121

External stakeholder who provide products or services

Front 122

SWOT Analysis

Back 122

A SWOT analysis is a valuable tool to quickly analyze various aspects of the current state of the business process undergoing change.

Front 123

System

Back 123

A collection or interrelated elements that interact to achieve an objective

Front 124

Timeboxing

Back 124

Prioritize requirements, using a fixed number of units of time

Task-Specific

Front 125

Tester

Back 125

Stakeholder who determines how to verify the solution meets the solution requirements, plus conducts the verification process

Front 126

Use Case

Back 126

Describes all possible outcomes of an attempt to accomplish a particular goal that the solution will support.

Key

Front 127

User Story

Back 127

Actor, action, achievement

Front 128

Validation

Back 128

The work done to ensure that the stated requirements support and are aligned with the goals and objectives

Front 129

Variance Analysis

Back 129

Analysis of discrepencies between planned and actual performance

Front 130

Verification

Back 130

The work done to ensure that requirements are defined correctly and are of an acceptable level of quality.

Front 131

Vision Statement

Back 131

A brief statement that describes the why, what, and who of desired software product from a business point of view. Identifies key stakeholders and describes the impact that meeting the business need will have on them.

Front 132

Voting

Back 132

Prioritize requirements, stakeholders get a fixed number of tokens to distribute

Task-Specific