Implementing Domain-Driven Design

Reason One: User Interface Convenience

Sometimes user interfaces, as a convenience, allow users to define the common characteristics of many things at once in order to create batches of them. Perhaps it happens frequently that team members want to create several backlog items as a batch. The user interface allows them to fill out all the common properties in one section, and then one by one the few distinguishing properties of each, eliminating repeated gestures. All of the new backlog items are then planned (created) at once:

Click here to view code image

public class ProductBacklogItemService ... {     ...     @Transactional     public void planBatchOfProductBacklogItems(         String aTenantId, String productId,         BacklogItemDescription[] ...