ChapterFour Release

In ChapterFour the team has made several important changes to the project structure and the UI. The initial frontend approach, let's call it web 1.0 UI, was completely rewritten. The new approach is based on Backbone.js, uses a RESTful API to interact with the backend and provides a fast, lightweight and task based UI. But that's not all. The original Application module is now splitted into 3 modules:

• The new Application module contains the REST API and the ZF2 MVC stack
• The Domain has moved to the CargoBackend module
• The original RoutingService has moved to the GraphTraversalService and is no longer in scope of the project

A new DTO isolation layer shields the domain layer from concerns about such things as the user interface and remoting.

With this change the team has begun to implement a hexagonal architecture where the UI is just one of several other clients using the cargo domain.

Changelog

ChapterThree Release

ChapterThree is about Model-Driven Design.
Chanelog

ChapterTwo Relaese

In Chapter Two we learn the importance of the Ubiquitous Language. With it's help the team works out a Cargo Router and redefines the use cases for the Shipping Application.
Changelog

Chapter One implementation

Chapter One release contains the first draft of the Cargo DDD model. It contains the Entities Cargo and Voyage and also an Application BookingService that works with an overbooking policy to allow the booking of a Cargo even when the Voyage has not enough free capacity.