1 / 11

Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

Quality Assurance in Construction and Maintenance (Section 13.4 of Maintenance Text; Chapter 20 of Code Complete ). Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture. Today. Team progress report & show a test case Quality Issues – this (no quiz)

waynej
Download Presentation

Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Quality Assurance inConstruction and Maintenance(Section 13.4 of Maintenance Text;Chapter 20 of Code Complete) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture

  2. Today • Team progress report & show a test case • Quality Issues – this (no quiz) • Tonight - Start HW3: Detailed Design. • Tomorrow – • Help on coding and testing - Bring your laptop • Defensive Programming and Debugging – Tori

  3. Review:Goal-Question-Metric Method • One source of information: • http://wwwagse.informatik.uni-kl.de/pubs/repository/basili94b/encyclo.gqm.pdf. • A short example: • Goal: To maximize customer support satisfaction • Question: Are there are consistent problems with the software? • Metric: Number of problem reports generated per day → →

  4. Outline • General Principle of Software Quality • Software Quality Assurance Factors • External Quality Characteristics • Internal Quality Characteristics • Some Software Quality Improvement Techniques

  5. General Principle of Software Quality: Improving quality reduces development costs.

  6. Quality Assurance Factors • External quality characteristics • Attributes that can be determined from use of the software product • Functional • Correctness/Reliability • Accuracy • Other (“Non-Functional”) • Efficiency • Integrity • Usability • Adaptability • Robustness

  7. Quality Assurance Factors • Internal quality characteristics • Attributes determined from examination of the artifacts • Both Development and Maintenance Characteristics • Readability • Understandability • Reusability • Primarily a Development Characteristic • Testability • Primarily Maintenance Characteristics • Flexibility • Portability • Maintainability

  8. McConnell’s caution on these – It depends on the project. You could argue, for example, that Efficiency often conflicts with all the rest of these.

  9. How do these QA factors compare with Bass’s list1? Here are his six “Quality Attributes”: • Performance & capacity • Reliability & availability • Usability • Security • Modifiability, maintainability, & customizability • Testability 1From Software Architecture in Practice (2nd Edition), by Len Bass, et al, the book we use in CSSE 374 and 377.

  10. Some Software Quality Improvement Techniques • Improved Process • Formal and Informal Reviews • Software Quality Metrics • Note that metrics relate to an improved process and reviews!

  11. Exercise • You work for a company that develops commercial desktop software • Your team will be assigned an external quality attribute • Come up with a plan on how to measure and improve that attribute • Repeat for an internal quality attribute • 5 min per attribute!

More Related