1. Team Skill 6 - Building The Right System Part 2: Traceability, Change and Quality (Chapters 27-29 of the requirements text) CSSE 371 Software Requirements and Specification Don Bagert, Rose-Hulman Institute of Technology October 11, 2005 Thanks to Mark Ardis and Steve Chenoweth for some of the slides included. Traceability in the US food supply, from http://www.ers.usda.gov/Briefing/Traceability/overview.htm

2. 2 Outline Tracing Requirements Managing Requirements Assessing Requirements Quality

3. 3 Tracing Requirements

4. 4 Traceability: Primary Questions Why is tracing important? What mechanisms are used for tracing? Why we care – remember this triangle?

5. 5 Traceability: The Problem How do you know, if you’re at one of these later stages, that you have a requirements fault?

6. 6 In general, how to trace…

7. 7 With use cases, for instance…

8. 8 Managing Requirements

9. 9 Managing Change: Primary Questions How do you capture change requests? How do you respond to these (individually & overall)? How does this tie-in with tracing requirements?

10. 10 A Process for Managing Change – 1/3 Step 1: Recognize that change is inevitable, and plan for it

11. 11 A Process for Managing Change – 2/3 Step 2: Baseline the requirements –This means they are signed-off on, and –From then on, they fall under change control – see below Step 3: Establish a single channel to control change –No ad hoc additions –No ad hoc fixes, either

12. 12 A Process for Managing Change – 3/3 In  this big picture, you especially need to know what “release management”  is! Figure on middle right from http://www.debian.org/vote/2002/platforms/raphael Step 4: Use a Change Control System to Capture Changes Step 5: Manage Change Hierarchically

13. 13 Assessing Requirements Quality

14. 14 Quality Issues Products vs. Processes Review Methods Checklists

15. 15 Products vs. Processes Organizations that produce high-quality products invest in high-quality processes. Product quality can be measured through testing. How can we measure process quality?

16. 16 Review Methods Informal –Ask a peer to read and give comments Formal –Ask a peer to prepare for review –Record and report results of review Active –Interrogate reviewer

17. 17 Checklists Look for anticipated defects Some defects apply to almost all artifacts –Does the artifact exist? Some defects are artifact-specific –Have you identified all stakeholders?

18. 18 Problem Statement Checklist 1.Has a problem statement been drafted? 2.Is it written in an easy-to-understand way? 3.Does the team understand it? 4.Has it been circulated for agreement to the key stakeholders, including management? 5.Do the team members have agreement that this is the problem they are trying to solve?

19. 19 Supplementary Specification Checklist (1/2) 1.Have you established an appropriate template? 2.Are all non-functional requirements included in the supplementary specification? 3.Have requirements for usability, reliability, performance and supportability been captured?

20. 20 Supplementary Specification Checklist (2/2) 4.Have design constraints been identified? 5.Have supplementary requirements been linked to use cases where appropriate?