Please enable JavaScript.
Coggle requires JavaScript to display documents.
5.0 Req Life Cycle Mgmt - Coggle Diagram
5.0 Req Life Cycle Mgmt
5.1) Trace
Requirements
A)) Levels of formality
- Effort increases by number of requirements therefore you need to consider effort vs, value
B) Relationships - several types to consider
- Derive - solution requirement derived from a business requirement (e.g. to allow only authorised users to access a system - a login screen will be created)
- Depends - when requirement depends on another requirement
- necessity - when it only make sense to implement if related requirement is also implemented
- effort - easier to implement if a related requirement is also implemented
- Satisfy - does the implemented solution satisfy the requirement
- Validate - a check (for example test case) that validates the solution fulfils the requirement
C) Traceability Repository
- Requirements traceability is documented and maintained in accordance with the BA approach
- Requirement management tool can be used and provides significant benefit when there is a large number of requirements
-
-
-
5.5) Approve
Requirements
B) Conflict and issue management
- Seek consensus before requesting requirements approval
- Approach to secure decisions and resolve conflicts is outlined in the Plan BA Governance
- BA facilitates Stakeholder conflicts
C) Gain Consensus
- BA responsible for presents to all stakeholders and to gain approval and consensus
- Approaches defined within the Plan BA Governance + Communicate BA info
A) Understand stakeholder roles
- Approval process is defined by the Plan BA Governance
- And helps understand stakeholders roles, authority levels and decision makers and sign off authority
- Also consider stakeholders who can influence decisions but have no approval authority
D) Track and Communicate Approval
- BA records approval decisions and decision status (possible using requirements maintenance and tracking tools)
- Also audit history should be used