Should an image be able to resize itself in OOP?
I’m writing an app that will have an Image entity, and I’m already having trouble deciding whose responsibility each task should be.
Resources for popular domain models [closed]
Closed 10 years ago.
Accessing Repositories from Domain
Say we have a task logging system, when a task is logged, the user specifies a category and the task defaults to a status of ‘Outstanding’. Assume in this instance that Category and Status have to be implemented as entities. Normally I would do this:
Should a domain expert make class diagrams?
The domain expert in our team uses UML class diagrams to model the domain model.
Can the following Domain Entity contain logic for creating/deleting other entities?
a) As far as I understand it, in most cases Domain Model DM doesn’t contain code for creating/deleting domain entities, but instead it is the job of layers ( ie service layer or UI layer ) on top of DM to create/delete domain entities?
In a team practicing Domain Driven Design, should the whole team participate in Stakeholder meetings?
In my experience, a Software Development Team that comprises:
How to choose between using a Domain Event, or letting the application layer orchestrate everything
I’m setting my first steps into domain driven design, bought the blue book and all, and I find myself seeing three ways to implement a certain solution. For the record: I’m not using CQRS or Event Sourcing.
Recovering an anemic domain model into a multitier architecture
I have spent the past several days learning about domain driven design and attempting to apply it to a current project. I decomposed the problem domain into the canonical logical components: domain, infrastrucutre, and presentation. Having completed a first pass, I stepped back and realized that the architecture I created resulted in virtually all of the business logic being contained in the application services, which is the tell-tale sign of the anemic domain model code smell. After further consideration, domain driven design may not be the correct fit for my application, and even if it is, given the small number of business logic rules in my application, the layering overhead may not be worth it. Since I have only written UML and psuedo code I haven’t invested too much time and effort, but I would like to leverage what I can if it’s possible.
How to manage long running background threads and report progress with DDD
Title says most of it. I have found surprising little information about this. I have a long running operation of which the user wants to see the progress (as in, item x of y processed). I also need to be able to pause and stop the operation. (Stopping doesn’t rollback the items already processed.)
DDD Model Design and Repository Persistence Performance Considerations
So I have been reading about DDD for some time and trying to figure out the best approach on several issues.