Model Evolution Sample Clauses

Model Evolution. The PROV structure used to represent a new model entity being created from an existing one is very similar to that used for model introduction but with the addition of further “used” entities defining the which model files were used a sources. Figure 29 shows the evolution of the UT CT model to have line follow sensors. Note that utCT.emx is not only connected to the activity by the used relation but is also connected to the unewCT.emx entity via a was derived from relation. In this example there was only one source model and one generated model and so there is no ambiguity regarding which models influenced which other models, however this is not always the case. If we consider the two modelling exercises shown in Figure 30 we see that ambiguity could be present. In the modelling2 activity, where the single 20-sim model is decomposed into smaller components, we can see that there is one source model and two generated models and we can infer that the two generated models were both influenced in some way by the single source model. However, in the modelling3 activity, in which openModelica versions of the 20-sim component models are produced, there are two source models and two output models. Here the derived relation helps to make explicit which of the produced models was influenced by which of the source models. This explicit lineage could be important if there is a need to trace some property through the model chain.