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?
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.
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.