In many modelling tools the user can define multiple diagrams or views of the entities and associations in a model. This makes it easier to organise and layout complex Domain Models as each diagram can contain a subset of the entities and associations in the Domain Model, allowing you to create different diagrams for different purposes and with different scopes.
There is still one Domain Model (per module) and when you select the properties of any given entity you still see everything in the model. But in the diagram you can add or remove entities and associations which exist in the model.
This generalised approach would also go some way to addressing other request for improved usability of the existing domain model diagram.
I agree, this can be very useful. No need to duplicate module security when there are different views available
Yes, I have also been needing this for a few years. My suggestion is that within a module, the entities may be placed in different domain models - purely for visual reasons to keep the domain organised. The security for a module should apply to all the domain models within it.
I totally support this idea. A model should have different view even in one modul. Each view could have its own diagram focusing only on the relevant elements.
For sure, some kind of better "visual separation" or handling subset would be great.
The model may grow large and complex. But maybe we just need to consider to use more modules?
What can be the best practice in case of large and complex Data Model?