Please enable JavaScript.
Coggle requires JavaScript to display documents.
Requirements Life Cycle Management (Trace Requirements (Stakeholders…
Requirements Life Cycle Management
Trace Requirements
Purpose: to ensure that requirements and designs at
different levels are aligned to one another, and to manage the effects of change
to one level on related requirements.
Inputs
Requirements
Designs
Elements
Level of formality
Relationships
Derive: when a requirement is derived from another.
Depends: Necessity: when one has to be implemented so the other can be implemented. Effort: When it is easier to implement if the other is implemented.
Satisfy: when an implementation satisfies a requirement
Validate: relationship between a requirement and a test case
Traceability Repository: documenting and maintaining traceability either manually or using tools
Guidelines
Domain knowledge
Information Management Approach
Legal / Regulatory information
Requirements management repository / tool
Techniques
Business Rules analysis
Functional decomposition
Process modelling
Scope modeling
Stakeholders
Customer
Domain SME
End user
Implementation SME
Operational Support
Project Manager
Sponsor
Supplier
Tester
Output
Requirements (traced)
Designs (traced)
Maintain Requirements
Purpose: to retain requirement accuracy and
consistency throughout and beyond the change during the entire requirements
life cycle, and to support reuse of requirements in other solutions
Inputs
requirements
designs
Elements
Maintain requirements: must be clearly named, defined and easily accessible by stakeholders
Maintain attributes: such as requirements source, priority and complexity
Reuse requirements: within similar departments, similar initiatives, current initiative, throughout entire organization
Guidelines
Information management approach
Techniques
Business rules anaylsis
data flow diagrams
data modelling
Document analysis
functional decomposition
Process modelling
Use cases and scenarios
user stories
Stakeholders
Domain SME
Implementation SME
Operational support
Regulator
Tester
Output
Requirements (maintained)
Designs (maintained)
Prioritise Requirements
Purpose: rank in the order of relative importance
Inputs
Requirements
Designs
Elements
!. Basis for prioritization
Benefit
Penalty of not implementing
Cost
Risk
Dependencies
Time sensitivity
Stability
Regulatory or Policy compliance
Challenges of prioritization: stakeholders may have different methods to prioritize, may not be able to trade off, may indicate priority to influence a desired result
Continual prioritization
Guidelines
Business contraints
Change strategy
Domain Knowledge
Governance approach
Requirements architecture
Requirements management tool / repository
Solution scope
Techniques
Backlog management
business cases
Decision analysis
Estimation
Financial analysis
Interviews
Item tracking
prioritization
Risk analysis and management
Workshops
Stakeholders
Customer
end user
Implementation SME
PM
Regulator
Sponsor
Output
Requirements (Prioritized)
Designs (Prioritized)
Assess Requirements
Purpose: Evaluate the implications of proposed changes to requirements and designs
Inputs
Proposed change
Requirements
Designs
Elements
Assessment formality
Impact analysis: traceability is a useful tool. BA asses the following
Benefit
Cost
Impact
Schedule
Urgency
Impact resolution : approvals, docomentation, communication..
Guidelines
Change Strategy
Domain Knowledge
Governance approach
Legal / regulatory info
Requirements Architecture
Solution scope
Techniques
Business cases
Business Rules analysis
Decision analysis
Document analysis
Estimation
financial analysis
Interface analysis
Interviews
item tracking
Risk analysis and management
workshops
Stakeholders
Customer
Domain SME
End user
Operation support
PM
Regulator
Sponsor
Tester
Output
Requirements change assessment
Designs change assessment
Approve requirements
Purpose: to gain approval for BA process to continue or solution implementation to start
Inputs
Requirements (verified)
Designs
Elements
Understand stakeholder roles (who should approve.. )
Conflict and issue management
Gain consensus
4.Track and communicate approval
Guidelines
Change strategy
Governance Approach
egal / regulatory infomation
Requirements management tools / repository
Solution scope
Techniques
Acceptance and evaluation criteria
Decision analysis
Item tracking
reviews
workshops
Stakeholders
Output
Requirements (approved)
Designs (approved)