From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 109fba,7f8fc37d854731d6
X-Google-Attributes: gid109fba,public
X-Google-Thread: 103376,7f8fc37d854731d6
X-Google-Attributes: gid103376,public
X-Google-Thread: 10461e,7f8fc37d854731d6
X-Google-Attributes: gid10461e,public
X-Google-Thread: 1108a1,7f8fc37d854731d6
X-Google-Attributes: gid1108a1,public
X-Google-Thread: 114809,7f8fc37d854731d6
X-Google-Attributes: gid114809,public
From: ell@access2.digex.net (Ell)
Subject: Re: Interesting but sensitive topic to discuss (HELP: - OOP and CASE
 tools)
Date: 1996/11/13
Message-ID: <56cmum$9j5@news4.digex.net>#1/1
X-Deja-AN: 196223134
references: <32813322.41C6@kyebek3.kjist.ac.kr>
 <55pqr5$136a@grimsel.zurich.ibm.com> <328109CD.6685@concentric.net>
 <55v177$ufo@grimsel.zurich.ibm.com> <55vfg3$513@news3.digex.net>
 <32838D59.6462@concentric.net>
followup-to: 
 comp.object,comp.lang.c++,comp.lang.ada,comp.lang.smalltalk,comp.ai
organization: The Universe
newsgroups: 
 comp.object,comp.lang.c++,comp.lang.ada,comp.lang.smalltalk,comp.ai
Date: 1996-11-13T00:00:00+00:00
List-Id: <comp.lang.ada>


Alan Lovejoy (alovejoy@concentric.net) wrote:

: If the same class hierarchy can be used to create many different
: programs
: (without defining any new classes or methods), then it should be obvious
: that the class inheritance hierarchy and program architecture and design
: are not at all the same things! 

Earlier I should have said that using the term "design" in a non-standard
way can lead to incorrect thinking about related issues.

I think you need to distinguish analysis from arcitecture from design. 
>From what I gather in my experience in and readings on the development
phases, analysis examines requirements and traditionally in sw engineering
posits a logical solution.  Architecture takes that and creates an overall
physical design for implementation based in large part on language. Design
is mostly considered to be subsystem and category/object creation - though
architecture is the first part of it. 

I agree with you however that polymorphism/subtstitution in analysis
should be portrayed as a kind of non-specific (indefinite :-)
generalization rather than inheritance.  And that inheritance if
applicable should only first show up in architectural blueprints.

Elliott