What the hell is behaviour driven development? Everyone has some sort of behaviour, so it sounds as if everyone must be practising it.
Recently I spotted a new one, domain driven development. I decided to read up on it and realised this is how I had been taught to design code, and how I generally go about doing things. Its got a name now.
Test driven development with silly/vague method names, like it() and should(), often written by people who don't write the code so behaviour can be defined separately from implementation.
It was quite popular in the ruby community a couple of years ago.
Thanks for that but to be honest it just sound like more of the same, but viewed from a different angle.
My understanding of your write up is that that tests may be written without understanding the problem. I mean that is just dumb TDD religious zealots who would do that sort of thing, assuming that test make up for design (and thought process). I also think that the verification process is an inherent part of waterfall model - hence the iterations.
Recently I spotted a new one, domain driven development. I decided to read up on it and realised this is how I had been taught to design code, and how I generally go about doing things. Its got a name now.