Revision as of 13:47, 28 September 2021 edit Pachu Kannan (talk \| contribs) Extended confirmed users, Rollbackers 33,983 edits Undid revision 1046993678 by 62.7.93.194 (talk) unexplained content removal. Tags: Undo Mobile edit Mobile web edit Advanced mobile edit ← Previous edit		Revision as of 08:30, 4 October 2021 edit undo 2a01:4c8:1400:693f:cbc7:56c4:7f7b:1a71 (talk) →Key aspects: Removed what seems to be opinion (use of modules refutes the rule of thumb described in The Mythical Man Month) Tags: Mobile edit Mobile app edit Android app edit Next edit →
Line 28: These independent functions are commonly classified as either program control functions or specific task functions. Program control functions are designed to work for one program. Specific task functions are closely prepared to be applicable for various programs. This makes modular designed systems, if built correctly, far more reusable than a traditional monolithic design, since all (or many) of these modules may then be reused (without change) in other projects. This also facilitates the "breaking down" of projects into several smaller projects. Theoretically, a modularized software project will be more easily assembled by large teams, since no team members are creating the whole system, or even need to know about the system as a whole. They can focus just on the assigned smaller task (this, it is claimed{{By whom\|date=July 2021}}, counters the key assumption of [[The Mythical Man Month]], making it actually possible to add more developers to a late software project without making it later still). ==History==

Modular programming: Difference between revisions