
I recently received and re-read Dan Haywood's excellent "
Domain-Driven Design Using Naked Objects" (I'd read a review copy some months ago). It's definitely worth the effort and I'm hoping to get some of the exercises done too as this means I can get up to speed with where the Naked Objects framework currently is these days.One of the first pieces of prototyping we did with xProcess (back in 2003) was to create a domain model (using TogetherSoft's "Together") and then connect it to Naked Objects so we could dynamically interact with those early models of Project, Task and Person. Naked Object effectively animates a domain model so you have an instant user interface to manipulate the domain objects. I believe the approach helped us then and I would certainly recommend projects consider doing the same - particularly in early stages of a project - as getting good domain models early pays off many times over at the end of the day.
Comments
I remember the conversation well and I'm delighted that it was so fruitful - was it at BeJUG in Antwerp?. I am still interested in Naked Object because I am sure that frameworks like this are such a natural support for development teams. Surely that they will become ubiquitous. I think it's obvious that a good domain model contains more than enough information to generate full applications - albeit with standard user access and persistence mechanisms. It's probable that user interfaces will get specialised to gain competitive advantage, but in the early stages of projects/products there really is no justification for this extra expense.
Keep pounding the message. It'll get through eventually!