Re: C++ fluency
On May 8, 9:51 pm, "Phlip" <phlip2...@gmail.com> wrote:
http://collaboration.csc.ncsu.edu/laurie/Papers/TDDpaperv8.pdf
The interesting phrase I noticed was "a small java program".
A scientific study of large projects would cost way too much to run.
I'm really not convinced that TDD (and XP, especially) scale well.
The bigger the project, the more you should apply XP,
especially. Look up how the Space Shuttle's software is
written. They use pair programming and their version of TDD.
That's not what the people who actually work there say. For
starters, of course, most of the software on the Space Shuttle
was written before anyone had heard of TDD.
For those interested: see the article "NASA's Shuttle Software:
Lives Depend on Its Quality", in
http://lifelong.engr.utexas.edu/sqi/sqi_newsletter/winter97.pdf.
For example: "Testing obviously plays a central role in
producing a quality product, but since we know that exhaustive
testing of any nontrivial software system is impossible, we must
put into place `a defined, controlled, repeatable, predictable
process that will result in a product of known quality,'"
They integrate continuously, and run a humongous test
batch.
Studies of very large projects have shown that the more
carefully they collect all their requirements up front, the
more likely they are to fail.
I suspect that this is just another invention on your part, but
it really doesn't matter, since it's just a strawman anyway.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34