Software development basics: Decomposition
Posted by Andrey Khavryuchenko on 20 Dec 2006 at 08:37 am | Tagged as: Blog if (function_exists('social_bookmark')) { social_bookmark(); } ?>
This is second article about software development basics.
The first one was “Software development basics: well formed outcome”.
This tool, in contrast to the Well Formed Outcome, is very well known by software developers.
Divide and conquer - what can be simpler?
– How an elephant could be ate?
– Sliced.
Enough said. Will conclude with two wikipedia links: Decomposition and Decomposition paradigm. They distinguish between object-oriented and structural program decomposition, but this really doesn’t matter. The instrument stays the same.
The next article will cover the specifics of implementation of a Well Formed Outcome and Decomposition in the software development.
Update. The other term for the Decomposition is the Separation of Concerns
3 Responses to “Software development basics: Decomposition”
Leave a Reply
You must be logged in to post a comment.








[…] Posted by Administrator on 27 Dec 2006 at 04:56 pm | Tagged as: Blog In this post I’ll show how well formed outcome and decomposition play together in the software development. […]
[…] separation of concerns (see my previous post on decomposition […]
[…] Decomposition also known as the “Separation of Concerns”. […]