mros-robmosys-itp / metacontrol_tooling Goto Github PK

o Manual test: write small example model instances that we can express each element that is required
o Criteria to evaluate our test instances (they overlap):
· Requirements coverage
· Metamodel coverage

A set of rules should be defined to capture the transformation between the MROS metamodel and OWL metamodel. OWL metamodel is used so OWL model can be specified and used by the meta controller.

T6.2 MROS transformations, including: 1) the Ecore2OWL transformation to automatically generate the OWL file with the initial runtime model from the system architecture model created with the metacontrol view, and 2) the Ecore2SMH transformation to obtain the “Systems Modes and Hierarchy” model file from the same system architecture model.

The name mros.mros could be more informative about the system that is modelled in this file.
I propose pilot_urjc_patrol.mros

Ecore implementation of MROS metamodels and an Eclipse plugin with a metacontrol view that allows system architects to define alternative skill implementations.

• Create OWL metamodel that can be used to represent the runtime model of the system architecture that can be used by the metacontroller. The OWL metamodel should capture the “Systems Modes and Hierarchy” developed in metacontrol_ontology issue