Asset Oriented Modeling (AOM)

- Merging -


The ability to merge two or more models becomes important in large scenarios, where applications are developed by multiple groups, or when formerly distinct applications grow together. 

When merging two models, we usually have to deal with conflicting definitions. We adopt the strategy to loosen constraints so that the resulting model can host all instances from the original models. Because this results in a loss of semantic information, the original models still remain valuable: they provide a specific view on the new model. This merging method is used to combine models from different domains into one integrated model.

To merge two models M1 and M2 into a new model M3, we use the following rules:

When merging two assets A1 or A2 , the following rules apply:

When merging two Level 2 structures S1 and S2, the following rules apply:


When merging two models, the merging process can be influenced by applying a scope to one or both components:


When merging two models, the merging process can be influenced by defining a bindings between the two components. Bindings can be applied to L2S and assets. Given model A and B, the following bindings can be applied:

Structural restrictions apply. When an L2S L1 of model A is bound to an L2S L2 of model B the contents of L1 must not be bound to items outside of L2.


The application of Design Patterns to models is similar to the merging of two models. The following differences apply:

Home Definition Step-by-Step Examples Downloads

Contact: support 'at'