>...It occured to me, after this particular event, that what was lacking was a
>few good design principles. I began, at that moment, to think about
>writing a design methodology for messaging systems, particularly Novell
>GroupWise. Over the next few months a colleague and I talked about it,
>experimented, and took careful notes as we visited different companies.
Most events that are begun without proper planning and thinking will
result in less than satisfactory results. While outcomes are sometimes
achieved, IMHO it is at much greater costs than possible with planning
thinking designs frameworks rules etc...
>...It also uses a rather systemic approach,
>where you work from the whole to the parts instead of the parts to the
>whole.
Two observations: first, good object-oriented design will deal with the
important item first, leaving the details of the parts "encapsulated"
within the objects. (Note I said GOOD OO because any idea can be poorly
implemented). Second, the essence of good project management (and problem-
solving) is in the selection of the components in which to decompose the
larger problem. While arbitrary decomposition can work, smart
decomposition will yield superlative results.
FWIW...IMHO....Keith
--Keith Cowan <72212.51@CompuServe.COM>
Learning-org -- An Internet Dialog on Learning Organizations For info: <rkarash@karash.com> -or- <http://world.std.com/~lo/>