1. Traceability, Change and Quality – Chapters 27-29 Requirements Text Sriram Mohan/Steve Chenoweth

2. Traceability: Primary Questions Why is tracing important? 2 Why we care – remember this triangle?

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

4. In general, how to trace… 4 Use Traceability matrices

5. Tracing User Needs to Features 5 Feature 1Feature 2...Feature n Need 1X Need 2X …XX Need mX

6. Tracing Features to Use Cases 6 Use Case 1 Use Case 2...Use Case n Feature 1X Feature 2X …XX Feature 3X

7. Tracing Requirements to Implementation 7

8. Tool Support Spreadsheets ◦ Maintaining and updating the links is difficult Relational Databases Requirements Management Software ◦ Extra Credit: Find two web based requirements management software and briefly describe the features they support. Submit using Angel (Lessons – Extra Credit – Week 6 – Requirements Management Software) 8

9. Factors for Change External Internal Unofficial sources contributed up to half of the total scope of the project 9

10. 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

11. A Process for Managing Change 11 Step 1: Recognize that change is inevitable, and plan for it

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

13. A Process for Managing Change 13 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

14. Follow the link There is a dependency between the various artifacts involved in requirements mgmt Follow the chain and make sure that the change is propagated 14

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? 15

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 16

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? 17

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? 18

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

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

21. Extra Credit How are requirements captured in the agile and extreme methodologies? Read Chapter 30 and write a report. (Lessons -Extra Credit - Week 6 - Requirements in an agile world)