Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!hacgate!ashtate!atsun!dwiggins From: dwiggins@atsun.a-t.com (Don Dwiggins) Newsgroups: comp.software-eng Subject: Re: Today's Software Standards (was RE:some advice to a sw e Message-ID: Date: 4 Oct 90 19:54:12 GMT References: <15444@yunexus.YorkU.CA> <233@srchtec.UUCP> <199@smds.UUCP> <244@srchtec.UUCP> Sender: news@ashtate.UUCP Organization: Ashton-Tate, Inc. Lines: 16 In-reply-to: johnb@srchtec.UUCP's message of 28 Sep 90 17:14:18 GMT In article <244@srchtec.UUCP> johnb@srchtec.UUCP (John Baldwin) writes: IMHO, the intelligent software engineer (AND his intelligent managers!) will realise that ***the system is GOING to change***, and will begin the project with this a-priori assumption. We might as well manage the alteration process at the beginning. This is one of the things covered by risk management, which is becoming recognized as an important part of software project management, especially for large and/or tightly constrained projects (see the IEEE tutorial by Boehm or the McGraw Hill book by Charette). -- Don Dwiggins "If you think training is expensive, Ashton-Tate, Inc. try ignorance" dwiggins@ashtate.a-t.com -- Derek Bok, Harvard U.