Naked Objects

We have spent the last few months creating a new web development framework, which we have called Scimpi – see http://www.scimpi.org. No doubt your immediate thought will be: surely there are too many web frameworks already, why create another one? Well, unlike a project rationalisation I saw today on SourceForge, it was not because I wanted to brush up on my coding. We wrote it because Naked Objects is currently ignoring the biggest development area going; that of web applications. What Naked Objects currently offers is a unique choice of generic user interfaces Read more »

For those interested in Domain Driven Design, there is an interesting article on InfoQ, by Mats Helander:  Aspects of Domain Model Management.  In the resulting discussion, Dan Haywood has made a couple of useful postings concerning the Naked Objects approach to dealing with the issues raised.

Richard

I have argued for some while that it is possible to divide business systems development projects into two distinct categories: ‘requirements-dominated projects’ and ‘engineering-dominated projects’.  One way to understand which of the two types you are dealing with, is to try to imagine that project failing, and then to write down a list of the 5 most likely reasons why that particular project had failed. Read more »

In response a previous blog entry, Gerald Loeffler raised a question about the potential relationship of Naked Objects to workflow or business process management (BPM).

I have always disliked both of those concepts for three reasons. The first is from technical perspective: they tend to encourage the separation of procedure from data and thus discourage good object-oriented design. The second is from a human perspectice: workflow and BPM systems tend to encourage a management philosophy that disempowers the users. I wrote about this in the original Naked Objects Read more »