Path: utzoo!attcan!uunet!aplcen!samsung!crackers!jjmhome!smds!rh
From: rh@smds.UUCP (Richard Harter)
Newsgroups: comp.software-eng
Subject: Re: Today's Software Standards (was RE:some advice to a sw e
Summary: Designing for incremental implementation
Message-ID: <199@smds.UUCP>
Date: 28 Sep 90 00:17:06 GMT
References: <3259@mindlink.UUCP> <15444@yunexus.YorkU.CA> <233@srchtec.UUCP>
Organization: SMDS Inc., Concord, MA
Lines: 34

In article <233@srchtec.UUCP>, johnb@srchtec.UUCP (John Baldwin) writes:
> David Collier-Brown writes:

> I would have to agree.  In fact, therein lies a good course of action
> to take when a project *must* be completed on time, and it begins to
> show uncorrectable signs of going over.  Its called "trimming."...

A related concept is design for incremental implentation, which is a
very comfortable way to work. *Soapbox mode on*  

I regularly advocate that software development should be done in the
same way the good software maintenance is done.  Design and implement
an irreducible kernel of functionality to produce a working program.
Modify the working program in stages, using incremental refinement
and the standard suite of good change control procedures, so that
each stage is a working program with defined functionality and
testability.

Many developers are uncomfortable with the notion of controlled
change; however my experience is that development which uses
controlled change and which always keeps a working program(s)
in hand is a much comfortable and reliable way to work, and that
the resulting software is produced more quickly and more reliably.

It is not enough to design what a software product should be when
it is completed; one should also plan how one is going to produce
it.  *End soapbox mode*


-- 
Richard Harter, Software Maintenance and Development Systems, Inc.
Net address: jjmhome!smds!rh Phone: 508-369-7398 
US Mail: SMDS Inc., PO Box 555, Concord MA 01742
This sentence no verb.  This sentence short.  This signature done.