7 Requirements Analysis and Design Definition 160528195229

Requirements Analysis
and Design Definition

IIBA Cairo Chapter
@_Darwishh
TODAY …
• Introduction (Requirement and Designs)
• Specify and Model Requirements
• Verify Requirements
• Validate Requirements
• Define Requirements Architecture
• Define Design Options
• Analyze Potential Value and Recommend Solutions
• Open discussion ….
Requirements Analysis and Design Definition 2
Introduction (Requirements and Designs)
Source: Requirements and Designs Webinar by IIBA

Introduction (Requirements and Designs)
Source: Requirements and Designs Webinar by IIBA

Introduction (Knowledge Area)
• Chapter 7 of BABOK v3
Tasks
BA performs To
Structure and Organize
Requirements
Practices

Introduction (Accomplishing Tasks)
Incrementally
Iteratively
6
Introduction (Input / Output Diagram)

Introduction (Business Analysis Core Concept Model)
Change Value Context
Need Solution Stakeholder

7.1 Specify and Model Requirements
Purpose & Guidelines

Description Inputs Elements
and tools
Techniques Stakeholders Output
9
Specify and model requirements
Analyze
Requirements
Purpose Elicitation Refine &
Results
Designs
Transform

Elicitation
1. Results
Inputs
May require expansion or clarification

Model Requirement
Matrices Diagrams
Analyze Requirements
What is missing What is unnecessary
2.
Elements Represent Requirements and Attributes
Characteristics Design Qualities
Implement the Appropriate Levels of Abstraction (Context)

Audience Type of Requirement

Modelling and Notation / Standards
Modelling tools (Software Apps)
Requirements architecture
3.
Guidelines
and Tools Requirements life cycle management tools
Solution scope

Acceptance and Business model

Data flow diagrams
evaluation criteria canvas
4.
Techniques
Prototyping User stories

5.
Stakeholders
Current operating state (As Is)
Key Concepts: Desired operating state (To Be)
Gaps between the states

Specified Modeled
6.
Outputs
Requirements


7.2 Verify Requirements
18
Verify Requirements
Meet quality standards

Specifications
Purpose and
Models
Usable for the purpose
they serve

Verify Requirements
Well
documented
Requirements
1. (specified and
Inputs modelled)
Well written

Verify Requirements
Characteristics of Requirements and Designs Quality
Complete, Atomic,
Feasible Prioritized Testable Understandable
Consistent Concise
Verification Activities
2.
compliance with Correct use of notations, Comparing models against
Elements organizational standards templates, forms other relevant models
Checklists
Standard set of qualifying elements important items are included

Verify Requirements
Recording
Requirements Organizing
Life Cycle
3. Management
Guidelines Tools
and Tools (Software to) Storing
Sharing

Verify Requirements
Acceptance and
Item Tracking
evaluation criteria
4.
Techniques
Metrics and Key
Performance Indicators Reviews
(KPI)

Verify Requirements
5.
Stakeholders

Verify Requirements
Requirements Designs
6.
Outputs
Verified

Verify Requirements

7.3 Validate Requirements
27
Validate Requirements
Support Business
Requirements
Requirements
Purpose and Designs
Deliver Business
Value needed

Well
documented
Requirements
(specified and
1. modelled)
Inputs
Well written
Validation cannot conclude until all requirements are completely verified

Identify Assumptions  Unprecedented requirements
Define Measurable Evaluation Criteria

2.
How successful the change has been after the solution is implemented.
Elements
Evaluate Alignment with Solution Scope (!)

Business Objectives
Future State Description
3.
Guidelines Potential Value
and Tools
Solution Scope

Acceptance and
Document Analysis Financial Analysis
Evaluation Criteria
Metrics and Key

4. Item Tracking Reviews Performance
Indicators (KPI)
Techniques
Risk Analysis
Management

5.
Stakeholders

Requirements Designs
6.
Outputs
Validated


7.4 Define Requirements
Architecture
36
Define Requirements Architecture
Collectively support
each other
Requirements
Fully achieve the
business objectives
Purpose
Requirements
Goal
Harmony

1- Information Management Approach
1. 2- Requirements (any state) (only once)

Inputs
3- Solution Scope

Requirements Viewpoints and Views
Template Architecture Frameworks
Industry Sector Organization
Completeness
2. Understandable Full story
Elements
Relate and Verify Requirements Relationships
Defined Necessary Correct Unambiguous Consistent
Business Analysis Information Architecture

Architecture Management Software

(Source control)
Legal / Regulatory Information

3.
Guidelines
and Tools
Methodologies and Frameworks

Functional Organizational
Data Modelling
Decomposition Modelling
4.
Techniques
Interviews and
Scope Modelling
Workshops

5.
Stakeholders

Completed
interrelationships
Complete Contextual
Requirements information
6.
Outputs
Requirement
Architecture


7.5 Define Design Options
45
Define Design Options
Opportunities to improve
Define Solution
Purpose Options
Desired Future State

Requirements
Change Requirements
1. Strategy
(validated,
Architecture
prioritized)
Inputs

Define Solution Approaches
Created Purchased Combination of Both
Identify Improvement Opportunities:
Increase Efficiency Improve Access to data Additional capabilities
2.
Elements Requirements Allocation
Solution Components Release
Describe Design Options:

Business Policy or Operational Organizational
Business Process
Business Role Business Decision structure

Existing Solutions
Future State Description
3.
Guidelines Requirements (traced)
and Tools
Solution Scope

Benchmarking and
Brainstorming Document Analysis
Market Analysis
Survey or
Interviews Workshops
Questionnaire
4.
Techniques
Root Cause
Lessons Learned Mind Mapping
Analysis
Vendor
Assessment

5.
Stakeholders

6. Design
Outputs Options


7.6 Analyze Potential Value
and Recommend Solution
54
Analyze Potential Value and Recommend Solution
Estimate Potential
Value
Design Options
The most appropriate

option
Purpose
Trade offs to
Best Solution
will be
made Option

Potential Design
1.
Value Options
Inputs

Expected Benefits
Expected Costs
2.
Elements
Determine Value
Assess Design Options and Recommend Solution

Business Objectives
Current State Description
3. Future State Description

Guidelines
and Tools
Risk Analysis Results
Solution Scope

Acceptance and
Business Model
Evaluation Brainstorming
Canvas
Criteria
Backlog Decision
Business Cases
Management Analysis
4.
Techniques Financial
Estimation Focus Groups
Analysis
Metrics and Key

Performance
Interviews
Indicators
(KPIs)

5.
Stakeholders

6. Solution
Recommendation
Outputs

Analyze Potential Value and Recommend
Solution

FULL STORY
Specify and Model Verify

•Specification •Verified
Elicitation Results •Models
Validate Requirements Deign and Solution

•Accepted Architecture Options
•Rejected •Organize •Solution 1
•Store •Solution 2
•Share •Solution N
Potential Value and

Recommend the Best
•Solution X Solution Evolution

Thank You

64

7 Requirements Analysis and Design Definition 160528195229

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7 Requirements Analysis and Design Definition 160528195229

Uploaded by

Copyright:

Available Formats

Requirements Analysis

and Design Definition

• Specify and Model Requirements

• Define Requirements Architecture

• Define Design Options

• Analyze Potential Value and Recommend Solutions

Source: Requirements and Designs Webinar by IIBA

Requirements Analysis and Design Definition 3

Source: Requirements and Designs Webinar by IIBA

Requirements Analysis and Design Definition 4

Requirements Analysis and Design Definition 5

Requirements Analysis and Design Definition 7

Change Value Context

Need Solution Stakeholder

Requirements Analysis and Design Definition 8

Purpose & Guidelines

Techniques Stakeholders Output

Requirements Analysis and Design Definition 10

May require expansion or clarification

Requirements Analysis and Design Definition 11

Implement the Appropriate Levels of Abstraction (Context)

Requirements Analysis and Design Definition 12

Modelling and Notation / Standards

Modelling tools (Software Apps)

Requirements Analysis and Design Definition 13

Acceptance and Business model

Requirements Analysis and Design Definition 14

Current operating state (As Is)

Key Concepts: Desired operating state (To Be)

Gaps between the states

Requirements Analysis and Design Definition 16

Requirements Analysis and Design Definition 17

Meet quality standards

Requirements Analysis and Design Definition 19

Requirements Analysis and Design Definition 20

Requirements Analysis and Design Definition 21

Requirements Analysis and Design Definition 22

Requirements Analysis and Design Definition 23

Requirements Analysis and Design Definition 24

Requirements Analysis and Design Definition 25

Requirements Analysis and Design Definition 26

Requirements Analysis and Design Definition 28

Validation cannot conclude until all requirements are completely verified

Requirements Analysis and Design Definition 29

Identify Assumptions  Unprecedented requirements

Define Measurable Evaluation Criteria

Evaluate Alignment with Solution Scope (!)

Requirements Analysis and Design Definition 30

Future State Description

Requirements Analysis and Design Definition 31

Metrics and Key

Requirements Analysis and Design Definition 32

Requirements Analysis and Design Definition 33

Requirements Analysis and Design Definition 34

Requirements Analysis and Design Definition 35

Requirements Analysis and Design Definition 37

1- Information Management Approach

1. 2- Requirements (any state) (only once)

Requirements Analysis and Design Definition 38

Requirements Viewpoints and Views

Template Architecture Frameworks

Industry Sector Organization

Defined Necessary Correct Unambiguous Consistent