Upload
osama-darwish
View
566
Download
1
Embed Size (px)
Citation preview
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 ….
Requirements Life Cycle Management
3
Requirements (What and Why)
Requirements Designs
Business Requirements
Stakeholder Requirements
Solution Requirements
Transition Requirements
4
Requirements (What and Why)
Photo credit to IIBA webinars
5
Requirements (What and Why)
Requirements Analysis and Design Definition
Photo credit to IIBA webinars
6
INTRODUCTION (Knowledge Area)
Requirements Analysis and Design Definition
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)
Requirements Analysis and Design Definition
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)
Requirements Analysis and Design Definition
• 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
Requirements Life Cycle
Management
10
INTRODUCTION (Input / Output Diagram)
Requirements Life Cycle Management
11
INTRODUCTION (Business Analysis Core Concept Model)
Requirements Analysis and Design Definition
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 Analysis and Design Definition
Requirements
Aligned Togetrher
Manage the Effects of Change
Designs
Backward Traceability
Forward TraceabilityBenefit?
14
5.1 TRACE REQUIREMENTS
• 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
Requirements Life Cycle Management
15
5.1 TRACE REQUIREMENTS
Requirements Life Cycle Management
16
5.1 TRACE REQUIREMENTS
Requirements Life Cycle Management
17
5.1 TRACE REQUIREMENTS
1.
Inputs
Requirements Life Cycle Management
Requirements Designs
May be traced to other requirements, solution components, and other work products
18
5.1 TRACE REQUIREMENTS
2.
Elements
Requirements Life Cycle Management
Traceability Repository
Relationships
Derive Depends Satisfy Validate
Level of Formality
Effort Level
19
5.1 TRACE REQUIREMENTS
3.
Guidelines and Tools
Requirements Life Cycle Management
Domain Knowledge
Information Management Approach
Legal/Regulatory Information
Requirements Management Tools/Repository
20
5.1 TRACE REQUIREMENTS
4.
Techniques
Requirements Life Cycle Management
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.1 TRACE REQUIREMENTS
5.
Stakeholders
Requirements Life Cycle Management
Customer
Domain Subject Matter Expert
End User
Implementation Subject Matter Expert
Operational Support
Project Manager
Sponsor
Supplier
Tester
22
5.1 TRACE REQUIREMENTS
6.
Outputs
Requirements Life Cycle Management
Traced
Requirements Designs
23
5.2 Maintain Requirements
24
5.2 MAINTAIN REQUIREMENTS
Purpose
Requirements Analysis and Design Definition
Retain Accuracy and Consistency
Reuse in other solutions
Designs
An Ongoing Need
Requirements
25
5.2 MAINTAIN REQUIREMENTS
Requirements Life Cycle Management
26
5.2 MAINTAIN REQUIREMENTS
1.
Inputs
Requirements Life Cycle Management
Requirements Designs
includes goals, objectives, business requirements, stakeholder requirements, solution requirements and trasnsition requirements
Can be maintained as needed
27
5.2 MAINTAIN REQUIREMENTS
2.
Elements
Requirements Life Cycle Management
Reusing RequirementsCurrent initiative Similar initiatives Similar departments Organization
Maintain AttributesSource Priority Complexity
Maintain RequirementsOwner of the maintenance Maintain Relationships
28
5.2 MAINTAIN REQUIREMENTS
Information Management Approach
3.
Guidelines and Tools
Requirements Life Cycle Management
Indicates how requirements will be managed for reuse
29
5.2 MAINTAIN REQUIREMENTS
4.
Techniques
Requirements Life Cycle Management
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.2 MAINTAIN REQUIREMENTS
5.
Stakeholders
Requirements Life Cycle Management
Domain Subject Matter Expert
Implementation Subject Matter Expert
Operational Support
Regulator
Tester
31
5.2 MAINTAIN REQUIREMENTS
6.
Outputs
Requirements Life Cycle Management
Maintained
Requirements Designs
Defined once Available for long-term usage
32
5.3 Prioritize Requirements
33
5.3 PRIORITIZE REQUIREMENTS
Purpose
Requirements Analysis and Design Definition
An Ongoing Process
RequirementsRequirements Designs
Relative value of a requirement
Relative importance to stakeholders
Rank based on
34
5.3 PRIORITIZE REQUIREMENTS
Requirements Life Cycle Management
35
5.3 PRIORITIZE REQUIREMENTS
1.
Inputs
Requirements Life Cycle Management
Requirements Designs
TextPrototypeDiagramsIn any form
36
5.3 PRIORITIZE REQUIREMENTS
2.
Elements
Requirements Life Cycle Management
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
5.3 PRIORITIZE REQUIREMENTS
3.
Guidelines and Tools
Requirements Life Cycle Management
Business Constraints
Change Strategy
Domain Knowledge
Governance Approach
Requirements Architecture
Requirements Management Tools/Repository
Solution Scope
38
5.3 PRIORITIZE REQUIREMENTS
4.
Techniques
Requirements Life Cycle Management
Backlog Management Business Cases Estimation
Financial Analysis Interviews Prioritization
Workshops
39
5.3 PRIORITIZE REQUIREMENTS
5.
Stakeholders
Requirements Life Cycle Management
Customer
End User
Implementation Subject Matter Expert
Project Manager
Regulator
Sponsor
40
5.3 PRIORITIZE REQUIREMENTS
6.
Outputs
Requirements Life Cycle Management
Prioritized
Requirements Designs
41
5.4 Assess Requirements Changes
42
5.4 ASSESS REQUIREMENTS CHANGES
Purpose
Requirements Analysis and Design Definition
RequirementsRequirements DesignsChange Implication on
Risks, Opportunities or Constraints
Time or Resources
Business Value on business or stakeholders
Overall strategy
Considerations
43
5.4 ASSESS REQUIREMENTS CHANGES
Requirements Life Cycle Management
44
5.4 ASSESS REQUIREMENTS CHANGES
1.
Inputs
Requirements Life Cycle Management
Proposed Change
RequirementsDesigns
45
5.4 ASSESS REQUIREMENTS CHANGES
2.
Elements
Requirements Life Cycle Management
Impact Resolution
Impact AnalysisBenefit Cost Schedule Urgency
Assessment FormalityInformation Importance Governance process
46
5.4 ASSESS REQUIREMENTS CHANGES
3.
Guidelines and Tools
Requirements Life Cycle Management
Change Strategy
Domain Knowledge
Governance Approach
Legal/Regulatory Information
Requirements Architecture
Solution Scope
47
5.4 ASSESS REQUIREMENTS CHANGES
4.
Techniques
Requirements Life Cycle Management
Business Case
Business Rules
AnalysisDecision Analysis
Document Analysis
Estimation Financial Analysis
Interface Analysis
Item Tracking
Risk Analysis and Management
Workshops Interviews
48
5.4 ASSESS REQUIREMENTS CHANGES
5.
Stakeholders
Requirements Life Cycle Management
Customer
Domain Subject Matter Expert
End User
Operational Support
Project Manager
Regulator
Sponsor
Tester
49
5.4 ASSESS REQUIREMENTS CHANGES
6.
Outputs
Requirements Life Cycle Management
Assessed
Requirements Designs
50
5.5 Approve Requirements
51
5.5 APPROVE REQUIREMENTS
Purpose
Requirements Analysis and Design Definition
Requirements
Requirements Designs
Agreement or
Approval (Stakeholders)
Obtain
Solution Implantation Starts To let
Formal
Informal
52
5.5 Approve Requirements
Requirements Life Cycle Management
53
1.
Inputs
5.5 Approve Requirements
Requirements Life Cycle Management
Requirements Designs
Verified Ready for development
54
2.
Elements
5.5 Approve Requirements
Requirements Life Cycle Management
Track and Communicate Approval
Gain Consensus
Conflict and Issue Management
Understand Stakeholder Roles
55
3.
Guidelines and Tools
5.5 Approve Requirements
Requirements Life Cycle Management
Change Strategy Governance Approach
Legal/Regulatory Information
56
4.
Techniques
5.5 Approve Requirements
Requirements Life Cycle Management
Acceptance and Evaluation Criteria
Decision Analysis
Item Tracking
Reviews
Workshop
57
5.
Stakeholders
5.5 Approve Requirements
Requirements Life Cycle Management
Customer
Domain Subject Matter Expert
End User
Operational Support
Project Manager
Regulator
Sponsor
Tester
58
6.
Outputs
5.5 Approve Requirements
Requirements Life Cycle Management
Approved
Requirements Designs
59
SUMMARY
• Introduction
• Trace Requirements
• Maintain Requirements
• Prioritize Requirements
• Assess Requirements Changes
• Approve Requirements
Requirements Life Cycle Management
60
SUMMARY
Requirements Analysis and Design Definition
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