Implementing Domain-Driven Design

Modeling Events

Let’s take a requirement from the Agile Project Management Context. The domain experts indicated the need for an Event in this way (italics added for emphasis):

Allow each backlog item to be committed to a sprint. It may be committed only if it is already scheduled for release. If it is already committed to a different sprint, it must be uncommitted first. When the backlog item is committed, notify the sprint and other interested parties.

When modeling Events, name them and their properties according to the Ubiquitous Language in the Bounded Context where they originate. If an Event is the result of executing a command operation ...