Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!think!ames!ucbcad!ucbvax!HI-MULTICS.ARPA!Erstad
From: Erstad@HI-MULTICS.ARPA
Newsgroups: comp.sys.apollo
Subject: Re: AEGIS/UN*X
Message-ID: <870609130948.836911@HI-MULTICS.ARPA>
Date: Tue, 9-Jun-87 09:09:00 EDT
Article-I.D.: HI-MULTI.870609130948.836911
Posted: Tue Jun  9 09:09:00 1987
Date-Received: Fri, 12-Jun-87 03:49:37 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 26


With regard to Robert Reed's comments on "dizzy" (DSEE, or Domain
Software Engineering Environment).  As a relatively experienced DSEE
user (1.5 years of intense use) I would contend that DSEE does indeed
deliver what it promises.  The primary complaint I would have is that
the documentation is not up to snuff, although it did improve
significantly with 9.0.  On the other hand, it provides powerful, yet
easy to use, procedures for code control, history management, and
parallel/semi-interelated development efforts.

We had one summer student in last year from Stanford (a junior) and had
here dizzying away after about 3 days total training on the Apollos and
DSEE combined.  We've had half a dozen people working in the same
general areas; frequently even had two people working on the same tool
at the same time for different purposes; DSEE provides the ability to
control interactions between these people to allow maximum sharing of
commonality while preventing destructive interference.  It also allows
alternate "branches" of development to proceed, so we may have an
obsoleted version of a tool which we continue to bugfix, while
developing the next generation of that tool.

In short, DSEE doesn't do a lot that couldn't be done manually (except
for enforcing proper revision control/history), but I sure as heck
wouldn't want to do it.

Dave Erstad, Honeywell Solid State Electronics Division