<html>MODELS 2015<br /><br />09-29<br /><br />CloudMDE - Modeling On and For the Cloud Workshop<br />- 14 people<br /><br />Dimitris Kolovos: Code Generation as a Service<br />- goal: make modeling easier to start<br />- MSc thesis<br />- move code generators, metamodels, templates, validators etc. to a server<br />- calling the code generator creates an asynchronous job on the server<br />- generators can be loaded from github repos<br />- publicly accessible version is yet to be deployed<br /><br />Juan De Lara: Building MDE cloud services with Distil<br />- DSL to describe MDE services in the cloud<br />- MongoDB, Heroku<br />- prototype software<br />- miso.es/tools/distil.html<br /><br />Daniel Varro: Optimization of Incrstrongental Queries in the Cloud<br />- IncQuery-D<br />- differebt resource allocation optimizations<br />- Akka actors, Yarn resource management, ZooKeeper monitoring<br />- dynamic reallocation is future work<br /><br />Informal discussions<br /><br />- ElementTypeFramework of Papyrus: not usable to solve the "easily adding a transition" problem<br />- properties view customization is a better option:<br /> - add a new field to the properties tab of the transition to be able to select a signal<br /> - it is not clear how to use this to add the trigger, the signalevent etc, but seems feasible<br /> - doc: Properties View / Advanced customization<br /> - looking at the code of adding multiplicities can be a good example<br /> - contact: Camille Letavernie<br /><br />Open Source for MDE Workshop<br />- 30 people<br /><br />Francis Bordelaux: 5 Years of ‘Papyrusing’: Migrating Industrial Development from a Proprietary Tool to an Open Source Tool<br />- migration from a tool to another one: 2-5 years - it was 5 in this case<br />- issue with commertial tools: end-of-life, end-of-support, licences ==> open source<br />- ECIM toolchain<br /> - started in 2010<br /> - 2009: Ericsson study on open source<br /> - Papyrus is far from usable, but still elected as best choice<br />- all of the modelling tools "absolutely sucks"<br />- model diff-merge in the large scale is complex<br />- model review is also not solved<br />- "new way of working":<br /> - customer/client relationship ==> peer to peer<br /> - Ericsson-specific requests ==> generic requests, community point of view<br /> - give use cases to the suppliers<br />- Replace RSA-RTE with Papyrus: not ready, some years needed<br />- Papyrus Industrial Consortium<br /><br />Umple Tutorial<br /><br />umple.org<br />- web based and Eclipse plugin<br />- support for class modeling, state machines and (in-progress) composite structures<br />- no action code - behavior is written in Java/C++/Php etc. in separate files, the code generator inserts the fragments<br />- no execution / debug / animation support<br />- can generate random traces from state machines<br />- can inject trace points in generated code<br />- diagram is either editable, but has crappy first layout or immutable graphwiz image<br />- state machine diagrams are not editable<br />- implemented in itself and Java<br /> </html>