IfSQ

IfSQ, Institute for Software Quality

Overview of this website, listed by section by section

This website contains the following sections and pages:

Research into the Maintenance of Software

Code Inspection Pays For Itself Inspection is up to 20 times more efficient than testing Inspection is 80% faster than testing Debugging represents half of development costs	Code Inspection Powers Up Testing Strategies Code inspection is four times more effective than testing Inspection catches 70% of defects Design defects take 6 times longer to find using testing Inspection catches 60% more errors than testing
Code Inspection Boosts Productivity Developers find the majority of defects when preparing for code reviews An hour of inspection saves 100 hours of work 90% of development work occurs after initial release Developers who inspect code are at least 20% more productive	Code Inspection Makes Testing Cheaper 85% of errors can be fixed in a few hours Catching defects during testing is 10 times more expensive Fixing defects early cuts costs in half
Code Inspection Increases Agility Inspected software costs 90% less to maintain An hour of inspection saves 30 hours of maintenance Quality processes reduce errors without increasing costs	Inspect during development 25% of requirements change during development 70% of rework caused by changing requirements Inspections cut rework by half
Inspect before testing Defect removal is the most expensive part of software process Inspection is nearly twice as fast Inspection 4 to 7 times faster than testing	Entry Level Compliance Best size for routines is 100-150 lines Better not to exceed 143 lines in a routine Long routines are more error prone Few understand more than 3 levels of nesting More than 4 levels of nesting too difficult Don't Repeat Yourself (DRY)
Professional Software Development Better to limit control flow complexity Competent programmers know their limits Repetitive code indicates poor design 39% of errors caused by interfacing Missing "else" for 50-80% of plain "if"s	Industry Best Practice Better to write cohesive routines Coupling-to-Cohesion ratio inversely correlated to errors High cohesion correlated to low fix cost Choice of names impacts cost of debugging Unreferenced variables strong indicator for other errors Information-Hiding makes large programs 4 times easier to modify

Papers, Presentations and Books

A An Analysis of Some Commercial PL/1 Programs Analyzing Error-Prone System Structure Applied Software Measurement: Assuring Productivity and Quality Software Assessments, Benchmarks, and Best Practices		B - Col Balancing Agility and Discipline: A Guide for the Perplexed Calculating the Return on Investment from More Effective Requirements Management Code Complete Collecting and Categorizing Software Error Data in an Industrial Environment
Com - Def Comparing The Effectiveness of Software Testing Strategies A Complexity Measure Debugging Effort Estimation using Software Metrics Software Defect Prevention Using McCabe's Complexity Metric Software Defect Removal Efficiency		Des - Ec Design and Code Inspections to Reduce Errors in Program Development Document Inspection as an Agent of Change An Economic Release Decision Model: Insights into Software Project Management
Em - Es An Empirical Study of Modularity on Program Modifiability An Empirical Study of Software Design Practices Software Engineering Economics Software Errors and Complexity: An Empirical Investigation Estimating Software Costs		Ev - Ex Evaluating Software Development by Error Analysis: The Data from the Architecture Research Facility Evaluating Software Engineering Technologies Experience with Inspection in Ultralarge-Scale Developments An Experimental Investigation of Software Metrics and Their Relationship to Software Development Effort
F - Id What We Have Learned About Fighting Defects Hughes Aircraft's Widespread Deployment of a Continuously Improving Software Process The Humble Programmer Identifying Error-Prone Software - An Empirical Study		Im - In Improving Software Productivity Software Inspection Software Inspection: An Industry Best Practice Inspections - Some Surprising Findings Software Inspections: An Effective Verification Process
Ma - Pe Managing the Software Process Managing the Structured Techniques: Strategies for Software Development in the 1990's Some Pascal Style Guidelines Peer Reviews in Software: A Practical Guide		Pr - Proc Practical Software Maintenance Practical Software Metrics for Project Management and Process Improvement The Pragmatic Programmer Software Process Improvement at Raytheon
Prod - Rel Software Productivity Professional Software Development Professional Software, vol. 2, Programming Practice Programming Productivity Software Reliability		Req - Z Software Requirements They Write the Right Stuff Why You Should Use Routines, Routinely Swords and Plowshares: The Rework Cycle of Defense and Commercial Software Development

Authors, Contributors and Researchers

A - C Ackerman, A. Frank Agresti, William W. Basili, Victor R. Benander, A.C. Benander, B.A. Boehm, Barry W. Brykczynski, Bill Buchwald, Lynne S. Card, David N. Chomsky, Noam Church, Victor E. Cooper, Kenneth G.	D - G Dijkstra, Edsger Elshoff, James L. Fagan, Michael E. Fishman, Charles Gilb, Tom Glass, Robert L. Gorla, N. Grady, Robert B. Graham, Dorothy	H - L Haley, Thomas J. Holland, D. Humphrey, Watts S. Hunt, Andrew Jones, Capers Korson, Timothy D. Ledgard, Henry F. Leffingwell, Dean Lewski, Frank H. Lind, Randy K.
M - O Marca, David McCabe, Tom McConnell, Steve McGarry, F.E. Meeson, Reginald Mills, Harlan D. Mullen, Thomas W. Myers, Glenford J. Ostrand, Thomas J.	P - T Page, G.T. Paulsen, L.R. Perricone, B.T. Pigoski, Thomas M. Russell, Glen W. Selby, Richard W. Shen, Vincent Y. Shull, Forrest Slack, Tom Van Tauer, John Thebaut, S.M. Thomas, David Turner, Richard	V - Z Vairavan, Kenneth G. Vaishnavi, Vijay K. Ward, William T. Weinberg, Gerald M. Weiss, David M. Weyuker, Elaine J. Wheeler, David Wiegers, Karl Willis, Ron R. Yourdon, Edward Yu, Tze-jie

Findings from Research

Obstacles to Software Maintenance

The IfSQ Standards

IfSQ, Institute for Software Quality

How to Contact IfSQ
The World and IfSQ
Overview of this website, listed by section by section