Jump to content

Critical mass (software engineering): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
No edit summary
Yobot (talk | contribs)
Bots
4,733,870 edits
m clean up, References after punctuation per WP:REFPUNC and WP:CITEFOOT using AWB (8792)
Line 1: Line 1:
In [[software engineering]], '''critical mass''' is a stage in the [[Product lifecycle (engineering)|life cycle]] when the [[source code]] grows too complicated to effectively manage without a complete rewrite.<ref>{{cite web|url=http://www.testingreflections.com/node/view/8429|title=Sharks, Debts, Critical Mass and other reasons to Sustain Quality|accessdate=15 February 2010}}</ref> At the critical mass stage, fixing a [[Software bug|bug]] introduces one or more new bugs.<ref name="catb.org">http://catb.org/jargon/html/C/critical-mass.html</ref>
In [[software engineering]], '''critical mass''' is a stage in the [[Product lifecycle (engineering)|life cycle]] when the [[source code]] grows too complicated to effectively manage without a complete rewrite.<ref>{{cite web|url=http://www.testingreflections.com/node/view/8429|title=Sharks, Debts, Critical Mass and other reasons to Sustain Quality|accessdate=15 February 2010}}</ref> At the critical mass stage, fixing a [[Software bug|bug]] introduces one or more new bugs.<ref name="catb.org">http://catb.org/jargon/html/C/critical-mass.html</ref>


Tools such as [[high-level programming language]]s, [[object-oriented programming language]]s <ref>http://duramecho.com/ComputerInformation/WhatIsObjectOrientedProgramming.html</ref>, and techniques such as [[programming in the large]], [[code refactoring]] and [[test-driven development]], exist to make it easier to maintain large, complicated programs.
Tools such as [[high-level programming language]]s, [[object-oriented programming language]]s,<ref>http://duramecho.com/ComputerInformation/WhatIsObjectOrientedProgramming.html</ref> 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==
==References==
Line 12: Line 12:
* [[Test-driven development]]
* [[Test-driven development]]
* [[The Mythical Man-Month]]
* [[The Mythical Man-Month]]

⚫
{{software-eng-stub}}


[[Category:Software project management]]
[[Category:Software project management]]



⚫
[[fi:Kriittinen massa (ohjelmistotuotanto)]]
⚫
{{software-eng-stub}}

[[ga:Mais chriticiúil (innealtóireacht bogearraí)]]
[[ga:Mais chriticiúil (innealtóireacht bogearraí)]]
⚫
[[fi:Kriittinen massa (ohjelmistotuotanto)]]

Revision as of 02:05, 11 December 2012

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.

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