Jump to content

Critical mass (software engineering)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Eog1916 (talk | contribs) at 22:33, 8 October 2011 (ga). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Critical mass in software engineering is a term used to describe a stage in software life cycle: when the source code grows too large to effectively manage without a complete rewrite.[1] At the Critical Mass stage, fixing a bug introduces one or more new bugs.[2]

Tools such as high-level programming languages, object-oriented programming languages [3], and techniques such as programming in the large, code refactoring and test-driven development, exist to make it easier to maintain large, complicated programs.

References

  1. ^ "Sharks, Debts, Critical Mass and other reasons to Sustain Quality". Retrieved 15 February 2010.
  2. ^ http://catb.org/jargon/html/C/critical-mass.html
  3. ^ http://duramecho.com/ComputerInformation/WhatIsObjectOrientedProgramming.html

See also

Stub icon

This software-engineering-related article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Critical_mass_(software_engineering)&oldid=454620140"