Statistical Quality Assurance

Statistical quality assurance reflects a growing trend throughout industry to become more quantitative about quality. For software, statistical quality assurance implies the following steps

  1. Information about software defects is collected and categorized
  2. An attempt is made to trace each defect to its underlying cause
  3. Using Pareto principle (80% of the defects can be traced to 20% of all possible causes), isolate the 20% (the "vital few")
  4. Once the vital few causes have been identified, move to correct the problems that have caused the defects.

This relatively simple concept represents an important step toward the creation of an adaptive software engineering process in which changes are made to improve those elements of the process that introduce errors. To illustrate the process, assume that a software development organization collects information on defects for a period of one year. Some errors are uncovered as software is being developed. Other defects are encountered after the software has been released to its end user.

Although hundreds of errors are uncovered all can be tracked to one of the following causes.

  1. Incomplete or erroneous specification (IES)
  2. Misinterpretation of customer communication (MCC)
  3. Intentional deviation from specification (IDS)
  4. Violation of programming standards ( VPS )
  5. Error in data representation (EDR)
  6. Inconsistent module interface (IMI)
  7. Error in design logic (EDL)
  8. Incomplete or erroneous testing (IET)
  9. Inaccurate or incomplete documentation (IID)
  10. Error in programming language translation of design (PLT)
  11. Ambiguous or inconsistent human-computer interface (HCI)
  12. Miscellaneous (MIS)
Related Posts

TEST CASE DESIGN

TEST CASE DESIGN TWO

DESIGN OF TEST CASES PART THREE

TEST CASE DESIGN PART THREE

TEST CASE DESIGN PART FOUR

TEST CASE DESIGN PART FIVE

TEST CASE DESIGN PART SIX

TEST CASE DESIGN PART SEVEN

TEST CASE DESIGN PART EIGHT

TEST CASE DESIGN PART NINE

REVIEWS AND APPROVAL OF TEST CASES

WRITING SOFTWARE TEST CASES PART ONE

WRITING SOFTWARE TEST CASES PART TWO

WRITING SOFTWARE TEST CASES PART THREE

WRITING SOFTWARE TEST CASES PART FOUR

No comments:

Post a Comment