Revision as of 18:45, 12 May 2013 edit Diggory Hardy (talk \| contribs) 38 edits two new sections ← Previous edit		Revision as of 15:02, 27 June 2013 edit undo Catnaroek (talk \| contribs) 27 edits No edit summary Next edit →
Line 146: This section is wooly (no citations, vague language) and is not balanced by talking about drawbacks (e.g. modifications of a module's interface having to touch on a lot of code, the advantages for testing only being realised with considerable extra work writing tests, and the often large amount of extra code required (over if logic)). Should it be deleted? Complemented by a "drawbacks" section? Renamed "comments"? [[User:Diggory Hardy\|Diggory Hardy]] ([[User talk:Diggory Hardy\|talk]]) 18:45, 12 May 2013 (UTC) == wut == What does "modularity" have to do with "stepwise refinement"? Modularity is all about abstraction and separation of concerns. A user of a module does not need to be concerned with its concrete implementation, so long as the module's structure matches its given signature. Of course, modular programming makes stepwise refinement easier by allowing programmers to handle the evolution of each module's internals independently, but even if this were not the case, stepwise refinement would be feasible.

Talk:Modular programming: Difference between revisions