3.4. Aspects and Join Points
The principle of domain autonomy allows us to build models of domains that are quite separate from one another. From the point of view of the user interface domain, the meaning of what is selected from a menu is both irrelevant and unknown, and from the point of view of the application the fact that a catalog item was selected from a menu list is irrelevant.
At construction time, when we have already built complete executable UML models of each domain, we will need to build a correspondence between different elements of each of the participating domains. The correspondence is between a specific type of thing in the application (catalog item) and an instance, expressed as data, in the user interface (the list of allowable ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access