As an advanced user of domain-driven modeling you may have experienced that you find yourself soon dealing with a huge set of domain-specific elements: A description of a complex domain can need hundreds of elements. Having all these elements as a flat list is no longer convenient. Fortunately, actifsource lets you group your elements -- which are simply called Resources in actifsource -- into so-called Packages (similar to Java packages).
Packages enable a simple hierarchical structuring and are currently the all-embracing grouping element:
- A Package can contain Resources
- A Package can contain nested Packages
... and need to be grouped domain-specifically!
So, after some discussion, we came to the following idea to solve the problems mentioned above: We need to have a way to define grouping elements on the domain meta-level! All the grouping concepts have something in common:
- A grouping element can contain nested grouping elements of some grouping types
- A grouping element can define dependencies to other grouping elements
So, the current concept of Packages containing Classes would be only a realization of the more general grouping concept!