From “Domain Modeling or Data Modeling“:
Users do not care “objects”. They care UI, and the fact that the data on the UI are saved in databases. So, by definition, UI and the key data are the “business language”; objects are not.
I have seen the value of domain driven design, but my style lends itself mostly to UI modeling using mockups. This is probably a result of my upbringing: I’m not a trained computer programmer!
For me, user interface mockups are the most effective way to communicate concepts and start building an application. Normal business people (that is, everyone except computer programmers!) respond to a visual and interactive UI in a different way than an abstract object/data/domain model. UI mockups can be easily understood by any user, which improves feedback.
Popularity: 2% [?]
Related posts:
- Unit testing an Activerecord domain model with NUnit
- Installing Systems Center Essentials fails: “The specified domain does not exist or cannot be contacted.”
- Running a Windows NT Domain / Active Directory Audit
- Operator overloading your domain model with interfaces and base classes
- Cool feature: Balsamiq’s auto ‘lorem ipsum’ generator
