Python for large projects

[Alan Gauld]

On 25 Mar 2004 12:21:36 +0100, Matthias <no at spam.pls> wrote:

> Jacek Generowicz <jacek.generowicz at cern.ch> writes:
> 
> > "After", is far too late, in my opinion. It's a bit like suggesting to
> > a static-typing-for-safety fan, that he should only run his program
> > through the compiler _after_ he has finished developing. 
> 
> I think this method was advertised as the "cleanroom approach".
> Google finds some references.

The clean room approach was slihtly different although heading in
that direction. It relied on rigorous review, inspection and
testing at every stage of the process. (sound familiar?)

It was popular in the early/mid eighties and here are a few
references:

Wicked problems, Righteous Solutions; P DeGrace & L Hulet Stahl
- many methodolofgies including a section on clean room.

Cleanroom approach to REliable Software Devt; Dyer & MIlls
Proceedings Validation Methods Research for Fault Tolerant
Avionics....; Research Triangele Institiute, 1981

Cleanroom Software Devt, An Emopirical Investigation; 
Selby, Basili, Baker, 1987
IEEE Transactions on Software Engineering, 
VolSE-13,#9, Sept 1987

HTH,

Alan G.

PS. Keeping programmers away from compilers is not that old a
prctice, I was working on a VAX project in 1989 that only allowed
us one compile each per day, with a full compile overnight (which
took 6 hours)

Author of the Learn to Program website
http://www.freenetpages.co.uk/hp/alan.gauld