Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cimshop!davidm From: cimshop!davidm@uunet.UU.NET (David S. Masterson) Newsgroups: comp.software-eng Subject: Re: CASE, the Little Red Hen, and Stone Soup Message-ID: Date: 27 Aug 90 07:06:37 GMT References: <28596@athertn.Atherton.COM> <28966@athertn.Atherton.COM> Sender: davidm@cimshop.UUCP Distribution: comp Organization: Consilium Inc., Mountain View, California. Lines: 21 In-reply-to: jgautier@deimos.ads.com's message of 23 Aug 90 18:05:27 GMT In article jgautier@deimos.ads.com (Jorge Gautier) writes: I want to see the design of a useful CASE environment as the "raison d'etre" for a tool integration standard. I have not seen such a design (yet?), so I am not ready to buy tool integration just because it *could* lead to a useful CASE environment. I see the value that tool integration standards could have for a developing industry. But as a client, I am interested in the useful CASE environment, not in how it's implemented. As a computer scientist, I believe there may be other paths leading to it. Okay, what is a "useful" CASE environment? (You knew that was coming, didn't you ;-) Before designing such an environment, the requirements for such an environment need to be established. Anyone got an OORA CASE tool handy? ;-) -- ==================================================================== David Masterson Consilium, Inc. uunet!cimshop!davidm Mtn. View, CA 94043 ==================================================================== "If someone thinks they know what I said, then I didn't say it!"