• Print

Research Project Symposium Programme

This symposium will be held in Polytech'Montpellier in conjunction with the three co-located conferences (ECMFA, ECOOP and ECSA) on Monday and Tuesday 1-2 July 2013.

Registration/Check-in starts at 7:15am in the same building.

The research project symposium will take place in room: TD014.

Monday, 1st July 2013:

  • GEMOC Initiative : http://gemoc.org/meeting-ec2013
    Benoit Combemale1, Robert B. France2,Jeff Gray3, Jean-Marc Jézéquel1
    1University Rennes 1, France
    2Colorado State University, USA
    3University of Alabama, USA
    Abstract: GEMOC is an open initiative that aims to develop breakthrough for software language engineering (SLE) approaches that support global software engineering through the coordinated use of multiple domain-specific languages. GEMOC researchers aim to provide effective SLE solutions to problems associated with the design and implementation of collaborative, interoperable and composable modeling languages.
    The GEMOC initiative aims to provide a framework that facilitates collaborative work on the challenges of using of multiple domain-specific languages in software development projects. The framework consists of mechanisms for coordinating the work of members, and for disseminating research results and other related information on GEMOC activities. The framework also provides the required infrastructure for sharing artifacts produced by members, including publications, case studies, and tools.

Tuesday, 2nd July 2013:

  • Legacy2Cloud:
    Franck Barbier, University of Pau, France
    Imad Bernoussi, BLU AGE software, France
    Abstract: In the overall Model-Driven Development (MDD) problematics, Platform-Independent-Models (PIMs) are transformed into Platform-Specific Models (PSMs) weaving PIMs with PDMs (Platform Description Models).
    With the emergence of cloud platforms, business analysts simply expect the possibility of designing cloud applications based on PIMs, which represent domain concepts, business requirements... Traditionaly, PIMs are expressed in UML or, in more subtle cases, in a tailor-made DSML (Domain-Specific Modeling Language).
    Concomitantly, software architects design PDMs. PDMs match to platforms. With regard to the hereterogeneity of cloud APIs, one PDM correspond to a given cloud platform, a cloud platform version and/or a cloud platform configuration, etc. PDM design is a complex cutting-edge technology with support in open-source products (PDMs are "cartridges" in AndroMDA) or in commercial products (PDMs are BSPs in Blu Age®). Research on MDD + cloud is nowadays very open including the possibility of generating towards neutral APIs like jclouds.
    However, the approach above described may be viewed as “theoretical” in the sense that hands-on software development is greatly depending upon dinausor legacy information systems whose linking to the Cloud is subject to a lot of inertia. One may think in terms of interoperability between old systems and new cloud-based systems with, probably, heavyweight resulting architectures. One may differently think in terms of software modernization with the help of MDD. However, the elaboration of models is not natural and easy for average software people in industry, greatly slowing down the penetration of MDD.
    In Legacy2Cloud, PIMs are elaborated from legacy code (e.g., COBOL) and associated legacy frameworks (Pacbase, CICS, mainframe OSs from the ‘80s…). Standards exist for this specific purpose: Abstract Syntax Tree Metamodel (ASTM) and Knowledge Discovery Metamodel (KDM). In this context, Reverse modeling is the model transformation phase in which the legacy code is first represented as ASTM models. Next, it is represented as KDM models to capture the legacy system semantics of data, execution flows, business rules, GUIs, architecture, components, services... The ultimate model is a UML model showing the legacy system as a PIM. The Forward engineering phase is the weaving of this PIM with a PDM to compute an executable PSM deployable on a given cloud platform, a cloud platform version and/or a cloud platform configuration...
    This tutorial exposes research and associated results obtained in the ReMiCS FP7 ICT European STREP project (www.remics.eu). ReMiCS standing for "Reuse and Migration of legacy applications to Interoperable Cloud Services" tackled the Legacy2Cloud problematics. This tutorial also exposes and illustrates partial implementation of ReMiCS results in the BLU AGE® tool chain, which both encompasses Reverse modeling and Forward engineering. A BLU AGE® demo. is planned in the tutorial based on an industrial case study.
  • BETTY - Behavioural Types for Reliable Large-Scale Software Systems (COST action IC1201) : http://www.cost.eu/domains_actions/ict/Actions/IC1201
    Antonio Ravara, New University of Lisbon, Portugal
    Simon J.Gay, University of Glasgow, UK
    Abstract: Modern society is increasingly dependent on large-scale software systems that are distributed, collaborative and communication-centred. Correctness and reliability of such systems depend on compatibility between components and services that are newly developed or may already exist. The consequences of failure are severe, including security breaches and unavailability of essential services. Current software development technology is not well suited to producing these systems, due to the lack of high-level structuring abstractions for complex communication behaviour.
    The COST Action Behavioural Types for Reliable Large-Scale Software Systems (http://www.cost.eu/domains_actions/ict/Actions/IC1201) uses behavioural type theory as the basis for new foundations, programming languages, and software development methods for communication-intensive distributed systems. Behavioural type theory encompasses concepts such as interfaces, communication protocols, contracts, and choreography. As a unifying structural principle it will transform the theory and practice of distributed software development.