Re: Books / Articles on Embedded SW Architecture

Darin Johnson wrote:

Steve at fivetrees wrote:
A complex system is a collection of simple parts, or or complex parts
consisting of simple elements. It's the interactions between these parts
that confuse us. Which is dumb. We should be designing in terms of
interactions and simple things. Complexity doesn't exist - unless you
don't understand the problem, or the solution offered.

This is the problem. People CAN'T understand the entire problem or
all possible interactions. An individual module may be bug free at
the level of the original requirements and the uses it was expected to
undergo, but the interaction with other modules, reliance on other
modules, changing requirements, and unexpected uses can changes this.

Dealing with just this issue. You are right that people have a problem
understanding all the possible interactions of a complex system as a whole.
However, the thing about decomposing the system until the level of problems
approaches close enough to trivial that we do fully understand the
interactions of that section is a technique worth developing for any
engineer. By fully understanding the simple parts we get to understand the
more complex bits without the undue burden of the underlying simple parts.

Much of this decomposition effort will yield a vision of a natural structure
for the overall system that allows development of the simple parts and
testing of same in the appropriate places in ths structure. You should also
be able to identify good prospects for reuse ase well.

--
********************************************************************
Paul E. Bennett ....................<email://peb@xxxxxxxxxxxxxxxxxx>
Forth based HIDECS Consultancy .....<http://www.amleth.demon.co.uk/>
Mob: +44 (0)7811-639972
Tel: +44 (0)1235-811095
Going Forth Safely ..... EBA. www.electric-boat-association.org.uk..
********************************************************************
.