Re: Good Design Strategies <Was comments on comments>

[snidely@inteloa.intel.com (David P. Schneider)]

Another point to note is that for large (complex) projects, identifying the
subject of ADTs (e.g., Object-oriented design) may require an analysis step
using traditional requirements-oriented techniques, such as  data-flow  di-
agrams.   The associated data dictionary would then be used to identify the
objects or components, and the transform bubbles would be used to  identify
the required operations on those objects.

Note that traditional software engineering (Pressman, for instance)  breaks
the pre-release part of a project into *three* phases: analysis first, then
design, and finally implementation.   Analysis  tries  to  identify  system
characteristics   and   requirements   without   going   into   design-  or
implementation-level descriptions (which would  prematurely  constrain  op-
tions); design translates the output of analysis into implementable specif-
ications, and implementation puts code behind them thar words.   Note  that
the differentiation is a matter of degree more than type.

I'm gearing up for a term paper on the subject  of  object-oriented  design
and software reuse in complex projects, and if you can provide me with some
additional references in the trade journals, or have  had  experience  with
using ADT/object-oriented design on large projects, your mail would be wel-
come.

                                                David P. Schneider
                                                     BiiN (tm)
                                                  Wednesday, 3.8