bookmarks  4

  •  

    Papyrus is aiming at providing an integrated and user-consumable environment for editing any kind of EMF model and particularly supporting UML and related modeling languages such as SysML and MARTE. Papyrus provides diagram editors for EMF-based modeling languages amongst them UML 2 and SysML and the glue required for integrating these editors (GMF-based or not) with other MBD and MDSD tools. Papyrus also offers a very advanced support of UML profiles that enables users to define editors for DSLs based on the UML 2 standard. The main feature of Papyrus regarding this latter point is a set of very powerful customization mechanisms which can be leveraged to create user-defined Papyrus perspectives and give it the same look and feel as a "pure" DSL editor.
    7 years ago by @gresch
    (0)
     
     
  •  

    Das OKSIMO Projekt entwickelt einen Satz von Open Source Software Lösungen um tägliche Fragen und Aufgaben zu formalisieren, modellieren und simulieren. Dienstleistungen Das OKSIMO Team bietet auf Ihre Bedürfnisse zugeschittene Dienstleistungen. Erfahren Sie mehr über Unterstützung, Betreuungs- und Serviceoptionen für Ihr OKSIMO Projekt. Model Library Die Model Library ist eine durch das OKSIMO Team unterstützte Open Community um den freien Austausch von Wissens-Modellen für die OKSIMO Software Suite zu ermöglichen. Projekt Informationen Erfahren Sie mehr über das OKSIMO Projekt, aktuelle Entwicklungen, offene Fragen sowie unsere Benutzer- und Entwicklergemeinde.
    9 years ago by @gresch
    (0)
     
     
  •  

    Have you ever evolved your metamodel in EMF and your models were no longer valid afterwards? Or have you avoided to evolve your metamodel in order not to invalidate your models? Or have you even deteriorated your metamodel so that it remains downwards compatible to previous versions in order to avoid these problems? This site introduces COPE, a tool based on EMF that eases the migration of models in response to an evolving metamodel. COPE explicitly records the history of the metamodel as a sequence of changes and allows to attach information of how to migrate models (which is referred to as coupled evolution). The attached information can be used to automatically migrate models to the new version of the metamodel. COPE even goes one step further and allows to reuse combinations of metamodel adaptation and model migration steps across metamodels. In order not to disturb EMF users in their habits, COPE seamlessly integrates into the Ecore editor. A demonstration of the tool in action can be looked at here. It is planned to contribute COPE to the Eclipse community.
    9 years ago by @gresch
    (0)
     
     
  •  

    A meta-programming approach to general data modeling. Introduction Meta-JB is a MetaClass/MetaObject layer providing generic access to model implementations, decoupling application logic from underlying implementation details, and allowing user interfaces (Swing, HTML, etc.) to be dynamically generated at runtime. By wrapping model implementations in MetaObject adapters, applications can interact with the model layer in a homogenous way. Description Meta-JB extends the Java Beans-based meta-programming concept to provide more generic access to object attributes and descriptions for any model object with an appropriate adapter. The descriptions of a class's properties (the MetaClass) and access to an object's attributes are decoupled from actual implementations by adapters implementing a Map-like name/value interface (the MetaObject). Because the thin framework is built on generic interfaces, it is not tied directly to real Java bean implementations and can also be used for anything that can access values by name. (Some examples are SQL result sets, HTTP request data, or simple hash maps.) Once a "class" has been described, the information can even be applied to different underlying implementations. The MetaClass/MetaObject layer is a foundation for dynamically generating user-level access to application object models. Toolkits are provided for generating Swing GUIs at runtime or dynamically rendering objects as XML using the class descriptions. On the drawing board is support for generating HTML forms and views as well. Future development may also extend to a collaborative data access layer.
    9 years ago by @gresch
    (0)
     
     
  • ⟨⟨
  • 1
  • ⟩⟩

publications  5

  • ⟨⟨
  • 1
  • ⟩⟩