SlideServe
Menu
Préférences
© SlideServe · v2026

A graphical specification environment for GCM component-based applications

taipa avatar
20 diapositives · 380 Views · Jul 19, 2014

A graphical specification environment for GCM component-based applications. INRIA – I3S – CNRS – University of Nice-Sophia Antipolis EPC OASIS Oleksandra Kulankhina Internship supervisor: Eric Madelaine. Background: modeling tools for component-based software Grid Component Model (GCM).

A graphical specification environment for GCM component-based applications - slide 1
01 / 20A graphical specification environment for GCM component-based applications
1 / 17

Télécharger la présentation

A graphical specification environment for GCM component-based applications
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. A graphical specification environment for GCM component-based applications INRIA – I3S – CNRS – University of Nice-Sophia Antipolis EPC OASIS Oleksandra Kulankhina Internship supervisor: Eric Madelaine

  2. Background: modeling tools for component-based softwareGrid Component Model (GCM) Client interface Binding Server interface

  3. Background: modeling tools for component-based softwareGCM Architecture in VerCors Composite component GCM: Hierarchical model GCM: Separation of concerns: functional (business logic) and non-functional (control) aspects Membrane Primitive component Content

  4. Background: modeling tools for component-based softwareThe aspects of the project 1 2 3 The GCM implementation : • ADL generation • Component factory Formalization and semantics: mathematical formulas and proofs The Editor for the GCM Architecture specification: VerCors

  5. Motivation Formalization issues: • The existing formal model does not contain the Membrane • There is no properly defined set of constraints for the GCM Architecture. The well-formed component definition does not consider the membrane.

  6. Motivation Implementation issues: • The technology of VerCors (Topcased) is not maintained: cannot be ran on the latest Eclipse versions • The behavior (e.g. finite state machines) of Components cannot be specified in VerCors

  7. Agenda • Background • Motivation • Formal Model extension • Examples of constraints • The new VerCors prototype creation • Contributions and future work

  8. Formal model extension : ADL -> ADL-V2

  9. Agenda • Background • Motivation • Formal Model extension • Examples of constraints • The new VerCors prototype creation • Contributions and future work

  10. Examples of new constraints • Subtyping constraint • Separation of concerns Control level constraint

  11. Agenda • Background • Motivation • Formal Model extension • Examples of constraints • The new VerCors prototype creation • Contributions and future work

  12. Last Experiments with Eclipse Papyrus Result: • A simple editor was implemented and integrated in Eclipse Papyrus. It allows creation of primitive components, bindings and interfaces. Limitations: • The development is extremely time-consuming • The Papyrus project is unstable • It is unclear if it is possible to link our model with UML one: we did not succeed

  13. Obeo Designer Principles Code generation uses A set of Eclipse plugins for graphical editors creation Create graphical editors Based on Based on UML Diagrams Editors • Obeo: • Startup project from the NantesUniversity • Commercial project • The free version Sirius is going to be released in September 2013 • Strong community

  14. Obeo Designer Principles Exploit the Models Describe the Graphical Designer Define the Domain Model

  15. New VerCors prototype: implementation of existing features

  16. New VerCorsprototype: integration with UML Diagrams

  17. Agenda • Background • Motivation • Formal Model extension • Examples of constraints • The new VerCors prototype creation • Contributions and future work

  18. Contributions (intermediate !) The formal part: • The GCM formal model was extended. It includes the membrane now • The set of consistency constraints for the GCM Architecture was defined and formalized The implementation part: • The VerCors Prototype was created in Obeo Designer. Most of the features of the old version of VerCors were implemented • The UML Diagrams were integrated in the VerCors prototype

  19. Ongoing work Short term: • Implement the diagrams validation in the new VerCors prototype in Obeo Designer; express rules using Acceleo • Implement the ADL-V2 file generation • Check scalability: develop a significant use-case Longer term • Create the VerCors prototype in the free version of Obeo Designer

  20. Thank you! Oleksandra Kulankhina A graphical specification environment for GCM component-based applications • References: • VerCors platform homepage: http://www-sop.inria.fr/oasis/index.php?page=VerCors • Obeo Designer homepage: http://www.obeodesigner.com • Obeo Designer community homepage: http://www.obeonetwork.com/group/obeo-designer • RabéaAmeur-Boulifa, LudovicHenrio,  Eric Madelaine, Alexandra Savu, Behavioural Semantics for Asynchronous Components : http://hal.inria.fr/docs/00/76/10/73/PDF/RR8167.pdf