Critical mass (software engineering)
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 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
- High-level programming language
- Programming in the large
- Code refactoring
- Test-driven development
- The Mythical Man-Month
References
- ↑ "Sharks, Debts, Critical Mass and other reasons to Sustain Quality". Archived from the original on 21 January 2010. Retrieved 15 February 2010. Unknown parameter
|url-status=ignored (help) - ↑ "critical mass". Catb.org. Retrieved 2013-09-08.
 | This software-engineering-related article is a stub. You can help EverybodyWiki by expanding it. |
This article "Critical mass (software engineering)" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Critical mass (software engineering). Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
