What is this feature about?
The domain model is quite well for generating code on backend, ie. some sort of HTTP API. But for the Frontend/UI... it's not the best model.
OOUX instead is a model used by designers and is more suited to build UIs.
Here is the best article to it: https://alistapart.com/article/object-oriented-ux/
Since it is similar to a class-diagram or ERM, this is were communication between designers and engineers speeds up and both models connect.
It also connects very well to the given domain model here:
- Object -> Read Model / Aggregate
- Action -> Command
- Metadata/Content -> Properties (but with more semantics)
- Relationships -> Object
I think implementation is straight forward and then a skill to use the OOUX part to generate a UI.
What is this feature about?
The domain model is quite well for generating code on backend, ie. some sort of HTTP API. But for the Frontend/UI... it's not the best model.
OOUX instead is a model used by designers and is more suited to build UIs.
Here is the best article to it: https://alistapart.com/article/object-oriented-ux/
Since it is similar to a class-diagram or ERM, this is were communication between designers and engineers speeds up and both models connect.
It also connects very well to the given domain model here:
I think implementation is straight forward and then a skill to use the OOUX part to generate a UI.