Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!hi-csc!slocum From: slocum@hi-csc.UUCP (Brett Slocum) Newsgroups: comp.sys.apollo Subject: Re: DSEE Opinions Message-ID: <43a6dde5.805@hi-csc.UUCP> Date: 5 Jun 89 16:52:00 GMT References: <3860@hacgate.scg.hac.com> Reply-To: slocum@hi-csc.UUCP (Brett Slocum) Organization: csdd Lines: 21 In article <3860@hacgate.scg.hac.com> lori@hacgate.scg.hac.com (Lori Barfield) writes: >I'll be evaluating DSEE for purchase soon. Anyone have any gotchas, >favorite features, comparisons with other products, or other potential >"I told you so"s to share? > >Thanks in advance, > >...lori I would confirm Dave Erstad's comments about DSEE. We used DSEE on a huge SW project involving a team of programmers that changed often, 100-200 K lines of code, and software that was full of kludges, etc. We performed so efficiently, that we had extra contract funds left over for additional functionality. About half the code was new development, and the other half was existing code that needed massive reworking, enhancements, input and output filters, and maintenance. The DSEE performed both of these functions well. -- Brett Slocum | If you keep your head, while everyone or | else loses theirs, you'll be the only or | one needing a haircut.