Setting Standards for Computer Program Source Code

• 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

Defect Indicators: (This information is currently under review and available only to Members and Fellows.)

Risks: (This information is currently under review and available only to Members and Fellows.)

Assessment: (This information is currently under review and available only to Members and Fellows.)

Remedy: (This information is currently under review and available only to Members and Fellows.)

References:

• Debugging Effort Estimation using Software Metrics (N. Gorla, A.C. Benander, and B.A. Benander), 1990.

Research Findings:

• Choice of names impacts cost of debugging:
  The effort required to debug a program is minimized when variables had names averaging 10 to 16 characters long.

Copyright © 2005, 2012 by IfSQ, Institute for Software Quality. All Rights Reserved.