1. Trace requirements

2. What do we mean by the term “Trace”? Why should we trace? 2 Requirements Life Cycle Management Trace Requirements

3. Requirements Life Cycle Management Trace Requirements Understanding req. traceability  Traceability is the ability to look at a requirement, and other elements to which it is related  Links business requirements to stakeholder, and solution requirements, to associated artifacts, and to solution components Requirements Life Cycle Management Trace Requirements 3

4. Requirements Life Cycle Management Trace Requirements Purpose  To ensure requirements and designs at different levels are aligned to one another  To manage the effects of change to one level on related requirements and designs 4

5. Requirements Life Cycle Management Trace Requirements 3 types of traceability  Backward traceability (Derivation)  Forward traceability (Allocation)  Relationship to other requirements 5

6. Requirements Life Cycle Management Trace Requirements Sample Traceability Matrix Req IDRequirementUser ContactUse caseRelease 10000Manage scheduleLily VasantiniABCT SRS-Schedule Management - v12.0.xlsx 3 20000Manage defectShalini PaulABCT SRS-Defect Management - v12.0.xlsx 2 30000Manage riskSara LeeABCT SRS-Risk Management - v12.0.xlsx 4 40000Manage requirementsNori MasaABCT SRS-Backlog Management - v12.0.xlsx 5 50000Track effortGajendra BattallaABCT SRS-Effort Management - v12.0.xlsx 1 60000Manage audit and complianceRebecca RandadABCT SRS-Audit Management - v12.0.xlsx 6 6

7. Requirements Life Cycle Management Trace Requirements Benefits of traceability  Ensures solution conforms to the requirements  Helps in managing scope, risk, time, req. changes, cost, and communication  Detects missing functionalities 7

8. Requirements Life Cycle Management Trace Requirements Benefits of traceability  Assists in impact analysis for requirements changes  Ensures requirements coverage: How business objectives are implemented  Requirements allocation 8

9. Requirements Life Cycle Management Trace Requirements Elements Level of formality Relationships Traceability repositories Traced requirements Elements of traceability 9

10. Requirements Life Cycle Management Trace Requirements Level of formality  Consider value provided, nature and use while tracing requirements  Traceability is expensive  Use right judgment 10

11. Requirements Life Cycle Management Trace Requirements Elements to be part of Traceability  1 business requirement  50 stakeholder requirements  500 solution requirements  5000 solution components  100 data base objects  800 procedures  100 user interfaces  2000 test cases 11

12. Requirements Life Cycle Management Trace Requirements Relationships type  Derive  Depend  Satisfy  Validate Req IDRequirementUser ContactUse caseRelease 10000Manage scheduleLily VasantiniABCT SRS-Schedule Management - v12.0.xlsx 3 20000Manage defectShalini PaulABCT SRS-Defect Management - v12.0.xlsx 2 30000Manage riskSara LeeABCT SRS-Risk Management - v12.0.xlsx 4 40000Manage requirements Nori MasaABCT SRS-Backlog Management - v12.0.xlsx 5 12

13. Requirements Life Cycle Management Trace Requirements Relationships: Derive (Parent – Child)  When one requirement is derived from the other  Stakeholder requirements are derived from business requirements  Solution requirements are derived from stakeholder requirements Biz Req Stakeholder Req Solution Req 13

14. Requirements Life Cycle Management Trace Requirements Relationship : Depends  One requirement can be implemented only if the other has been implemented or easier to implement if the other is implemented  Shopping cart is dependent on payment gateway 14

15. Requirements Life Cycle Management Trace Requirements Relationship : Satisfy  Relationship between an implementation element and the requirements it is satisfying  A particular component satisfies a requirements 15

16. Requirements Life Cycle Management Trace Requirements Relationship : Validate  A relation between a requirement and its test cases to validate whether the solution fulfills the requirement  Test cases validate requirements 16

17. Requirements Life Cycle Management Trace Requirements Traceability repositories  A tool or manual approach to maintain requirements traceabilities 17

18. Requirements Life Cycle Management Trace Requirements Summarizing Purpose: To ensure requirements and designs at different levels are aligned to one another and to manage the effects of change to one level on related requirements and designs. InputsStakeholdersOutputs Requirements Designs All except regulator Requirements (Traced) Designs (Traced) Guidelines and Tools: Domain knowledge, Information management approach, Legal / Regulatory information, Requirements management tools / repository. Techniques: Business rules analysis, Functional decomposition, Process modelling, Scope modelling. 18