Xref: utzoo comp.object:2784 comp.lang.c++:12337
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!ucivax!song
From: song@berault.ics.uci.edu (Xiping Song)
Newsgroups: comp.object,comp.lang.c++
Subject: Re: OO Design Methodologies
Message-ID: <27E6AA00.17006@ics.uci.edu>
Date: 20 Mar 91 00:17:04 GMT
References: <1991Mar13.052243.27569@dhw68k.cts.com> <1991Mar15.182940.3421@porthos.cc.bellcore.com>
Reply-To: song@ics.uci.edu (Xiping Song)
Organization: UC Irvine Department of ICS
Lines: 14
Nntp-Posting-Host: berault.ics.uci.edu

In article <1991Mar15.182940.3421@porthos.cc.bellcore.com> haim@taichi.UUCP (24122-Haim Kilov) writes:
>
>Concepts are much more important than methodologies. Only after a concept
>is precisely (i.e., formally) defined, is it possible to discuss the
>methodology (guidelines?) of its use. For generic (application-neutral)

I quite agree this point. I have been using formal/modeling techniques
formalize design methodologies. As a result, a design methodology usually
can be characterized into four types. Concept is one of them. All the
other types--artifacts, representation mechanism and activities
are constructured around concepts to help a methodology more applicable
and effective.

-Song