Model-driven software development requires techniques to consistently propagate modifications between different related models to realize its full potential. For large-scale models, efficiency is essential in this respect. In this paper, we present an improved model synchronization algorithm based on triple graph grammars that is highly efficient and, therefore, can also synchronize large-scale models sufficiently fast. We can show, that the overall algorithm has optimal complexity if it is dominating the rule matching and further present extensive measurements that show the efficiency of the presented model transformation and synchronization technique. / Die Model-getriebene Softwareentwicklung benötigt Techniken zur Übertragung von Änderungen zwischen verschiedenen zusammenhängenden Modellen, um vollständig nutzbar zu sein. Bei großen Modellen spielt hier die Effizienz eine entscheidende Rolle. In diesem Bericht stellen wir einen verbesserten Modellsynchronisationsalgorithmus vor, der auf Tripel-Graph-Grammatiken basiert. Dieser arbeitet sehr effizient und kann auch sehr große Modelle schnell synchronisieren. Wir können zeigen, dass der Gesamtalgortihmus eine optimale Komplexität aufweist, sofern er die Ausführung dominiert. Die Effizient des Algorithmus' wird durch einige Benchmarkergebnisse belegt.

During the overall development of complex engineering systems different modeling notations are employed. For example, in the domain of automotive systems system engineering models are employed quite early to capture the requirements and basic structuring of the entire system, while software engineering models are used later on to describe the concrete software architecture. Each model helps in addressing the specific design issue with appropriate notations and at a suitable level of abstraction. However, when we step forward from system design to the software design, the engineers have to ensure that all decisions captured in the system design model are correctly transferred to the software engineering model. Even worse, when changes occur later on in either model, today the consistency has to be reestablished in a cumbersome manual step. In this report, we present in an extended version of [Holger Giese, Stefan Neumann, and Stephan Hildebrandt. Model Synchronization at Work: Keeping SysML and AUTOSAR Models Consistent. In Gregor Engels, Claus Lewerentz, Wilhelm Schäfer, Andy Schürr, and B. Westfechtel, editors, Graph Transformations and Model Driven Enginering - Essays Dedicated to Manfred Nagl on the Occasion of his 65th Birthday, volume 5765 of Lecture Notes in Computer Science, pages 555–579. Springer Berlin / Heidelberg, 2010.] how model synchronization and consistency rules can be applied to automate this task and ensure that the different models are kept consistent. We also introduce a general approach for model synchronization. Besides synchronization, the approach consists of tool adapters as well as consistency rules covering the overlap between the synchronized parts of a model and the rest. We present the model synchronization algorithm based on triple graph grammars in detail and further exemplify the general approach by means of a model synchronization solution between system engineering models in SysML and software engineering models in AUTOSAR which has been developed for an industrial partner. In the appendix as extension to [19] the meta-models and all TGG rules for the SysML to AUTOSAR model synchronization are documented. / Bei der Entwicklung komplexer technischer Systeme werden verschiedene Modellierungssprachen verwendet. Zum Beispiel werden bei der Entwicklung von Systemen in der Automobilindustrie bereits früh im Entwicklungsprozess Systemmodelle verwendet, um die Anforderungen und die grobe Struktur des Gesamtsystems darzustellen. Später werden Softwaremodelle verwendet, um die konkrete Softwarearchitektur zu modellieren. Jedes Modell stellt spezifische Entwurfsaspekte mit Hilfe passender Notationen auf einem angemessenen Abstraktionsniveau dar. Wenn jedoch vom Systementwurf zum Softwareentwurf übergegangen wird, müssen die Entwicklungsingenieure sicherstellen, dass alle Entwurfsentscheidungen, die im Systemmodell enthalten sind, korrekt auf das Softwaremodell übertragen werden. Sobald danach auch noch Änderungen auftreten, muss die Konsistenz zwischen den Modellen in einem aufwändigen manuellen Schritt wiederhergestellt werden. In diesem Bericht zeigen wir, wie Modellsynchronisation und Konsistenzregeln zur Automatisierung dieses Arbeitsschrittes verwendet und die Konsistenz zwischen den Modellen sichergestellt werden können. Außerdem stellen wir einen allgemeinen Ansatz zur Modellsynchronisation vor. Neben der reinen Synchronisation umfasst unsere Lösung weiterhin Tool-Adapter, sowie Konsistenzregeln, die sowohl die Teile der Modelle abdecken, die synchronisiert werden können, als auch die restlichen Teile. Der Modellsynchronisationsalgorithmus basiert auf Tripel-Graph-Grammatiken und wird im Detail erläutert. An Hand einer konkreten Transformation zwischen SysML- und AUTOSAR-Modellen, die im Rahmen eines Industrieprojektes entwickelt wurde, wird der Ansatz demonstriert. Im Anhang des Berichts sind alle TGG-Regeln für die SysML-zu-AUTOSAR-Transformation dokumentiert.

In today’s world we see that Embedded Systems forms a major part in the life of a human being. Almost every device today has an electronic chip embedded in it. When it comes to automotive, these electronic devices are multiplying. This has resulted in innovative methods of developing Embedded Systems. Among them, Model Based Development has become very popular and a standard way of developing embedded systems. Now, we can see that most embedded systems, especially the automotive systems, are being developed using Model development tools like Simulink. In the design and development of Driver Assistance System, Model Based Design (MBD) plays an important role from system design and simulation to code generation. Modeling tool Matlab/Simulink is now among the most popular tools. Due to the proprietary nature of Simulink and challenges in requirement elicitation phase the industry is looking towards an open source alternative, such as Scicos. Since, most of the OEMs are still using Simulink, there is a need for interoperability between Simulink and Scicos. The present work proposes metamodels for Simulink and Scicos, and Model transformation using these Metamodels for the inter-operability. In order to develop the model transformation the metamodels for Simulink and Scicos were developed using EMF Ecore. These metamodels conform to OMGs MOF Standards. These metamodels were used in developing the transformation definition using the language QVTo. First a simple model was developed, and transformation rules were applied and verified using it. Then a Simulink subsystem of a cross wind assistance system was subjected to forward transformation. The outputs of the model before transformation and that after transformation were compared. They were found to give the same output as desired. Thus, verifying the transformation definition. An attempt was made to achieve reverse transformation. A subsystem in Scicos was considered for reverse transformation. After subjecting it to transformation, an intermediate model conforming to Simulink metamodel was obtained. This shows that the interoperability between Scicos and Simulink can be achieved.

Modern software systems have increasingly higher expectations on their reliability, in particular if the systems are critical and real-time. The development of these complex software systems requires strong modelling and analysis methods including quantitative modelling and formal verification. Unified Modelling Language (UML) is a widely used and intuitive graphical modelling language to design complex systems, while formal models provide a theoretical support to verify system design models. However, UML models are not sufficient to guarantee correct system designs and formal models, on the other hand, are often restrictive and complex to use. It is believed that a combined approach comprising the advantages of both models can offer better designs for modern complex software development needs. This thesis focuses on the design and development of a rigorous framework based on Model Driven Development (MDD) that facilitates transformations of non-formal models into formal models for design verification. This thesis defines and describes the transformation from UML2 sequence diagrams to coloured Petri nets and proves syntactic and semantic correctness of the transformation. Additionally, we explore ways of adding information (time, probability, and hierarchy) to a design and how it can be added onto extensions of a target model. Correctness results are extended in this context. The approach in this thesis is novel and significant both in how to establish semantic and syntactic correctness of transformations, and how to explore semantic variability in the target model for formal analysis. Hence, the motivation of this thesis establishes: the UML behavioural models can be validated by correct transformation of them into formal models that can be formally analysed and verified.

In this thesis, we describe how to use UML sequence diagrams with MARTE timing constraints to specify entirely the behavior of component-based systems while abstracting as much as possible the functional roles of components composing it. We have shown how to conduct compositional analysis of such specifications. For this, we have defined operational semantics to sequence diagrams by translating them into TIOSTS which are symbolic automata with timing constraints. We have used symbolic execution techniques to compute possible executions of the system in the form of a symbolic tree. We have defined projection mechanisms to extract the execution tree associated with any distinguished component. The resulting projected tree characterizes the possible behaviors of the component with respect to the context of the whole system specification. As such, it represents a constraint to be satisfied by the component and it can be used as a correctness reference to validate the system in a compositional manner. For that purpose, we have grounded our validation framework on testing techniques. We have presented compositional results relating the correctness of a system to the correctness of components. Based on these results, we have defined an incremental approach for testing from sequence diagrams.

Unlike many proprietary component systems, the academic ones do not have sufficient support in integrated development environments. This the- sis analyzes development of component-based applications in terms of the SOFA 2 component system and it finds out that the main issue is an in- sufficient connection between processes of common application design and creation of particular components. Based on this analysis, it defines a subset of the UML, a universal language for application design, and its semantics regarding entities of the SOFA 2 component system. Furthermore, it creates a tool integrated to the Eclipse IDE, which enables a developer to automat- ically generate these entities from a UML component model as well as to connect this model with already existing entities enabling their automatic correction in case of model changing. This tool is designed modularly so that it is possible to easily change semantics of the model or using it for other models. Finally, this thesis analyzes possibilities of extensions of this tool for other component systems, code generation and component behaviour verification.

Frameworks são ferramentas importantes no contexto atual da tecnologia de desenvolvimento de software, fornecendo funcionalidades através de código previamente testado, o que leva a uma redução na quantidade de código necessário para se implementar soluções e no tempo de implementação. Porém, devido a complexidade dos frameworks atuais, seu uso se torna trabalhoso, requerendo um gasto de tempo elevado para se aprender um framework novo. Neste trabalho de pesquisa foi desenvolvido o Framer, um método de transformação de modelos capaz de selecionar componentes de um framework, a partir de seu modelo UML, que são necessários para implementar as funcionalidades providas pelo framework para uma aplicação em desenvolvimento. Este método de transformação utiliza uma versão modificada do algoritmo NONLIN de planejamento, para identificar não somente os componentes que serão utilizados, mas como e em qual ordem devem ser invocados pela aplicação. Uma vez identificados os componentes, são criados os Diagramas UML necessários para representar sua utilização. / Frameworks are important tools for current software development technology, providing functionalities through previously tested code, reducing the amount of code and time necessary to implement the solution. However, due to framework complexity, a developer needs a significant investment in time to learn it. This work presents the Framer, a model transformation method capable of selecting components, from a framework\'s UML model, that will be used to construct the functionalities of the target application. Once the components are identified, the UML Diagrams necessary to describe its use are created.

La transformation de modèles est une opération fondamentale dans l'ingénierie dirigée par les modèles. Elle peut être manuelle ou automatisée, mais dans ce dernier cas elle nécessite de la part du développeur qui la conçoit la maîtrise des méta-modèles impliqués dans la transformation. La génération de transformations de modèles à partir d'exemples permet la création d'une transformation de modèle en se basant sur des exemples de modèles sources et cibles. Le fait de travailler au niveau modèle permet d'utiliser les syntaxes concrètes définies pour les méta-modèles et ne nécessite plus une maîtrise parfaite de ces derniers.Nous proposons une méthode de génération de transformations de modèles à partir d'exemples basée sur l'Analyse Relationnelle de Concepts (ARC) permettant d'obtenir un ensemble de règles de transformations ordonnées sous forme de treillis. L'ARC est une méthode de classification qui se base sur des liens de correspondances entre les modèles pour faire émerger des règles. Ces liens étant un problème commun à toute les méthodes de génération de transformation de modèles à partir d'exemples, nous proposons une méthode basée sur des méthodes d'alignement d'ontologie permettant de les générer. / Model transformation is a fundamental operation for Model Driven Engineering. It can be performed manually or automatically, but in the later cas the developper needs to master all the meta-models involved. Model Transformation generation from examples allows to create a model transformation based on source models examples and target models exemples. Working at the model level allows the use of concrete syntaxes defined for the meta-models so there is no more need for the developper to perfectly know them.We propose a method to generate model transformations from examples using Relational Concept Analysis (RCA) which provides a set of transformation rules ordered under the structure of a lattice. RCA is a classification method based on matching links between models to extract rules. Those matching are a common feature between the model transformation generation from examples methods, so we propose a method based on an ontology matching approach to generate them.

As transformações de modelos são um ponto vital para os enfoques de desenvolvimento dirigido por modelos, incluindo a MDA. No presente trabalho apresenta-se alguns dos conceitos da MDA relacionados a transformações de modelos. São vistos os conceitos de PIM, PSM, transformações, mapeamentos e marcas. Estes conceitos são analisados no contexto de três ferramentas MDA, a OptimalJ, a AndroMDA e a ArcStyler, para verificar se as ferramentas os implementam de acordo com a MDA. Também é analisado como e quais transformações e mapeamentos de modelos estão sendo implementados pelas ferramentas, através da comparação qualitativa de definições de conceitos e de exemplos do uso destes. Além de verificar os conceitos relacionados às transformações, faz-se um estudo de caso qualitativo para analisar as transformações e mapeamentos providos pelas ferramentas e como as ferramentas trabalham com eles. Mostram-se as dificuldades de se criar um modelo PIM do sistema do estudo de caso e adaptá-lo para cada uma das ferramentas. / Model transformations are a vital point for model driven development, including MDA. In the present essay we introduce some of the MDA concepts related with model transformations. We present the concept of PIM, PSM, transformations, mappings and marks. These concepts are analyzed in the context of three MDA tools, OptimalJ, AndroMDA and ArcStyler, to verify if the tools implement the concepts according to MDA. We also analyze how and which model transformations and model mappings are being implemented by the tools, through a qualitative comparison of the definition of these concepts and using some examples of their intended use. In addition to verifying the concepts related to transformations, we create a qualitative case study to analyze the model transformations and model mappings provided by the tools, and how the tools work with them. We show a few of the problems faced when creating a PIM model of the case study\'s system and the adaptations it required for each tool.

As transformações de modelos são um ponto vital para os enfoques de desenvolvimento dirigido por modelos, incluindo a MDA. No presente trabalho apresenta-se alguns dos conceitos da MDA relacionados a transformações de modelos. São vistos os conceitos de PIM, PSM, transformações, mapeamentos e marcas. Estes conceitos são analisados no contexto de três ferramentas MDA, a OptimalJ, a AndroMDA e a ArcStyler, para verificar se as ferramentas os implementam de acordo com a MDA. Também é analisado como e quais transformações e mapeamentos de modelos estão sendo implementados pelas ferramentas, através da comparação qualitativa de definições de conceitos e de exemplos do uso destes. Além de verificar os conceitos relacionados às transformações, faz-se um estudo de caso qualitativo para analisar as transformações e mapeamentos providos pelas ferramentas e como as ferramentas trabalham com eles. Mostram-se as dificuldades de se criar um modelo PIM do sistema do estudo de caso e adaptá-lo para cada uma das ferramentas. / Model transformations are a vital point for model driven development, including MDA. In the present essay we introduce some of the MDA concepts related with model transformations. We present the concept of PIM, PSM, transformations, mappings and marks. These concepts are analyzed in the context of three MDA tools, OptimalJ, AndroMDA and ArcStyler, to verify if the tools implement the concepts according to MDA. We also analyze how and which model transformations and model mappings are being implemented by the tools, through a qualitative comparison of the definition of these concepts and using some examples of their intended use. In addition to verifying the concepts related to transformations, we create a qualitative case study to analyze the model transformations and model mappings provided by the tools, and how the tools work with them. We show a few of the problems faced when creating a PIM model of the case study\'s system and the adaptations it required for each tool.