Modular Programming: Difference between revisions

Latest revision as of 21:09, 5 November 2014

Redirect to:

@@ Line 1: / Line 1: @@
-A [[Modular Programming Design]] is a [[Software Design Pattern]] that emphasizes separating the functionality of a program into independent, interchangeable [[software module]]s.
+#REDIRECT [[Modular Programming Design]]
-* <B>Counter-Example(s):</B>
-** a [[Contract-based Software Design]].
-** [[Object Oriented Design]].
-* <B>See:</B> [[Software Design]], [[Separation of Concerns]], [[Maintainability]], [[Interface (Computing)]], [[Implementation]].
-----
-----
-==References==
-=== 2014 ===
-* (Wikipedia, 2014) &rArr; http://en.wikipedia.org/wiki/Modular_programming Retrieved:2014-11-5.
-** '''Modular programming''' is a [[software design]] technique that emphasizes separating the functionality of a program into independent, interchangeable '''modules''', such that each contains everything necessary to execute only one aspect of the desired functionality.  Conceptually, modules represent a [[separation of concerns]], and improve [[maintainability]] by enforcing logical boundaries between components. Modules are typically incorporated into the program through [[interface (computing)|interfaces]].  A module 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.
-----
-[[Category:Concept]]
-__NOTOC__