Path: utzoo!attcan!uunet!cs.utexas.edu!asuvax!ncar!boulder!uswat!gbeary
From: gbeary@uswat.uswest.com ( Greg Beary )
Newsgroups: comp.software-eng
Subject: Re: CASE - The Emperor has no clothes on!
Keywords: CASE rubbish
Message-ID: <8648@uswat.UUCP>
Date: 11 Jun 90 16:29:07 GMT
References: <37538@genrad.UUCP> <3205@goanna.cs.rmit.oz.au> <1990Jun11.120915.320@iesd.auc.dk>
Sender: news@uswat.UUCP
Organization: US WEST Advanced Technologies, CO, USA
Lines: 35

Given the interest in CRC cards I thought I'd chime in. The CRC
approach is more like "storyboarding" than SA/SD. It is a 
vehicle for a group of developers/designers to discuss the
system they're working on.            

You specify the name of a class on the top of the card, its
repsonsibilites (on the left 2/3rds of the card), and its
collaborations (which classes-methods it interacts with) on
the right 1/3. You then use these cards to help decompose 
and explore the system under discussion. We have coupled
this with Ivar Jacobsen`s notion of Use Cases and 
will combine CRC cards to describe a particular Use 
Case. 

I have a paper on our approach to Object-oriented Analysis
and Design (OOAD) that I can share with interested parties.
(Unfortunately, it's been done on Mac with MSWord and 
I don't know how well it could be distributed over the net.)
The approach we use couples Use Cases, CRC cards, Use Case
based Object-Communication Models, and EER diagrams to 
perform OOAD. 

It is written on a "practioner's level" and makes no 
pretention to be a work of academic research.  I'd
be willing to US mail it to interested parties 
providing that they would be willing to critique it.
(Continued Process Improvement).
 
   
 
--
Greg Beary 
US West Advanced Technology  
6200 S. Quebec St.          
Englewood, CO  80111