Timeline for Rich Domain Models -- how, exactly, does behavior fit in?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 29, 2017 at 16:54 | history | suggested | Fuhrmanator | CC BY-SA 3.0 |
grammar, spelling
|
| Dec 29, 2017 at 15:48 | review | Suggested edits | |||
| S Dec 29, 2017 at 16:54 | |||||
| Oct 7, 2013 at 20:36 | comment | added | Euphoric | @RJB Like I said, AddStatusUpdate is code that is using the domain. So either some kind of webservice or application that uses the domain classes. And like I said, you cannot expect any kind of mockup or pseudocode, because you would need to make whole project of big enough complexity to showcase real advantage of OOP domain model. | |
| Oct 7, 2013 at 17:20 | comment | added | RJB | Good points. Where would the AddStatusUpdate method belong then, in Data or another project in the Infrastrcture? What's an example of any behavior that might theoretically belong in WorkItem? Any psuedo-code or mock-up would be greatly appreciated. My example was actually simplified to be more readable. There are other entities, and for instance the AddStatusUpdate has some extra behavior -- it actually takes a status category name, and if that category doesn't exist, the category is created. | |
| Oct 7, 2013 at 6:21 | history | edited | Euphoric | CC BY-SA 3.0 |
added 333 characters in body
|
| Oct 7, 2013 at 6:13 | history | answered | Euphoric | CC BY-SA 3.0 |