Fri Nov 21, 2003 2:54 am
I feel as if DDD can be a good driver for TDD. Often I feel that TDD
as presented in it's present form lacks a view of the bigger picture.
I have been unable to find any resources of studies conducted using
TDD as a driver of a big project, linking domain experts with
developers and so on. I was thinking that perhaps TDD could be used as
a mediator between domain experts and developers or as a tool to
developing the domain model. A sample scenario would be a domain
expert sitting beside the developer as they knowledge crunch together
via TDD.
Any thoughts on this subject?
AlexisHui
This sounds like a plausable scenario to me.
I imagine the people who are writing about test-driven design (that is what you meant by TDD, isn't it?) are trying to describe it discretely, keeping it from getting too tangled with all the other practices needed to make a project go, thereby leaving room for projects to combine it with other things to make a working solution for them.
Or maybe they just take the DDD part for granted. ;-)
The title of your email got me thinking. DDD driving TDD --> Domain-driven design driving test-driven design --> domain-driven design driven test-driven design (DDDDTDD). Now that just rolls off the tongue.
EricEvans
DDDDrivingTDD is mentioned on: ThreadView
