1. Chapter 26 Quality Management Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman

3. Software Quality Conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software.

5. Software Quality Assurance Formal Technical Reviews Test Planning & Review Measurement Analysis & Reporting Process Definition & Standards

8. Why SQA Activities Pay Off? cost to find and fix a defect 100 10 log scale 1 Req. Design code test system test field use 0.75 1.00 1.50 3.00 10.00 60.00-100.00

9. Reviews & Inspections ... there is no particular reason why your friend and colleague cannot also be your sternest critic. Jerry Weinberg

12. The Players review leader producer recorder reviewer standards bearer (SQA) maintenance oracle user rep

13. Conducting the Review be prepared—evaluate product before the review review the product, not the producer keep your tone mild, ask questions instead of making accusations stick to the review agenda raise issues, don't resolve them avoid discussions of style—stick to technical correctness schedule reviews as project tasks record and report all review results 1. 2. 3. 4. 5. 6. 7. 8.

14. Review Options Matrix trained leader agenda established reviewers prepare in advance producer presents product “ reader” presents product recorder takes notes checklists used to find errors errors categorized as found issues list created team must sign-off on result IPR—informal peer review WT—Walkthrough IN—Inspection RRR—round robin review IPR WT IN RRR no maybe maybe maybe no maybe no no no no yes yes yes yes no yes no no yes yes yes yes yes no yes yes yes yes yes yes yes yes yes no no yes no no yes maybe * *

16. Metrics Derived from Reviews inspection time per page of documentation inspection time per KLOC or FP errors uncovered per reviewer hour errors uncovered per preparation hour errors uncovered per SE task (e.g., design) number of minor errors (e.g., typos) number of errors found during preparation number of major errors (e.g., nonconformance to req.) inspection effort per KLOC or FP

17. Statistical SQA Product & Process measurement ... an understanding of how to improve quality ... Collect information on all defects Find the causes of the defects Move to provide fixes for the process

23. Chapter 27 Change Management Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman

24. The “First Law” No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle. Bersoff, et al, 1980

25. What Are These Changes? data other documents code Test Project Plan changes in technical requirements changes in business requirements changes in user requirements software models

26. The Software Configuration programs documents data The pieces

28. Baselines

29. Software Configuration Objects

31. Repository Content

35. The SCM Process

37. Change Control STOP

38. Change Control Process—I change request from user developer evaluates change report is generated change control authority decides request is queued for action change request is denied user is informed need for change is recognized change control process—II

39. Change Control Process-II assign people to SCIs check-out SCIs make the change review/audit the change establish a “baseline” for testing change control process—III

40. Change Control Process-III perform SQA and testing activities promote SCI for inclusion in next release rebuild appropriate version review/audit the change include all changes in release check-in the changed SCIs

41. Auditing SCIs Change Requests SQA Plan SCM Audit

42. Status Accounting SCIs Change Requests Change Reports ECOs Status Accounting Reporting

47. Content Management

48. Change Management for WebApps-I

49. Change Management for WebApps-II