In my book I focus on the open source Java version of Naked Objects, but (as I briefly mention) there is also a commercial version of Naked Objects that runs on .NET. This is developed by Richard Pawson’s company, Richard being the originator of the Naked Objects pattern; (Richard and I continue to work [...]
|
||||||
Domain-driven design (DDD) focuses on what matters in enterprise applications: the core business domain. And Naked Objects lets you build DDD applications just by writing the core domain classes, the rest of the application is taken care of for you. This blog supplements and expands on my book, Domain Driven Design using Naked Objects, describing how you can rapidly develop and test domain applications using Naked Objects. |
In this screencast we’re going to continue looking at domain object properties, building on the first post in this series. We’ve already seen how Naked objects allows us to write supporting validateXxx() and choicesXxx() methods which we can use to limit the set of values that can be taken for a property, (eg “visa”, “mastercard” or [...] In the first post in this series, we saw how to add a new property to a domain object and specify some choices. One of the aims of Naked Objects is to ensure that our domain objects are behaviourally-complete: that they encapsulate a coherent set of responsibilities. Not anaemic domain models, but OO like your [...] Naked Objects excels as a rapid prototyping environment. However, many rapid prototyping environments focus on user interface details, and gloss over the underlying domain concepts that sit underneath. With Naked Objects though (because the UI is generated automatically from the domain model), when we do rapid development prototyping we are prototyping the domain [...] |
 |
||||
|
Copyright © 2010 Domain Driven Design using Naked Objects - All Rights Reserved |
||||||