7 requirements-analysis-and-design-definition-160528195229

Requirements Analysis and Design Definition

IIBA Cairo Chapter

@_Darwishh

2

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 ….


3

Introduction (Requirements and Designs)

Source: Requirements and Designs Webinar by IIBA


4

Introduction (Requirements and Designs)


Source: Requirements and Designs Webinar by IIBA

5

Introduction (Knowledge Area)

• Chapter 7 of BABOK v3


Tasks

Practices

Structure and Organize Requirements

BA performs To

6

Introduction (Accomplishing Tasks)

Incrementally

Iteratively

7

Introduction (Input / Output Diagram)


8

Introduction (Business Analysis Core Concept Model)


Change

Need Solution

Value Context

Stakeholder

9

7.1 Specify and Model Requirements

Purpose & Description Inputs Elements Guidelines

and tools

Techniques Stakeholders Output

10

Specify and model requirements

Purpose


Elicitation Results

Analyze

Refine

Transform

Requirements &

Designs

11


Elicitation Results

1.

Inputs


May require expansion or clarification

12


2.

Elements


Implement the Appropriate Levels of Abstraction (Context)Audience Type of Requirement

Represent Requirements and AttributesCharacteristics Design Qualities

Analyze RequirementsWhat is missing What is unnecessary

Model RequirementMatrices Diagrams

13


Modelling and Notation / Standards

Modelling tools (Software Apps)

Requirements architecture

Requirements life cycle management tools

Solution scope

3.

Guidelines and Tools


14


Acceptance and evaluation criteria Business model canvas

Data flow diagrams Prototyping

User stories

4.

Techniques


15


5.

Stakeholders


Key Concepts:

16


Requirements

Specified Modeled

6.

Outputs


17



18

7.2 Verify Requirements

19

Verify Requirements

Purpose


Specifications and

Models

Meet quality standards

Usable for the purpose they

serve

20

Verify Requirements

1.

Inputs


Requirements

(specified and

modelled)

Well documented

Well written

21

Verify Requirements

2.

Elements


22

Verify Requirements

Requirements Life Cycle Management Tools (Software to)

Recording

Organizing

Storing

Sharing

3.



23

Verify Requirements

Acceptance and evaluation criteria Item Tracking

Metrics and Key Performance

Indicators (KPI)Reviews

4. Techniques


24

Verify Requirements

5.

Stakeholders


25

Verify Requirements

6.

Outputs


Verified

Requirements Designs

26

Verify Requirements


27

7.3 Validate Requirements

28

Validate Requirements

Purpose


Requirements and Designs

Support Business

RequirementsDeliver

Business Value needed

29


1.

Inputs


Validation cannot conclude until all requirements are completely verified

Requirements

(specified and

modelled)

Well documented

Well written

30


2.

Elements


31

Validate RequirementsBusiness Objectives

Future State Description

Potential Value

Solution Scope

3.



32


Acceptance and Evaluation Criteria Document Analysis Financial Analysis

Item Tracking ReviewsMetrics and Key

Performance Indicators (KPI)

Risk Analysis Management

4.

Techniques


33


5.

Stakeholders


34


6.

Outputs


Validated

Requirements Designs

35



36

7.4 Define Requirements Architecture

37

Define Requirements Architecture

Purpose


RequirementsCollectively

support each other

Fully achieve the business

objectives

Goal

Requirements

Harmony

38


1- Information Management Approach

2- Requirements (any state) (only once)

3- Solution Scope

1.

Inputs


39


2.

Elements


40


Architecture Management Software (Source control)

Legal / Regulatory Information

Methodologies and Frameworks 3.



41


Data Modelling Functional Decomposition

Organizational Modelling Scope Modelling

Interviews and Workshops

4.

Techniques


42


5.

Stakeholders


43


6.

Outputs


Requirement

Architecture

Complete Requiremen

ts

Completed interrelation

shipsContextual information

44



45

7.5 Define Design Options

46

Define Design Options

Purpose


Define Solution Options

Opportunities to improve

Desired Future State

47


Requirements

Architecture

Requirements

(validated, prioritized)

Change Strategy

1. Inputs


48


2. Elements


49


Existing Solutions


Requirements (traced)

Solution Scope

3.



50


Benchmarking and Market Analysis Brainstorming Document Analysis

Interviews Workshops Survey or Questionnaire

Lessons Learned Mind Mapping Root Cause Analysis

Vendor Assessment

4.

Techniques


51


5.

Stakeholders


52


6.

Outputs


Design Options

53



54

7.6 Analyze Potential Value and Recommend Solution

55

Analyze Potential Value and Recommend Solution

Purpose


Design Options Estimate Potential Value

The most appropriate

optionTrade offs will be made

Best Solution Option

to

56


1.

Inputs


Design OptionsPotential Value

57


2.

Elements


58


Business Objectives

Current State Description


Risk Analysis Results

Solution Scope

3.



59

Analyze Potential Value and Recommend SolutionAcceptance

and Evaluation Criteria

Business Model Canvas

Brainstorming

Business Cases

Backlog Management

Decision Analysis

Estimation

Focus Groups

Financial Analysis

Interviews

Metrics and Key Performance

Indicators (KPIs)

4.

Techniques


60


5.

Stakeholders


61


6.

Outputs


Solution Recommendation

62



63

FULL STORY


Elicitation Results

Specify and Model•Specification•Models

Verify•Verified

Validate•Accepted•Rejected

Requirements Architecture•Organize•Store•Share

Deign and Solution Options•Solution 1•Solution 2•Solution N

64

Thank You