The Service Cloud paradigm stands for combination of cloud computing and SOA for the development of Software as a Service systems. OMG has now started discussions about a standardization process for PIM (Platform Impendent Model) for Cloud Computing (PIM4Cloud or CloudML). This work is in its starting phase and REMICS will participate in the OMG discussions regarding the RFP and later the standard itself. We foresee to use the SoaML[1]standard developed in the SHAPE[2]project and extend it in aspects related to cloud, especially the deployment of services.


KDM, standing for Knowledge Discovery Metamodel[6], is an OMG® standard led by the Architecture Driven Modernization ( task force. KDM is itself a standalone metamodel for modernizing legacy information systems by means of Model-Driven Development (MDD) but experience and practice show that key capabilities are missing in KDM. Several expected KDM packages are in the process of being specified (as standards) and next implemented. Abstract Syntax Tree Metamodel (ASTM) is one these packages to improve the fine-grain analysis and processing of code: ASTM builds upon KDM in order to represent software below the procedural level. This effort allows KDM to fully represent applications and facilitate the exchange of granular meta-data across multiple languages.


Interoperability is seen as the key to increase competitiveness of enterprises. With the move towards services-oriented architectures and the Service Clouds some of the old challenges of interoperability are no longer there, such as middleware procedure call protocols compatibility issues. However some of the more basic interoperability issues are still present, such as discrepancy in exchanged XML formats.

When exchanging information, creating service compositions and even calling a single service one does not always get the data in a format required. To solve these problems, mediation is a common solution. Nevertheless, the problem with mediation is that it often requires a lot of extra work in development, deployment and sometimes even running a special infrastructure for the mediation. This means that solving interoperability problems can be a cumbersome task and the solution may need to be integrated with the rest of your system. Model-Driven Interoperability has shown that lifting information to a higher level of abstraction can reduce the effort needed for mapping different information formats. Based on mappings and predefined transformations it is then possible to create some kind of mediation.


The idea of models@runtime results from that model executability, i.e., models endowed with an operational semantics. The OMG® is going to release FUML (beta available when writing these lines) standing for Semantics of a Foundational Subset for Executable UML Models ( This approach develops a metamodel that puts forward dedicated metatypes to embody execution notions. Concretely, metatypes like Event, State... are usually available in most common behaviuor-centered modelling languages but notions like Priority policy, Run-to-completion cycle (each instance corresponds to an event interpretation cycle)... are mandatory to create an action language.

Models@runtime are in essence executable but also persist at runtime to create a reflection layer in order to observe (read) and control (write) models. Application management is the spirit of technologies like Java Management eXtensions (JMX) are first-class domains in which models@runtime brings out a high significant added value.

UML Testing Profile (UTP)

The UML Testing Profile[7]is a specification of the OMG which defines a specification of test related artefacts. The UML Testing Profile is relevant in the REMICS context in order to model  test cases which are applied to the migrated system.

After a few years of experiences in using the first version of UTP it has been turned out that a couple of changes need to made to the definition of the UTP in order to make it more usable in practice and to cover a wider range of testing concepts. The has lead to the creation of a Revision Task Force at the OMG where among others also REMICS partners are already working on improving this specification.

The UML-Testing Profile specification of the OMG covers notation and concepts space for expressing testing relevant information. Fraunhofer FOKUS and SOFTEAM participated to the 1.1 RTF (Revision Task Force). The work has been conducted in close collaboration with the other members of the task force (e.g. bi-weekly telephone conference and face-to-face meetings). The first Revision Task Force has been finalized in June 2011 and a second Revision Task Force (RTP 1.2) has been charted in order to further improve this specification. This submission has been finalized in August 2012. Fraunhofer FOKUS is heading this Revision Task Force.

Software Metrics Metamodel (SMM)

The Software Metrics Metamodel[8](SMM) is used to structure the definition of metrics and metric computation results. Since metrics will be used during the migration process in REMICS it will be important to describe metrics and store evaluation results in order to give guidance during the migration process.

First version of the SMM specification of OMG is available but there are still many open issues which need to be resolved in order to make the specification better applicable in practice. It is expected that valuable feedback can be gathered during the course of the REMICS project which will then influence the SMM-specification. Currently, a RTF is running which has its report deadline set to September 30, 2011. It is expected that additional RTF will be charted.


On 12 November 2012 the working group of SEMAT submitted the third revised proposal of the Essence kernel and language [OMG Document ad/2012-11-01] as a response to the FACESEM RFP. to OMG members only)

REMICS, represented by SINTEF, IICT-BAS, Tecnaliaand SOFTEAM, has been supporting the standardisation. SINTEF is the main contact and editor of the proposal. The proposal is also publicly available at the SEMAT website:

The Domain-Specific Language and a kernel of essentials for Software Engineering, DSL4SE[9], is an ongoing standard in the OMG for the creation of a language and a kernel that allows people to describe the essentials of their current and future practices and methods in a light way; so that they can be composed, simulated, applied, compared, enacted, evaluated and measured by practitioners as well as taught and researched by academic and research communities. The initiative is supported by the committers of the SEMAT[10]initiative.



[3]See these described in in REMICS deliverable D2.1.






[9]“Domain-Specific Language and a kernel of essentials for Software Engineering (DSL4SE) draft RFP”, ad/11-02-01,