Content deleted Content added
Jerryobject (talk | contribs) Small WP:COPYEDITs WP:EoS WP:TERSE. WP:LINKs: needless-WP:PIPEs > WP:NOPIPEs, underscores > spaces, adds, update-standardizes. WP:BADEMPHASIS: MOS:QUOTEMARKS, MOS:BOLDs > MOS:NOBOLD WP:ITALICs. Nonlead-word nonproper noun MOS:CAPS > WP:LOWERCASE sentence case. |
Stevebroshar (talk | contribs) it's bigger and fuzzier than a technique (it's a mindset; way of thinking); it's not limited to design _before_ coding as the linked design page says; it applies to all code (not just programs) |
||
Line 1:
{{Short description|Software design technique}}
{{More citations needed|date=June 2022}}
'''Modular programming''' is a [[software
A module [[Interface (computing)|interface]] expresses the elements that are provided and required by the module. The elements defined in the interface are detectable by other modules. The [[implementation]] contains the working code that corresponds to the elements declared in the interface. Modular programming is closely related to [[structured programming]] and [[object-oriented programming]], all having the same goal of facilitating construction of large software programs and systems by [[Decomposition (computer science)|decomposition]] into smaller pieces, and all originating around the 1960s. While the historic use of these terms has been inconsistent, ''modular programming'' now refers to the [[High-level programming language|high-level]] decomposition of the code of a whole program into pieces: ''structured programming'' to the [[Low-level programming language|low-level]] code use of structured [[control flow]], and ''object-oriented programming'' to the ''data'' use of [[Object (computer science)|objects]], a kind of [[data structure]].
| |||