Chipping the web: November 8th

FWIW, some observations from the previous century :-

At Siemens, we found that Fagan Inspections would catch some 75%+ of the requirements errors. Assertions can catch about 30% of the coding errors (the Microsoft study quoted confirms this). BTW, Coding should, but does not always, follow the requirements specification phase

Curiously, there was little use of assertions in design documents until requirements-satisfaction tracking was introduced.

The largest variation factor was the individual doing the programming. Training, techniques and tools helped the worst – of course – much more than the best.

Statistically, in (C and Asm) coding, pointers were the most dangerous constructs.

Since I can’t comment at Just Shelley, I’ll say it here.

I remember when we had to put down our 15 year old cat, Tiffany. I know exactly how Shelley feels and my condolences to her and her roommate.