Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!sdcsvax!ucbvax!hi-csc.UUCP!slocum
From: slocum@hi-csc.UUCP.UUCP
Newsgroups: comp.sys.apollo
Subject: Re: DSEE
Message-ID: <8706111950.AA02795@hi-csc.uucp>
Date: Thu, 11-Jun-87 15:50:13 EDT
Article-I.D.: hi-csc.8706111950.AA02795
Posted: Thu Jun 11 15:50:13 1987
Date-Received: Sat, 13-Jun-87 11:13:40 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 37

I will second Dave Erstad's comments regarding the DSEE (I still
insist on using the letters and not "dizzy").  

I am a DSEE administrator and user for about 2 years on a huge SW
project which up to 16 designers all working on the same tool, a
digital synthesis package.  This toll is now about 50-75K lines of
code.  Our contract will be on time and within budget, if not under
budget, largely because of our extensive use of DSEE.

One 15K line piece (about a 1/2 meg of sourcecode) was specified,
designed, implemented, and tested in about 5 months, with more
functionality than originally planned, and within budget.  The team
consisted of about 10 total individuals, 2-5 at any one time.  Some of
these people worked as little as 3 weeks, and most people had no
Apollo experience, and only one (myself) had any DSEE experience.  I
heard nary a whimper, and in fact, many compliments.  As Mr. Erstad
said, an average of about 2-3 days to learn how to use the Apollo and
DSEE was normal.

Tim Giebelhaus mentioned about they guy who refused to use DSEE.  I
know the person in question (Mr. Giebelhaus works at my office).  I
was given the thankless job of helping this poor sot integrate his
version of the source with the current version, and let me tell you
that it was awful.  We not only lost a month, but that was a month of
his time, my time, and a grad student's time.  And this was the second
time it happened.  

Mr. Giebelhaus writes:
> For a small project DSEE is not very useful; it is more work than
> its worth.

This is is true if you define 'small' as one programmer and less than
about 1000-2000 lines of code.  Any more than that in either dept. and
DSEE is a BIG help.


--Brett Slocum, Honeywell Corporate Systems Development Division