babok Flashcards
Business Analysis Planning and Monitoring
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
Elicitation and Collaboration
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
Requirements Life Cycle Management
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
Strategy Analysis
6.1 Analyze Current State 103
6.2 Define Future State 110
6.3 Assess Risks 120
6.4 Define Change Strategy 124
Requirements Analysis and Design Definition
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
Solution Evaluation
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
Core Concept
Change
Need
Solution
Stakeholder
Value
Context
classification schema describes requirements:
Business requirements:
Stakeholder requirements:
Solution requirements:
* functional requirements:
* non-functional requirements or quality of service requirements:
* Transition requirements:
Specify and Model Requirements
analyze, synthesize, and refine elicitation results into requirements and designs.
Model Requirements
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.
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:
People and Roles
rationale
activity flow
capability
data and information
element of Specify and Model Requirements
Model Requirements
Analyze Requirements
Represent Requirements and Attributes
Implement the Appropriate Levels of Abstraction
Business analysis information is decomposed into components to further examine for:
- 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.
Guidelines and Tools verify re quirement
Modelling Notations/Standards:
Modelling Tools
Requirements Architecture
Requirements Life Cycle Management Tools
Solution Scope:
Verify Requirements p&d
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
Verify Requirements input
Requirements (specified and modelled)
Characteristics of Requirements and Designs Quality
Atomic
complete
concise
understandable
consistent
unambiguous
prioritized
testable
Verification Activities
- 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
Verify requirement element
Characteristics of Requirements and Designs Quality
Verification Activities
Checklists
Guidelines and Tools Verify requirement
Requirements Life Cycle Management Tools:
Validate Requirements
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.
Validate Requirements input
Requirements (specified and modelled):
Validation activities may begin before requirements are completely verified. However, validation activities cannot be completed before requirements are completely verified
Validate Requirements element
Identify Assumptions
Define Measurable Evaluation Criteria
Evaluate Alignment with Solution Scope
Guidelines and Tools Validate Requirements
Business Objectives:
Future State Description
Potential Value:
Solution Scope:
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
Define Requirements Architecture input
Information Management Approach:
Requirements (any state):
Solution Scope
Define Requirements Architecture element
Requirements Viewpoints and Views
Template Architectures
Completeness
Relate and Verify Requirements Relationships
Business Analysis Information Architecture
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
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.
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.
Define Design Options input
Change Strategy:
Requirements (validated, prioritized):
Requirements Architecture:
Define Design Options elements
Define Solution Approaches
Identify Improvement Opportunities
Requirements Allocation
Describe Design Options
Solution approaches include
Create
purchase
Combination of both
Some common examples of opportunities include:
Increase Efficiencies:
Improve Access to Information
Identify Additional Capabilities:
