Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirement life cycle management - Coggle Diagram
Requirement life cycle management
Assess requirements changes
Inputs
Proposal change
Requirements
Designs
Elements
Assessment formality
Impact analysis
Benefit: will be gained by accepting the change
Cost: total cost to implement the change including the cost to make the change
Impact: the number of customers or business processes affected
Schedule: the impact to the existing delivery commitments
Urgency: the level of importance including the factors
Impact resolution
Approve, deny, or defer the proposed change
Impact and solutions resulting from the change analysis are to be documented and communicated to alll stakeholders
Guides and tools
Change strategy
Purpose and direction for changes, establishes the context for the changes, identifies the critical compomemts for change
Domain knowledge
Knowledge of and expertise in the business domain
Governance approach
Change control and decisison making processes
Legal Regultory infomation
Requirements architecture
Solution scope
Prioritize requirements
Inputs
Requirements and designs
Elements
Basic for prioritization
Benefit
Penalty
Cost
Risk
Dependencies
Time sensivity
Best before date of the requirement, after which implement of the requirement loses significant value
Stability
Likehood that the requirement will change, either because it requires further analysis
Regulatory or policy compliance
Challenges of prioritization
Each stakeholder may value something different
Have difficulty characterizing any requirement as a lower priority
Continual prioritization
Basic for prioritization may be different at various stages of the change
Stakeholder
Customer
Enduser
Implementation subject matter expert
Project management
Regulator
Sponsor
Trace Reuirement
Purpose: to ensure that requireations and designs at different levels are algined to one another and to manage the effects of the change to one level on the related requirements
Input: designs anf requirement
Tracibility enables:
Faster and simpler impact analysis
More reliable discovery of inconsistencies and gaps in requirements
Deeper insights into the scope and complexity of the change
Reliable assessments of which requirements have been addressed and which have not
Output: requirement(traced) and design(traced)
Elements:
Level of formality
When tracing requirement, BA consider the value and nature and use of the specific relationships
Relationships
Derive: a requirement is derived from another requirement, appropriate to link the requirement in different levels of abstraction
Depends
Necessity
Effort
Satisfy
Validate
Traceability repostiory: is the document and maintained manually or requirement management tools
Maintain requirement
Input: requirement and design
Elements
Maintain requireement
Maintain attributes
Requirement source, priority, complexity aid in managing each requirement
Reusing requirements
Are identified, clearly name, defined, stored in a manner
Within thr current intitative
Within similar inititatives
Within similar departments
Thougout the entire prganization
Reflect currunt state
Approve requirement
Input: requirement(verified) and design
Elements:
Understand stakholder roles
Conflic and issue management
Sought prior to requesting approval of requirements: how to secure decisisons and resolve conflics across an initiatives