Jump to content

Talk:Decomposition (computer science)

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 184.230.134.14 (talk) at 22:19, 28 February 2011 (Criticisms: new section). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Top down approach

Decomposition has very much in common with top-down approach. Can one say it's basically the same? --Abdull 09:55, 21 October 2007 (UTC)[reply]

I think decomposition is (just) an important part of the top down approach. -- Marcel Douwe Dekker (talk) 21:04, 5 November 2008 (UTC)[reply]


Merge proposal

Merging this article with Decomposition (computer science) will best facilitate cooperation between editors in building Wikipedia coverage of these important topics. (sdsds - talk) 21:43, 11 February 2008 (UTC)[reply]

I agree and merged the two articles. -- Marcel Douwe Dekker (talk) 21:07, 5 November 2008 (UTC)[reply]

Copy-paste registration

In this edit text is copy/paste here from the Decomposition paradigm article. -- Mdd (talk) 14:11, 30 October 2009 (UTC)[reply]

Synonymous with "Programming paradigm"?

I find that the concept of decomposition paradigm is closely related if not synonymous with that of Programming paradigm. In the latter, a wider description and a list of programming paradigms is provided, so if you agree a link to the "programming paradigm" page could be added under the section "decomposition paradigm" of this page. —Preceding unsigned comment added by Liberalogica (talkcontribs)

Criticisms

It would be nice if someone (maybe me someday) would describe criticisms of using this for elaborating use cases/architectures. I've read repeatedly to avoid this kind of analysis for software. Here are a couple of references to start:

http://www.ibm.com/developerworks/rational/library/content/RationalEdge/oct03/m_rupse_mc.pdf

http://www.ibm.com/developerworks/forums/thread.jspa?threadID=174565