| 
Sending again the message that was rejected. Best, -- Matteo   
De : MORELLI Matteo
Envoyé : jeudi 8 décembre 2016 01:16
 À : 'Dimitris Kolovos' <dimitris.kolovos@xxxxxxxxxx>; GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx>
 Cc : papyrus-ic discussions <papyrus-ic@xxxxxxxxxxx>; CUCCURU Arnaud <arnaud.cuccuru@xxxxxx>; TATIBOUET JÉRÉMIE <jeremie.tatibouet@xxxxxx>
 Objet : RE: [papyrus-ic] Notes from a Papyrus training workshop
   Hello Dimitris ! Sorry for the long wait… please find the additional resources on the integration between Papyrus and Simulink at this
 address: ftp://ftp.cea.fr/incoming/y2k01/morelli-matteo-1481153530/SysMLSimulinkActivitiesReportDraft2.zip.
 NB: the file is available on our ftp server for just 5 days.   The zip archive contains a pptx presentation with companion videos showing the tool in action. Since the slides are a
 “work-in-progress”, do not hesitate if you or your course attendees want more information/clarification on a specific subject. Also, do not hesitate to contact us to discuss any extension to this work that may be of interest for you.
   For what concern Massif, indeed we are using it as the EMF format to manage the transition from SysML and Simulink (and
 back). We have also developed extensions to the Simulink meta-model in Massif to enable the representation of Stateflow models. You will find additional details in the slides and videos.   Best, -- Matteo     De : Dimitris Kolovos [mailto:dimitris.kolovos@xxxxxxxxxx]
Envoyé : jeudi 1 décembre 2016 15:00
 À : GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx>
 Cc : papyrus-ic discussions <papyrus-ic@xxxxxxxxxxx>;
 MORELLI Matteo <Matteo.MORELLI@xxxxxx>; CUCCURU
 Arnaud <arnaud.cuccuru@xxxxxx>; TATIBOUET JÉRÉMIE
 <JEREMIE.TATIBOUET@xxxxxx>
 Objet : Re: [papyrus-ic] Notes from a Papyrus training workshop
   
Thanks for your reply and for the additional resources! 
> We are working intensively on that point for several clients (Plastic Omnium and Sherpa Engineering) and also in the context of a European project in the context of co-simulation via FMI standard (OpenCPS project).
 Matteo I cc my response will send some details and video showing what Papyrus is able to do on this subject. 
There was a strong interest about this so any pointers would be more than welcome. I've also started looking at Massif [1, 2] from IncQuery Labs. 
> Dimitris, do not hesitate to join the PIC 
> BTW, is it possible to know who were the participants to your workshop? 
The seminar was attended by engineers from GE Aviation, Finmeccanica, BAE Systems, Rapita Systems, Rolls-Royce, D-Risq, Altran, Cobham, MBDA Systems and Leonardo. 
  
On 30 November 2016 at 23:04, GERARD Sebastien 166342 <Sebastien.GERARD@xxxxxx> wrote: 
Hi Dimitris,   Nice to see we can count on a new Papyrusien ;-) See some additional comments below.   Cheers, Séb.   PS: BTW, is it possible to know who were the participants to your workshop?       
  Dimitris,
 
Thanks very much for taking the time to send the questions and share the feedback. This is very much appreciated. This is exactly the type of things we need.  
Hi everyone,
 Today I delivered a 2-hour long Papyrus training workshop to 15-20
 engineers from UK industry and I thought I'd summarise some of their
 questions/remarks about Papyrus (before I forget), in case any of
 these can feed into future discussions/actions:
 
 - They liked the idea of being able to simplify the UI through a
 configuration model as demonstrated in [1]. One question was whether
 one can switch between the simplified/full UI at runtime (i.e. to
 “break-out" of the simplified UI when needed).
 [[SG] >]  If you want to see more oin this subject, here are some ongoing work details
 on that subject: http://wiki.eclipse.org/Papyrus/Oxygen_Work_Description/NewFeature/PapyrusAFViewpointSwitch   
The full UML is always available through configuration.   
- There was a question about who are the main contributors to the
 development of Papyrus
 
Seb can had to it regarding Papyrus contributors/committers, but here is the list of main contributors to the aspects Ericsson is involved in. In terms of projects,
 this includes Papyrus, Papyrus-RT, EMF Compare and EGit integration. This list includes different types of contributors: committers, product and project managers (managing the open source projects), and people defining requirements/use cases and performing
 testing/validation of the delivered functionality 
· 
All4Tec: Celine Janssens, Mickael Adam, Nicolas Fargues et
 
·       
CEA: Sebastien Gérard, Remi Schnekenburger, Florian Noyrit, Benoit Maggi, Asma Smaoui, Ansgar Radermacher, Patrick Tessier[[SG] >]
,Quentin Le Menez , Francois Le Fevre, Suai Li, Vincent Lorenzo, Mathilde Arnaud Arnaud Cuccuru
et Jérémie Tatibouet-- CEA[[SG] >]
 (me ;-) leads the work on Papyrus 
EclipseSource: Maximilian Koegel, Philip Langer, Alexandra Buzila, Martin Fleck, Stefan Dirix -- EclipseSource leads the work on EMF Compare and its integration in Papyrus
Ericsson: Simon Delisle, Patrik Nandorf
Tieto: Peter Cigehn 
Zeligsoft: Simon Redding, Charles Rivet, Ernesto Posse, Young-Soo Rho — Zeligsoft lead the work on Papyrus-RT
Independant: Christin Damus, Bran Selic, Magged Elaasar 
You can find the list of Committers to the different projects    
- Another question was whether Papyrus supports any import interfaces
 from other tools? (Developing such "import" facilities is an
 unrewarding task for researchers so we may want to pool resources
 here)
 
In the context of the Ericsson work, we have funded the development of model import for RSA (RSA to Papyrus), which is currently used to migrate from RSA to Papyrus
 at Ericsson, and RSA-RTE (RSA-RTE to Papyrus-RT) which is currently developed together with Papyrus-RT (Papyrus-RT is planned to be released at the end of January/beginning of February together with C++ Code Generator and Run-Time). [[SG] >]
In addition, Papyrus also support import/export of cvs format and ReqIF. 
- They liked the idea of being able to split models across multiple
 projects/files as many of them are struggling with large monolithic
 models stored in proprietary tool-specific repositories
 
This was one of the key priorities for Ericsson from the very beginning in all our development contexts and we worked closely with CEA (who did the development
 work) to implement the required support. This aspect is extensively used in the project (over 120 users) where are using Papyrus as a replacement for RSA. [[SG] >] In the model explorer, you can right click on the model element you would
 like to see in a separate resource and apply the “Create Submodel” command as shown below: 
 
- They also liked the idea of being able to use Git to version control
 models - especially after I demonstrated EMFCompare. They didn't seem
 to be too bothered that there's no built-in support for "live"
 collaboration (I was prepared to talk to them about the Papyrus-CDO
 integration but I saw little demand for a model repository)
 
This was another key Ericsson priority from the very beginning as Git is now the main technology used in Ericsson. EclipseSource and Obeo have led the development
 of this part.   
- There was a question about if/how Papyrus can interface to Simulink
 (I had to take this one offline as I have no idea)
 
I am not aware of any real implementation for the integration of MathWorks Simulink and Papyrus, but I know that Zeligsoft has worked on this type of integrations
 in the past. Here are links to two videos (one with MathWorks Simulink and one with Agilent SystemVue) that were developed in the context of Software Defined Radio (SDR) projects. The integration was done with Zeligsoft CX, which is a component-based modeling
 DSL built on top of IBM RSA. Similar integrations could be developed for Papyrus/Papyrus-RT. There is in fact quite much interest on this specific topic in the context of Automotive, Mechatronic, and CPS. We can potentially look at developing such an integration
 if industrial members/partners are interested in financially committing to it. You can contact Simon Redding (Zeligsoft) if you want additional details.   [[SG] >] We are working intensively on that point for several clients (Plastic Omnium
 and Sherpa Engineering) and also in the context of a European project in the context of co-simulation via FMI standard (OpenCPS project). Matteo I cc my response will send some details and video showing what Papyrus is able to do on this subject. 
- One of the attendees asked if/how UML model elements in Papyrus can
 be linked to elements from domain-specific (EMF) models (also had to
 take this offline)
 
I will let more other people comment on this one to provide appropriate level of details.   
- There was a question about model execution capabilities to which I
 responded by pointing the person that asked towards Moka
 
Mona is the only project that I am aware of. [[SG] >] @Arnaud or Jeremie: can you please send us pointers (tuto or/and video)
 to Papyrus-Simulation (a.k.a. Moka)   
- All in all, there was overwhelming support for continuing to
 evaluate Papyrus and we’ll run a second Q&A workshop after Christmas
   
   
 
 --  |