Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

babok > babok > Flashcards

babok Flashcards

(87 cards)

Start Studying
1
Q

Business Analysis Planning and Monitoring

A

3.1 Plan Business Analysis Approach
3.2 Plan Stakeholder Engagement
3.3 Plan Business Analysis Governance
3.4 Plan Business Analysis Information Management
3.5 Identify Business Analysis Performance Improvements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Elicitation and Collaboration

A

4.1 Prepare for Elicitation
4.2 Conduct Elicitation
4.3 Confirm Elicitation Results
4.4 Communicate Business Analysis Information
4.5 Manage Stakeholder Collaboration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Requirements Life Cycle Management

A

5.1 Trace Requirements 79
5.2 Maintain Requirements 83
5.3 Prioritize Requirements 86
5.4 Assess Requirements Changes 91
5.5 Approve Requirements 95

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Strategy Analysis

A

6.1 Analyze Current State 103
6.2 Define Future State 110
6.3 Assess Risks 120
6.4 Define Change Strategy 124

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Requirements Analysis and Design Definition

A

7.1 Specify and Model Requirements 136
7.2 Verify Requirements 141
7.3 Validate Requirements 144
7.4 Define Requirements Architecture 148
7.5 Define Design Options 152
7.6 Analyze Potential Value and Recommend Solution 157

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Solution Evaluation

A

8.1 Measure Solution Performance 166
8.2 Analyze Performance Measures 170
8.3 Assess Solution Limitations 173
8.4 Assess Enterprise Limitations 177
8.5 Recommend Actions to Increase Solution Value 182

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Core Concept

A

Change
Need
Solution
Stakeholder
Value
Context

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

classification schema describes requirements:

A

Business requirements:
Stakeholder requirements:
Solution requirements:
* functional requirements:
* non-functional requirements or quality of service requirements:
* Transition requirements:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Specify and Model Requirements

A

analyze, synthesize, and refine elicitation results into requirements and designs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Model Requirements

A

Matrices: complex but uniform structure, which can be broken down into elements that apply to every entry in the table. Matrices may be used for data dictionaries, requirements traceability, or for gap analysis. Matrices are also used for prioritizing
requirements and recording other requirements attributes and metadata.

Diagrams: a diagram is a visual, often pictorial, representation of arequirement or set of requirements. A diagram is especially useful to depict complexity in a way that would be difficult to do with words. Diagrams can also be used to define boundaries for business domains, to categorize and create hierarchies of items, and to show components of objects such as data and their relationships.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Using one or more of the model formats, business analysts determine specific categories and specific models within categories to be used. Model categories can include:

A

People and Roles
rationale
activity flow
capability
data and information

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

element of Specify and Model Requirements

A

Model Requirements
Analyze Requirements
Represent Requirements and Attributes
Implement the Appropriate Levels of Abstraction

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Business analysis information is decomposed into components to further examine for:

A
  • anything that must change to meet the business need,
  • anything that should stay the same to meet the business need,
  • missing components,
  • unnecessary components, and
  • any constraints or assumptions that impact the components.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Guidelines and Tools verify re quirement

A

Modelling Notations/Standards:
Modelling Tools
Requirements Architecture
Requirements Life Cycle Management Tools
Solution Scope:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Verify Requirements p&d

A

ensure that requirements and designs specifications and models meet quality standards and are usable for the purpose they serve.
check by the business analyst and key stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Verify Requirements input

A

Requirements (specified and modelled)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Characteristics of Requirements and Designs Quality

A

Atomic
complete
concise
understandable
consistent
unambiguous
prioritized
testable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Verification Activities

A
  • checking for compliance with organizational performance standards for business analysis, such as using the right tools and methods,
  • checking for correct use of modelling notation, templates, or forms,
  • checking for completeness within each model,
  • comparing each model against other relevant models, checking for elements that are mentioned in one model but are missing in other models,
    and verifying that the elements are referenced consistently,
  • ensuring the terminology used in expressing the requirement is understandable to stakeholders and consistent with the use of those terms
    within the organization, and
  • adding examples where appropriate for clarification
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Verify requirement element

A

Characteristics of Requirements and Designs Quality
Verification Activities
Checklists

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Guidelines and Tools Verify requirement

A

Requirements Life Cycle Management Tools:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Validate Requirements

A

ensure that all requirements and designs align to the business requirements and support the delivery of needed value
ensure that stakeholder,
solution, and transition requirements align to the business requirements and that the designs satisfy the requirements.
In many cases, stakeholders have different,
conflicting needs and expectations that may be exposed through the validation process.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Validate Requirements input

A

Requirements (specified and modelled):
Validation activities may begin before requirements are completely verified. However, validation activities cannot be completed before requirements are completely verified

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Validate Requirements element

A

Identify Assumptions
Define Measurable Evaluation Criteria
Evaluate Alignment with Solution Scope

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Guidelines and Tools Validate Requirements

A

Business Objectives:
Future State Description
Potential Value:
Solution Scope:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Define Requirements Architecture p&d
ensure that the requirements collectively support one another to fully achieve the objectives * understand which models are appropriate for the domain, solution scope, and audience, * organize requirements into structures relevant to different stakeholders, * illustrate how requirements and models interact with and relate to each other, and show how the parts fit together into a meaningful whole, * ensure the requirements work together to achieve the overall objectives, * make trade-off decisions about requirements while considering the overall objectives. work in harmony with one another
26
Define Requirements Architecture input
Information Management Approach: Requirements (any state): Solution Scope
27
Define Requirements Architecture element
Requirements Viewpoints and Views Template Architectures Completeness Relate and Verify Requirements Relationships Business Analysis Information Architecture
28
Requirements Viewpoints and Views
Viewpoints provide templates for addressing the concerns of particular stakeholder groups * model types used for requirements, * attributes that are included and consistently used in different models, * model notations that are used, and * analytical approaches used to identify and maintain relevant relationships among models. viewpoints tell business analysts what information they should provide for each stakeholder group to address their concerns, while views describe the actual requirements and designs that are produced
29
Business analysts examine each relationship to ensure that the relationships satisfy the following quality criteria:
* Defined: there is a relationship and the type of the relationship is described. * Necessary: the relationship is necessary for understanding the requirements holistically. * Correct: the elements do have the relationship described. * Unambiguous: there are no relationships that link elements in two different and conflicting ways. * Consistent: relationships are described in the same way, using the same set of standard descriptions as defined in the viewpoints.
30
Define Design Options p&d
define the solution approach, identify opportunities to improve the business, allocate requirements across solution components, and represent design options that achieve the desired future state.
31
Define Design Options input
Change Strategy: Requirements (validated, prioritized): Requirements Architecture:
32
Define Design Options elements
Define Solution Approaches Identify Improvement Opportunities Requirements Allocation Describe Design Options
33
Solution approaches include
Create purchase Combination of both
34
Some common examples of opportunities include:
Increase Efficiencies: Improve Access to Information Identify Additional Capabilities:
35
Define Design Options Guidelines and Tools
Existing Solutions: Future State Description: Requirements (traced): Solution Scope:
36
Analyze Potential Value and Recommend Solution p&d
estimate the potential value for each design option and to establish which one is most appropriate to meet the enterprise’s requirements.
37
Analyze Potential Value and Recommend Solution input
Potential Value: Design Options:
38
Analyze Potential Value and Recommend Solution element
Expected Benefits Expected Costs Determine Value Assess Design Options and Recommend Solution
39
Assess Design Options and Recommend Solution
Available Resources: Constraints on the Solution: Dependencies between Requirements:
40
Analyze Potential Value and Recommend Solution g&t
Business Objectives: Current State Description Future State Description Risk Analysis Results Solution Scope:
41
Solution Evaluation tasks can be performed on solution components in varying stages of development:
Prototypes or Proofs of Concept: Pilot or Beta releases Operational releases:
42
Measure Solution Performance p&d
define performance measures and use the data collected to evaluate the effectiveness of a solution
43
Measure Solution Performance input
Business Objectives: Implemented Solution (external)
44
Define Solution Performance Measures
Quantitative Measures: Qualitative Measures:
45
Measure Solution Performance element
Define Solution Performance Measures Validate Performance Measures Collect Performance Measures
46
When collecting performance measures, business analysts consider:
Volume or Sample Size Frequency and Timing: Currency:
47
Measure Solution Performance g&t
Change Strategy: Future State Description: Requirements (validated) Solution Scope
48
Analyze Performance Measures element
Solution Performance versus Desired Value Risks Trends Accuracy Performance Variances
49
Analyze Performance Measures input
Potential Value Solution Performance Measures
50
Analyze Performance Measures g&t
* Change Strategy: * Future State Description: * Risk Analysis Results: * Solution Scope:
51
Assess Solution Limitations input
Implemented Solution (external): Solution Performance Analysis:
52
Assess Solution Limitations element
Identify Internal Solution Component Dependencies Investigate Solution Problems Impact Assessment
53
Assess Solution Limitations g&t
Change Strategy Risks Analysis Results Solution Scope
54
Assess Enterprise Limitations p&d
determine how factors external to the solution are restricting value realization: culture, operations, technical components, stakeholder interests, or reporting structures.
55
Assess Enterprise Limitations input
Current State Description: Implemented Solution (external) Solution Performance Analysis
56
Assess Enterprise Limitations element
Enterprise Culture Assessment Stakeholder Impact Analysis Organizational Structure Changes Operational Assessment
57
Guidelines and Tools Assess Enterprise Limitations
Business Objectives Change Strategy Future State Descriptions Risk Analysis Results Solution Scope
58
Recommend Actions to Increase Solution Value p&d
understand the factors that create differences between potential value and actual value, and to recommend a course of action to align them.
59
Recommend Actions to Increase Solution Value input
Enterprise Limitation Solution Limitation
60
Some common examples of recommendations that a business analyst may make include:
Do Nothing: Organizational Change Reduce Complexity of Interfaces: Eliminate Redundancy: Avoid Waste: Identify Additional Capabilities Retire the Solution ongoing cost versus initial investment: opportunity cost necessity: sunk cost:
61
Guidelines and Tools Recommend Actions to Increase Solution Value
Business Objectives: Current State Description Solution Scope:
62
Plan Business Analysis Approach p&d
define an appropriate method to conduct business analysis activities * align to the overall goals of the change, * coordinate the business analysis tasks with the activities and deliverables of the overall change, * include tasks to manage any risks that could reduce the quality of business analysis deliverables or impede task efficiency, and * leverage approaches and select techniques and tools that have historically worked well.
63
Plan Business Analysis Approach input
Needs
64
Plan Business Analysis Approach element
Planning Approach Formality and Level of Detail of Business Analysis Deliverables Business Analysis Activities Timing of Business Analysis Work Complexity and Risk Acceptance
65
Plan Business Analysis Approach g&t
Business Analysis Performance Assessment Business Policies Expert Judgment: Methodologies and Frameworks: Stakeholder Engagement Approach:
66
Plan Stakeholder Engagement p&d
plan an approach for establishing and maintaining effective working relationships with the stakeholders
67
Plan Stakeholder Engagement input
Needs Business Analysis Approach:
68
Plan Stakeholder Engagement element
- Perform Stakeholder Analysis Roles Attitudes Decision Making Authority Level of Power or Influence - Define Stakeholder Collaboration - Stakeholder Communication Needs
69
Guidelines and Tools Plan Stakeholder Engagement
Business Analysis Performance Assessment Change Strategy: Current State Description:
70
Plan Stakeholder Engagement stakeholder
Customers: ex Supplier: ex Domain Subject Matter Expert: End User: in Project Manager: Regulator Sponsor:
71
Plan Business Analysis Governance p&d
define how decisions are made about requirements and designs, including reviews, change control, approvals, and prioritization.
72
Plan Business Analysis Governance input
Business Analysis Approach Stakeholder Engagement Approach:
73
Plan Business Analysis Governance element
Decision Making Change Control Process Plan Prioritization Approach Plan for Approvals
74
Plan Business Analysis Governance g&t
Business Analysis Performance Assessment Business Policies Current State Description: Legal/Regulatory Information
75
Plan Business Analysis Information Management p&d
develop an approach for how business analysis information will be stored and accessed.
76
Plan Business Analysis Information Management input
Business Analysis Approach: Governance Approach Stakeholder Engagement Approach
77
Plan Business Analysis Information Management element
Organization of Business Analysis Information Level of Abstraction Plan Traceability Approach Plan for Requirements Reuse Storage and Access Requirements Attributes
78
Some commonly used requirements attributes include:
Absolute reference: Author Complexity: Ownership Priority Risks Source Stability Status Urgency
79
Plan Business Analysis Information Management g&t
Plan Business Analysis Information Management Information Management Tools: Business Policies: Legal/Regulatory Information:
80
Plan Business Analysis Information Management stakeholder
Domain Subject Matter Expert: Regulator: Sponsor:
81
Identify Business Analysis Performance Improvements p&d
assess business analysis work and to plan to improve processes where required.
82
Inputs Identify Business Analysis Performance Improvements
Business Analysis Approach: Business Analysis Approach:
83
Identify Business Analysis Performance Improvements element
Performance Analysis Assessment Measures Analyze Results recommend Actions for Improvement
84
Some possible Assessment measures are:
Accuracy and Completeness Knowledge Effectiveness: Organizational Support: Significance Strategic: Timeliness:
85
Once the analysis of performance results is complete, the business analyst engages the appropriate stakeholders to identify the following actions:
Preventive: Preventive: Preventive:
86
Guidelines and Tools
87

babok (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions