Critical mass (software engineering)
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. The article may be deleted if this message remains in place for seven days, i.e., after 20:59, 5 April 2025 (UTC). Find sources: "Critical mass" software engineering – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Critical mass (software engineering)|concern=Fails [[WP:GNG]]}} ~~~~ |
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
[edit]- High-level programming language
- Programming in the large
- Code refactoring
- Test-driven development
- The Mythical Man-Month
References
[edit]- ^ "Sharks, Debts, Critical Mass and other reasons to Sustain Quality". Archived from the original on 21 January 2010. Retrieved 15 February 2010.
- ^ "critical mass". Catb.org. Retrieved 2013-09-08.
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |