Bearbeite Vortrag: Controlling Metamodel Availability Through a Maturity Model

Du bist aus dem folgenden Grund nicht berechtigt, diese Seite zu bearbeiten:

Fehlende Berechtigung Bitte melde Dich mit Deinen KIT-Zugangsdaten an. Falls Du trotz Anmeldung diese Seite siehst, bitte eine/-n Wissensmanager/-in darum, Dich zur richtigen Gruppe hinzuzufügen.

Titel:	Controlling Metamodel Availability Through a Maturity Model	Zum ändern des Titels bitte anklicken und die Seite verschieben.
Vortragende(r):
E-Mail Vortragende(r):		Bitte beachten Sie: Durch den Eintrag hier wird die E-Mail-Adresse des/der Vortragenden öffentlich sichtbar. Daher bitte die KIT-Adresse verwenden.
Vortragssprache:
Vortragstyp:
Betreuer(in):		Falls ein Betreuer noch nicht in dieser Liste vorhanden ist, bitte auf der Seite Betreuer hinzufügen und dieses Formular neu laden.
Termin:
Vortragsmodus:
Kurzfassung:	Collaborative metamodel development often suffers from delays or premature exposure of unstable parts of the metamodel due to the lack of mechanisms for controlling the availability of metamodel changes. In practice, this leads to two major issues: either metamodel changes must wait on each other before being delivered, or changes are included in the delivery although they are not yet suitable for certain stakeholders. To address these problems, we introduce the Maturity-Management-System (MMS), which leverages a descriptive maturity model to classify metamodel changes into distinct stages, ranging from Initial to Released. By integrating this model with the Transitional Metamodel approach—a metamodeling technique that preserves old states for each change—the MMS derives the maturity of individual metamodel elements from the maturity of the corresponding metamodel changes. Based on the maturity assessment of individual metamodel elements, the approach enables filtering of immature parts of the metamodel during code generation and disables metamodel elements at runtime depending on the maturity requirements of the end users. To ensure metamodel consistency while allowing filtering and disabling of parts of the metamodel, a set of metamodel invariants is defined. The MMS enforces these invariants through the Reject and Synchronize strategies. Using the metamodel of the model-based electric/electronic development environment PREEvision as an example, it was demonstrated that 64 % of MOF-compliant metamodel changes are supported by the prototype. Evaluation results further show that the approach significantly reduces the waiting time between the completion of a metamodel change and its availability for code generation—by up to 88 %—while introducing only a marginal increase in metamodel complexity.	Bitte maximal 150 Wörter verwenden.

Diese Seite beobachten

Abbrechen