Chapter Note

Chapter 29 Links in the Requirements Chain

© Karl E. Wiegers

1

2

29.1 Motivation for Tracing Requirements

 Certification - to certify that all requirements were implemented

 Change Control Analysis - to allow more accurate and complete impact analysis

 Maintenance - to allow making the changes correctly and completely during maintenance

3

 Project Tracking – to have accurate record of implementation status

 Reengineering - to identify components that need to be replaced

 Reuse - to identify reusable components in requirements, design, code and test

 Risk Reduction – reduces the risk if a team member leaves

 Testing - to identify the components in case of defects

4

29.2 Tracing Requirements

5

6

Possible traceability links

29.3 Requirements Traceability Matrix

 Represents the links between the requirements and other system elements

 Types of cardinality of links one-to-one, one-to-many, many-to-many

7

Where the Traceability Links Might Come From

8

9

Requirement Traceability Matrix 1

10

Shows two ways!

29.4 Requirements Traceability Implementation Procedure 1. Select the link relationship to implement 2. Choose the type of traceability matrix (1 or 2) 3. Identify the parts of the product for which to

maintain the traceability info 4. Modify the process to remind the developer to

update the links

11

5. Tag the components to identify them individually 6. Identify people for supplying link info, coordinate

and manage the link activities 7. Educate the team about the concept and

importance of links 8. Collect the traceability info from participants and

implement as development continues 9. Audit the traceability time-to-time

12

E N D

13