1. Measuring Change Activity
Is a way to assess the stability of the requirements and to identify opportunities for process improvement
The following could be measured
The number of change requests received, open, and closed
The cumulative number of changes made including added, deleted, and modified requirements
The number of change requests that originated from each source
The number of changes proposed and made in each requirement since it was base-lined
The total effort devoted to handling changes

2. Recap

3. Software Engineering II
Lecture 37
Fakhar Lodhi

6. Traced
An SRS is traced if the origin of its requirements is clear. That means that the SRS includes references to earlier supportive documents

7. Traceable
An SRS is traceable if it written in a manner that facilitates the referencing of each individual requirement stated therein

8. Tracing Requirements It is important to trace requirements both ways
origin of a requirement
how is it implemented
This is a continuous process
Rationale of requirements must also be traced. This information is, typically, lost

9. Motivation for Requirement Traceability
Certification
Change impact analysis
Maintenance
Project tracking
Reengineering
Reuse
Risk reduction
Testing

10. Traceability Matrix Functional Specifications Quality Assurance Design
Comment from Arshad (Mar. 3, 1998)
Outline purpose of the slide
Should have a visual dependency graph also that represents information in the traceability matrix

11. Organized
An SRS is organized if requirements contained therein are easy to locate. This implies that requirements are arranged so that requirements that are related are co-related

12. How to Organize an SRS?
Clients/developers may have their own way of organizing an SRS
Standard templates developed by:
US Department of Defense
NASA
IEEE/ANSI Standard