Software Quality Matters

• Standards
  • Level-1
  • Level-2
  • Level-3
  • Assessment
  • Downloads
• Code Inspection
  • Why Inspect?
  • When To Inspect
  • What To Look For
  • Research Findings
  • Publications
  • Authors
• Defect Indicators
  • Work In Progress
  • Structured Programming
  • Single Point of Maintenance
  • Defensive Programming
  • Causes for Concern
• About IfSQ...
  • Contact
  • The World and IfSQ
  • Site Map

Findings relevant to IfSQ Standards:

• Better to write cohesive routines
  A study of 450 routines found that 50 percent of highly cohesive programs were fault free, compared to only 18 percent of routines with low cohesion
• Unreferenced variables strong indicator for other errors
  46 percent of routines with no unused variables had no errors compared to only 17 to 29 percent for those with one or more unreferenced variables

IfSQ Defect Indicators:

• SP-4—Module Not Cohesive
  Routines which are cohesive are typically easier to modify, easier to fix and contain less errors than routines wth diverse tasks.,
• DP-4—Unused Variables
  There are unreferenced variables in the code. Unreferenced variables are a strong indicator for other errors.