Re: Books / Articles on Embedded SW Architecture

"Paul E. Bennett" <peb@xxxxxxxxxxxxxxxxxx> wrote in message
news:e7honh$297$1$8302bc10@xxxxxxxxxxxxxxxxxxx
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.

Absolutely right.

One other thing: the word "interaction" keeps getting mentioned. There
should be none - other than those intended, of course. Possibly *the* most
important part of good design is defining the interfaces between the
"trivial" bits.

Steve
http://www.fivetrees.com
http://www.sfdesign.co.uk


.

Relevant Pages

  • Re: Books / Articles on Embedded SW Architecture
    ... It's the interactions between these parts ... We should be designing in terms of ... Engineers are stretched thin and end up having more modules to ... Hardware has errors, not all of which are documented. ...
    (comp.arch.embedded)
  • Re: Books / Articles on Embedded SW Architecture
    ... It's the interactions between these ... We should be designing in terms ... The interfaces between the components is of absolute importance. ... customer that would require redesigning the high level architecture. ...
    (comp.arch.embedded)
  • Re: Books / Articles on Embedded SW Architecture
    ... It's the interactions between these ... We should be designing in terms ... The interfaces between the components is of absolute importance. ... I thank you for adding that reminder Steve. ...
    (comp.arch.embedded)
  • Re: Books / Articles on Embedded SW Architecture
    ... It's the interactions between these parts ... interactions of that section is a technique worth developing for any ... By fully understanding the simple parts we get to understand the ... Much of this decomposition effort will yield a vision of a natural structure ...
    (comp.arch.embedded)