5/19/2023 0 Comments Modelio tutorial![]() All entites in this model have unique IDs and are referencing back to the top-level MS entity. At the instance level this would also be an actual entity of some sort, which binds everything together, by back-referencing to its unique ID. The model in this repo has a proper entity, which encapsulates all the required and optional tables. One of the weaknesses of the current MSv3 draft is the fact that there is no top level MS entity. In addition to these fundamental model properties there is also a lot of (hidden) detail in the model. the SKA-MSv3, you would start with all the MSv3 mandatory tables and the option to add additional columns and tables. Once done, the beauty is that you could simply switch the tool to MS modelling and the only options you would see are proper MS table and column classes, rather than generic classes. Unfortuntely there is no standard for this kind of modelling and it would thus lock us to a certain tool. The current model is more or less just a short-cut and the next step would be to implement a proper meta-model for Modelio (for instance). If you switch Modelio (or any other UML tool) from modelling UML to modelling and Entity-Relationship model you are changing the meta-model of the tool itself, which gives you access to the definitions of the meta-model. Meta-modelling is quite tricky even in UML, since the meta-model is actually implemented on the tool level rather than the model level. Instantiating such a table class needs to happen when generating a physical MeasurementSet. Every actual implementation of a MSv3 table (for example the MAIN table class) is then an instance of this meta-model and thus a class, but obviously not yet an actual MAIN table of a physical MeasurementSet. In principle this is only required for the basic MS table definition, but since it has not been done before we have started at that level and it is included here. Which means that an instance of this model is a set of classes rather than an object. This also points to a quite fundamental property of the MSv3 table model: It actually is a When modelling the actual tables each column is thus of type MsTableColumn_class. In this model this is used as a complex type definition, which is prefectly valid in UML, but not in VO-DML (and thus the warnings mentioned above). This class is defining all mandatory and optional attributes required to properly define a MSv3 table column. This requires to download the Modelio debian package from ![]() Once installed the SKA MSv3 model can be loaded directly from the repository by pointing the Modelio workspace path to the Modelio/workspace folder in the repository.Īlternatively this repo also contains a Dockerfile in the Modelio subfolder to generate a docker container which will mount the workspace from this repo directly when started. It is available for free on various platforms and can be downloaded from the Modelio web site. The model has been created using the Modelio 4.1.0 UML modeller (public version). The base MSv3 model, which is the VO-DML compliant model of the MSv3 as described in the document with some modifications to address modelling issues, will be kept as a permanent release tag, all additional modifications will then happen on a SKA branch. This repository tracks the status of the development of a UML/VODML model for the Measurement version 3 with modifications to address shortcomings or special SKA requirements.
0 Comments
Leave a Reply. |