1 / 19

Applying the Seven Basic Quality Tools in Software Development

Applying the Seven Basic Quality Tools in Software Development. Ishikawa’s Seven Basic Tools for Quality Control. Checklist (or Check Sheet) – to facilitate gathering data and to arrange data so it can be easily used later

rodd
Download Presentation

Applying the Seven Basic Quality Tools in Software Development

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. Applying the Seven Basic Quality Tools in Software Development

  2. Ishikawa’s Seven Basic Tools for Quality Control • Checklist (or Check Sheet) – to facilitate gathering data and to arrange data so it can be easily used later • Pareto Diagram – a frequency chart of bars in descending order; the bars are usually associated with types of problems • Histogram – a graphic representation of frequency counts of a sample or a population • Scatter Diagram – portrays the relationship of two interval variables; can make outliers clear • Run Chart – tracks the performance of the parameter of interest over time; used for trend analysis • Control Chart – an advance form of a run chart for situations in which the process capability can be defined • Cause and Effect Diagram (fishbone diagram) – it shows the relationship between a characteristic and the factors that affect that relationship

  3. Ishikawa’s Seven Basic Tools for Quality Control

  4. Checklists • Summarize the key points of the software development process • More effective than lengthy process documents • Help ensure that all tasks are complete and the important factors or quality characteristics of each task are covered • Examples of checklists are: • Design review checklist • Code inspection checklist • Moderator (for review and inspection) checklist • Pre-code-integration checklist • Entrance and exit criteria for system tests • Product readiness checklist

  5. Pareto Diagram • Identifies areas that cause most of the problems

  6. Pareto Analysis of Software Defects

  7. Pareto Diagram of Defect by Component Problem Index

  8. Histograms

  9. Profile of Customer Satisfaction with a Software Product

  10. Scatter Diagram of Program Complexity and Defect Level

  11. Correlation of Defect Rates of Reused Components Between Two Platforms

  12. Grouping of Reused Components Based on Defect Rate Relationship

  13. Pseudo-Control Chart of Test Defect Rate—First Iteration

  14. Pseudo-Control Chart of Test Defect Rate—Second Iteration

  15. Pseudo-Control Chart of Inspection Effectiveness

  16. Cause-and-Effect Diagram

  17. Cause-and-Effect Diagram of Design Inspection

  18. A Schematic Representation of a Relations Diagram

  19. A Diagram of Complex Relationships Associated with Customer-Critical Situations of a Software Product

More Related