In today’s fast paced changing technology world, it is essential to adapt the new technologies and standards in order to stay compliant with the market. Software development is one of those key areas that have been growing highly fast and thus the need for staying up to date needs to be acknowledged by everyone in the area. The technology focused in this project is called ModelicaML[1] which is an integrated system modeling environment based on standardized languages such as UML[2] and Modelica[3]. Modelica Modeling Language (ModelicaML) is a graphical modeling language used for the description of time-continuous and time-discrete/event-based system dynamics. Currently, a ModelicaML code generator – that generates Modelica code from UML models – is implemented using the old Acceleo framework[4]. Within this thesis, the ModelicaML code generator was re-factored and implemented by using the latest Acceleo version 3.X[5]. The differences between the old and new Acceleo framework was also given an evaluation in the study in order to provide a hint of its future use for further improvements of the code generator.

Made available in DSpace on 2014-12-17T15:47:59Z (GMT). No. of bitstreams: 1 KeivilanyJLC_DISSERT.pdf: 3136956 bytes, checksum: 58f2931b21ff1ab0cd5e4e065e0d1aa4 (MD5) Previous issue date: 2012-02-06 / Conselho Nacional de Desenvolvimento Cient?fico e Tecnol?gico / The tracking between models of the requirements and architecture activities is a strategy that aims to prevent loss of information, reducing the gap between these two initial activities of the software life cycle. In the context of Software Product Lines (SPL), it is important to have this support, which allows the correspondence between this two activities, with management of variability. In order to address this issue, this paper presents a process of bidirectional mapping, defining transformation rules between elements of a goaloriented requirements model (described in PL-AOVgraph) and elements of an architectural description (defined in PL-AspectualACME). These mapping rules are evaluated using a case study: the GingaForAll LPS. To automate this transformation, we developed the MaRiPLA tool (Mapping Requirements to Product Line Architecture), through MDD techniques (Modeldriven Development), including Atlas Transformation Language (ATL) with specification of Ecore metamodels jointly with Xtext , a DSL definition framework, and Acceleo, a code generation tool, in Eclipse environment. Finally, the generated models are evaluated based on quality attributes such as variability, derivability, reusability, correctness, traceability, completeness, evolvability and maintainability, extracted from the CAF? Quality Model / O rastreamento entre modelos das atividades de requisitos e arquitetura ? uma estrat?gia que busca evitar a perda de informa??es, reduzindo o gap entre essas duas atividades iniciais do ciclo de vida do software. No contexto das Linhas de Produto de Software (LPS), ? importante que haja um suporte a esse rastreamento, que permita a correspond?ncia entre as duas atividades, com um gerenciamento satisfat?rio das variabilidades. Buscando atender a essa quest?o, este trabalho apresenta um processo de mapeamento bi-direcional, definindo regras de transforma??o entre elementos de modelo de requisitos orientado a objetivos (descrito em PL-AOVgraph) e elementos de descri??o arquitetural (definida em PL-AspectualACME). Essas regras de mapeamento s?o avaliadas em um estudo de caso: a LPS Ginga ForAll. Para automatizar essa transforma??o, implementamos a ferramenta MaRiPLA (Mapping Requirements to Product Line Architecture), atrav?s de t?cnicas do desenvolvimento dirigido a modelos (Model-driven Development MDD), incluindo a linguagem de transforma??es entre modelos Atlas Transformation Language (ATL) com especifica??o de metamodelos do tipo Ecore em conjunto com os frameworks Xtext, de defini??o DSL, e Acceleo, de gera??o de c?digo, em ambiente Eclipse. Por fim, os modelos gerados s?o avaliados, com base em atributos de qualidade como variabilidade, derivabilidade, reusabilidade, corretude, rastreabilidade, completude, evolutibilidade e manutenibilidade, extra?dos do Modelo de Qualidade CAF?