requirements lifecycle management

Requirements Life Cycle Management

IIBA Cairo Chapter Osama Darwish

2

TODAY …

• Requirement (What, Why)

• Introduction

• Trace Requirements

• Maintain Requirements

• Prioritize Requirements

• Assess Requirements Changes

• Approve Requirements

• Open discussion ….


3

Requirements (What and Why)

Requirements Designs

Business Requirements

Stakeholder Requirements

Solution Requirements

Transition Requirements

4


Photo credit to IIBA webinars

5


Requirements Analysis and Design Definition

Photo credit to IIBA webinars

6

INTRODUCTION (Knowledge Area)


Tasks

Practices

BA performs To

Other work productssolution components

Requirements and

Designs

Maintain Relationships

Accuracy and Relevance

The effective reuse

Value, Urgency and Risks

Changing in Stakeholder needs

Help to reach agreement Approve

Assess

Prioritize

Trace

Maintain

7

INTRODUCTION (Tasks and Practices)


Tasks&

Practices

Primary

Supporting

Meaningful Relationships

Assessing Changes

Gain Consensus (Agreement)

Manage and maintain requirements and

design

Ensure that Requirements and Designs are aligned

together

Monitor R & D

Direct the Implementation

Ensure the future use of R & D

8

INTRODUCTION (Life cycle)


• The requirements life cycle:• begins with the representation of a business need as a

requirement,• continues through the development of a solution, and • ends when a solution and the requirements that represent it are

retired.

9

INTRODUCTION (knowledge Areas)


Requirements Life Cycle

Management

10

INTRODUCTION (Input / Output Diagram)


11

INTRODUCTION (Business Analysis Core Concept Model)


Change Need Solution

ValueContextStakeholder

12

5.1 Trace Requirements

Purpose Inputs Elements Guidelines and tools

Techniques Stakeholders Output

13

5.1 TRACE REQUIREMENTS

Purpose


Requirements

Aligned Togetrher

Manage the Effects of Change

Designs

Backward Traceability

Forward TraceabilityBenefit?

14


• Requirements Traceability is used• To help ensure that the solution conforms to the requirements• To assist in scope, change, risk, time, cost and communication

management• To detect missing functionality or to identify if there is

implemented functionality that is not supported by any requirement

• Requirements Traceability enables:• faster and simpler impact analysis• more reliable discovery of inconsistencies and gaps in

requirements• deeper insights into the scope and complexity of a change• reliable assessment of which requirements have been addressed

and which have not


15



16



17


1.

Inputs



May be traced to other requirements, solution components, and other work products

18


2.

Elements


Traceability Repository

Relationships

Derive Depends Satisfy Validate

Level of Formality

Effort Level

19


3.

Guidelines and Tools


Domain Knowledge

Information Management Approach

Legal/Regulatory Information

Requirements Management Tools/Repository

20


4.

Techniques


Business Rules Analysis• Trace Business Rules to

Requirements

Functional Decomposition• Break down solution into

smaller components

Process Modelling• Trace requirements to

future state process

Scope Modelling• Trace requirements to the

scope

21


5.

Stakeholders


Customer

Domain Subject Matter Expert

End User

Implementation Subject Matter Expert

Operational Support

Project Manager

Sponsor

Supplier

Tester

22


6.

Outputs


Traced


23

5.2 Maintain Requirements

24

5.2 MAINTAIN REQUIREMENTS

Purpose


Retain Accuracy and Consistency

Reuse in other solutions

Designs

An Ongoing Need

Requirements

25



26


1.

Inputs



includes goals, objectives, business requirements, stakeholder requirements, solution requirements and trasnsition requirements

Can be maintained as needed

27


2.

Elements


Reusing RequirementsCurrent initiative Similar initiatives Similar departments Organization

Maintain AttributesSource Priority Complexity

Maintain RequirementsOwner of the maintenance Maintain Relationships

28


Information Management Approach

3.



Indicates how requirements will be managed for reuse

29


4.

Techniques


Business Rules Analysis

• Similar Business Rules

Data Flow Diagrams• Similar

Information Flow

Data Modeling• Similar Data

Structure

Process Modeling

Document Analysis

Functional Decomposition

Use cases and Scenarios• Similar

Requirements

User stories• Similar

Requirements

30


5.

Stakeholders




Operational Support

Regulator

Tester

31


6.

Outputs


Maintained


Defined once Available for long-term usage

32

5.3 Prioritize Requirements

33

5.3 PRIORITIZE REQUIREMENTS

Purpose


An Ongoing Process

RequirementsRequirements Designs

Relative value of a requirement

Relative importance to stakeholders

Rank based on

34



35


1.

Inputs



TextPrototypeDiagramsIn any form

36


2.

Elements


Continual Prioritization

Customer, Business team and SW team

Challenges of Prioritization (Stakeholders)Value something different Characterize requirement as

a lower priorityIndicate priority to influence

the result

Basis for PrioritizationBenefit Cost Risk Time

37


3.



Business Constraints

Change Strategy

Domain Knowledge

Governance Approach

Requirements Architecture

Requirements Management Tools/Repository

Solution Scope

38


4.

Techniques


Backlog Management Business Cases Estimation

Financial Analysis Interviews Prioritization

Workshops

39


5.

Stakeholders


Customer

End User


Project Manager

Regulator

Sponsor

40


6.

Outputs


Prioritized


41

5.4 Assess Requirements Changes

42

5.4 ASSESS REQUIREMENTS CHANGES

Purpose


RequirementsRequirements DesignsChange Implication on

Risks, Opportunities or Constraints

Time or Resources

Business Value on business or stakeholders

Overall strategy

Considerations

43



44


1.

Inputs


Proposed Change

RequirementsDesigns

45


2.

Elements


Impact Resolution

Impact AnalysisBenefit Cost Schedule Urgency

Assessment FormalityInformation Importance Governance process

46


3.



Change Strategy

Domain Knowledge

Governance Approach


Requirements Architecture

Solution Scope

47


4.

Techniques


Business Case

Business Rules

AnalysisDecision Analysis

Document Analysis

Estimation Financial Analysis

Interface Analysis

Item Tracking

Risk Analysis and Management

Workshops Interviews

48


5.

Stakeholders


Customer


End User

Operational Support

Project Manager

Regulator

Sponsor

Tester

49


6.

Outputs


Assessed


50

5.5 Approve Requirements

51

5.5 APPROVE REQUIREMENTS

Purpose


Requirements


Agreement or

Approval (Stakeholders)

Obtain

Solution Implantation Starts To let

Formal

Informal

52



53

1.

Inputs




Verified Ready for development

54

2.

Elements



Track and Communicate Approval

Gain Consensus

Conflict and Issue Management

Understand Stakeholder Roles

55

3.




Change Strategy Governance Approach


56

4.

Techniques



Acceptance and Evaluation Criteria

Decision Analysis

Item Tracking

Reviews

Workshop

57

5.

Stakeholders



Customer


End User

Operational Support

Project Manager

Regulator

Sponsor

Tester

58

6.

Outputs



Approved


59

SUMMARY

• Introduction

• Trace Requirements

• Maintain Requirements

• Prioritize Requirements

• Assess Requirements Changes

• Approve Requirements


60

SUMMARY


Tasks

Practices

BA performs To

Other work productssolution components

Requirements and

Designs

Maintain Relationships

Accuracy and Relevance

The effective reuse

Value, Urgency and Risks

Changing in Stakeholder needs

Help to reach agreement Approve

Assess

Prioritize

Trace

Maintain

61

Thank You