Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!COMMUNITY-CHEST.MITRE.ORG!howell
From: howell@COMMUNITY-CHEST.MITRE.ORG
Newsgroups: comp.software-eng
Subject: CASE tool "stress tests"?
Message-ID: <8912081454.AA02621@boardwalk.mitre.org>
Date: 8 Dec 89 14:54:00 GMT
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The MITRE Corp., Washington, D.C.
Lines: 16

Any opinions on (or better yet, experiences with :-) the subject of
"scale up factors" for CASE tools?  For example, a tool that works just
fine for 3 people developing a "toy" system may break or suffer dramatic
performance loss or just not provide needed support (e.g. name space
partitioning) when you move to a big system and/or lots of users.  Any
specific stress points, any experiences good or bad with any CASE tools
(especially Teamwork), and any pointers to other work in this area would
all be appreciated a LOT.
Thanks,

+------------------------------------------------------------------------+
| Chuck Howell, M/S Z645     INTERNET: howell@community-chest.mitre.org  |
| The MITRE Corporation           OR   howell@mwunix.mitre.org           |
| 7525 Colshire Drive                                                    |
| McLean VA 22102-3481            FAX: (703) 883-5519                    |
+------------------------------------------------------------------------+