Jump to content

Critical mass (software engineering)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Derek R Bullamore (talk | contribs) at 15:05, 8 September 2013 (Filling in 2 references using Reflinks). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In software engineering, critical mass is a stage in the life cycle when the source code grows too complicated 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.

See also

References

  1. ^ "Sharks, Debts, Critical Mass and other reasons to Sustain Quality". Retrieved 15 February 2010.
  2. ^ "critical mass". Catb.org. Retrieved 2013-09-08.
  3. ^ "What is Object Oriented Programming? (Without the Hype)". Duramecho.com. Retrieved 2013-09-08.


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=572064133"