Eclipse Unconference France 2015
This page is the live agenda for the Eclipse Unconference at ENSEEIHT, in Toulouse, on June 22-23, 2015.
If you want to suggest a session, please copy/paste the template at the bottom of the page and send the request to gael.blondelle _ at _ eclipse.org. You can also support a session proposal or comment it.
- Tracy Miranda: Science Working Group
- Ignacio Garro: Automotive Working Group
- Gaël Blondelle / Boris Baldassari: PolarSys / Embedded Systems
- Benjamin Cabé: IoT Working Group
- Francis Bordeleau / Sébastien Gérard: Papyrus
- Jean-Michel Bruel / Thierry Monteil: Eclipse for academics
- Ferhat Erata: ModelWriter meeting
Registration and Dinner
- There are two options:
- An Unconference Dinner is planned in Toulouse on the evening of June 23rd. Price is €60 (VAT included) and can be added when registering for EclipseCon France or for the Unconference Only. There are only 50 seats available and we will allocate them on first-come, first-served basis. So if you want to attend the dinner, please register quickly.
During the Unconference, we will have lunch onsite with the Eclipse Board of Directors and we will host a poster session at the same time. Please send an email to gael.blondelle _at_ eclipse.org if you plan to come with a poster.
Here is the current of posters:
- ReqCycle - Atos, Samares Engineering
- Papyrus-RT - CEA, Zeligsoft
- Eclipse Profiles - Yatta: Install, Share, Update: With Eclipse Profiles getting your Eclipse setup ready and sharing it with your team - or the world - is just a couple of clicks away.
Monday, June 22
|14:00-17:00||Science (A201)||IoT (A202)||PolarSys Rover Hackathon (A301)||Designing a CPS with Papyrus (A302)||Dev room (A304)||ModelWriter (A303)|
Tuesday, June 23
|9:30-9:50||Welcome Coffee (A03)|
|9:50-10:00||Tuesday Unconf Introduction and Program Presentation (A01)|
|10:00-12:00||Science (A201)||IoT (A202)||PolarSys infrastructure (A301)||Moka: Execute your Papyrus models (A302)||Dev room (A304)||ModelWriter (private meeting) (A303)|
|12:00-14:00||Lunch and Poster Session (A03)|
|14:00-15:30||Science (A201)||IoT (A202)||PolarSys projects updates (A301)||Automotive Working Group (A302)||Dev room (A304)||ModelWriter (private meeting) (A303)||Session: "The Eclipse ecosystem explained to academics" (A203)|
|15:30-16:00||Afternoon Coffee Break (A03)|
|16:00-17:30||Science (A201)||IoT (A202)||Common PolarSys and Automotive Working Group projects updates (A301)||Dev room (A304)||ModelWriter (private meeting) (A303)||Session: "The Eclipse ecosystem explained to academics" (A203)|
- 14.00 - 14.15 – Intro
- 14.15 - 15.30 – Tiaki project proposal
- Presentation of the Tiaki project proposal and collaboration opportunities with other projects
- 15.30 - 16.00 – Coffe break
- 16.00 - 16.15 – Open Source IoT Server
- Update on ongoing discussions regarding OSS IoT Server architecture, and next steps
- 16.15 - 17.00 – Eclipse IoT demonstrators
- Identify and discuss end-to-end demo scenarios to be "PoC'd" on Tuesday in the dev room
- All-day (starting at 10 am)
- Dev/hack room: Tiaki / SmartHome / Leshan / MQTT hackathon
- Afternoon meetings
- 14.00 - 15.30 – Project updates: each project will spend 10 minutes updating on their current status. The update should include:
- Project Overview: Short (1 slide) reminder about your project functionality. This is for people who might be new.
- Project stats: tell us how well your project is doing. Number of download, number of contributors, number of bugs opened, number of mailing list subscribers, etc.
- Project plan: when is the next release and what are the key features.
- Key Challenges: What challenges/issues are you having?
- Collaboration Opportunities: Where do you see potential for collaboration with other Eclipse IoT projects or other communities.
- Vorto - Olaf
- Californium - Julien?
- Tiaki- Regis & Souheil
- Leshan - Julien
- Wakaama - Julien
- Kura - Pierre
- OM2M - Mahdi
Science Working Group
- 9.30 - 10.00
- Welcome Coffee (A03)
- Tuesday Unconf Introduction and Program Presentation (A01)
- 10.00 - 12.00
- Introductions - Say hello and share what interests you about the Science Working Group
- Background on Science Working Group and description of current activities
- Science symposium - 5-10min demos or introduce your latest work to SWG
- 12.00 - 14.00
- Lunch and Poster session
- 14.00 - 15.30
- Science symposium - More demos
- Brainstorming sessions - carry on discussions from previous meetings, mailing lists, etc. Discuss collaborations
- 15.30 - 16.00
- Afternoon Coffee Break
- 16.00 - 17.30
- Hands on Sessions - chance to look at code and play with tools, maybe with Dawnsci, AnalysisRPC, Instrumentino others?
Automotive Working Group
- Automotive working group status
- Automotive Project updates
PolarSys Working Group
PolarSys Rover Hackthon
Joins us to brainstorm on the [rover] demo: * How to use it as a common demonstrator
- Share approaches and model parts
- What part of Systems Engineering process do we cover with this demo
- PolarSys maturity assessment
- PolarSys project management
- PolarSys testing infrastructure
PolarSys projects updates
The place to give a short (20 minutes) update about your project. The second part of this session will be shared with the Automotive working Group.
- Papyrus RT (Charles Rivet)
- Gendoc (Atos)
- Sirius (Samuel Rochet)
- EMF Compare & eGit (Etienne Juliot)
Send us an email to add your project here
Ask for your space in the dev room! One day before the EclipseCon France, get a room to work on your Eclipse project. The purpose is to assign a dev room to self-organizing groups to work together on open source projects, to discuss topics relevant to a broader subset of the community, and to hack code...
List your project here if you plan to be there and want to attend gather your folks in the dev room:
- Your name : Project name
Designing a CPS with Papyrus
- Session type: Presentation / Live demo / Hands-on
- Contact: email@example.com, firstname.lastname@example.org
- Time: 45 minutes
- Title: Using MDE to Design a Complex Cyber-Physical System: An Experiment with Papyrus
In recent years, Cyber-Physical Systems (CPS) have been the focus of many research projects. A CPS integrates computation with physical processes. Such systems are usually composed of embedded and networked computers that control physical components, who interact with the real environment in real-time. A Remote Operated Vehicle (ROV) is a typical CPS. Such vehicles may operate in harsh environments (such as Mars or Venus) where repair and assistance are not available after deployment. Therefore, it is crucial that the design and development of such systems meet hard constraints.
Model-Driven Engineering (MDE) is a development approach that proposes software and system design methods that help engineers build reliable complex systems. Several works have already applied MDE for the design of embedded systems. We propose an experiment to evaluate the MDE approach for the design of a CPS.
In this session a real ROV will be presented. In our work, we use Papyrus to design the ROV. Papyrus is a UML modeler with an eco-system of tools that typically support and promote MDE. In a live demo, we will show how the system is modeled with Papyrus and how Papyrus can interact directly with the physical system. This session also introduces fundamental concepts for the Moka session, on the simulation and analysis CPS.
Moka: Execute your Papyrus models
- Session type: Presentation (relies on the content presented during Designing a CPS with Papyrus)
- Contact: email@example.com, firstname.lastname@example.org
- Time constraints: 45 minutes
- Title: Moka: The Papyrus Framework for Model Execution based on Standards
Moka is a Papyrus module for execution of UML models, which natively includes an execution engine complying with Executable UML OMG standards – foundational UML (fUML, ) and Precise Semantics of UML Composite Structures (PSCS, ). Moka is integrated with the Eclipse debug framework to provide control (suspend / resume / step, etc.), observation (breakpoints, variables) and diagram animation during executions. Moka can be easily extended to support alternative execution semantics, and thereby be adapted to multiple usage scenarios and domains.
The use case concerns a small Lego Mindstorm © robot which is dedicated to space exploration. The system is mainly composed of a four wheels rover and a remote controller. The controller sends commands to the rover's actuators based on information captured by the rover's sensors. In this session, we will complete the Papyrus model of the rover built during the session "Designing a CPS with Papyrus". We will specify the behavior of the control part of the robot. The model will be simulated with Moka, in order to check that the modeled system performs the expected behavior. Once validated with simulation, the same model will be used to control the real system.
ModelWriter: Text & Model-Synchronized Document Engineering Platform
- Monday: Public meeting
- Tuesday: Private meeting
- Ferhat Erata, ModelWriter Project Leader <email@example.com>
- Moharram Challenger <firstname.lastname@example.org>
- Etienne Juliot <email@example.com>
- Monday 14:00 - 17:00 (Public)
- Tuesday 10:00 - 17:30 (Private)
Project Description: The objective of the ModelWriter project is to bring a quantum leap in the productivity of technical authors (such as software or systems engineers, project managers, business developers, etc.) who are engaged in authoring documents of a technical nature. The project also aims to improve the quality (consistency, completeness) of these documents that, in turn, will enhance the quality of companies’ products, e.g. via a reduction of cost of product defects. Finally, ModelWriter aims also to allow companies to further exploit, recycle and valorise their own internal knowledge, which is currently left unexploited in technical documents that are seen as a sequence of words only. To achieve this, the project envisions an integrated authoring environment called "ModelWriter", which will be locally used by each author / contributor. This will combine two parts, a semantic word processor (= the "Writer" part), which resembles a typical word processor but capable of "understanding" pieces of text and transparently creating models of contents out of them, and a Knowledge Capture Tool (= the "Model" part), which resembles a spreadsheet table, or other familiar information modelling tools.
The Eclipse ecosystem explained to academics
- Few things you need to consider if you plan to open source your project at Eclipse (Wayne Beaton, Eclipse Foundation)
- Return of Experience: Publication of OM2M by LAAS/CNRS (Thierry Monteil, LAAS)
- Eclipse as a research dissemination channel (Gaël Blondelle, Eclipse Foundation)
- Discussion / questions