Transformations play a central role in Model Based Software Engineering. Similar to the development of other types of software, a transformation's specification and implementation does not necessarily remain static over the course of a project's lifetime; the transformation may develop incrementally and evolve. The goal of this thesis is to propose metrics that can be used to characterize the evolution of model transformations. To perform an initial demonstration of the metrics, this thesis considers an incrementally defined model transformation task. The transformation is implemented using two model transformation languages, a textual language and a graphical language, and metrics are extracted from the historical artifacts. The thesis defines a set of change metrics based on an abstract syntax difference model. Language feature metrics are also defined for both transformation languages. A process for extracting model-based change metrics and language metrics from the abstract syntax of the transformation languages is introduced. The applicability of the metrics in characterizing changes is demonstrated using exploratory clustering analysis on a transformation task. We show how, for this transformation task using both languages, metrics derived from the difference model result in clusters that reflect characteristics of individual changes, in contrast to clusters obtained with language metrics. / Thesis (Master, Computing) -- Queen's University, 2012-09-28 10:47:10.999

This thesis describes the AP1 system, which serves as a platform for model-based CASE technology. AP1 is a set of libraries and tools that support different activities in the software development process. It provides different layers of reusable CASE functionality, and thus facilitates CASE tool development and integration. Some key problems of software development are addressed, such as the storage and management of artifacts, their creation and modification, and the generation of program code. The main parts of the abstract platform are a typed repository for models and model data, and a generic editor that acts as an integrated software development environment (IDE). The former enables data integration; the latter serves as a basis for presentation integration. Both parts have an extensible and customizable architecture that makes it possible for developers to adapt the system to their own individual needs. The thesis discusses different data models, explaining why the parsimonious data model was chosen for the repository. A mapping onto the relational data model is given that makes it possible to leverage a RDBMS for data management. On top of the RDBMS, the AP1 system implements new mechanisms for caching, event notification and change control, resulting in a unique architecture. The thesis introduces novel concepts of robustness and reflection for user interfaces, and delineates their implementation in the generic editor. Furthermore, a concept for code generators is presented that offers a particularly high degree of type-safety, which we call generator type-safety.

This thesis describes the AP1 system, which serves as a platform for model-based CASE technology. AP1 is a set of libraries and tools that support different activities in the software development process. It provides different layers of reusable CASE functionality, and thus facilitates CASE tool development and integration. Some key problems of software development are addressed, such as the storage and management of artifacts, their creation and modification, and the generation of program code. The main parts of the abstract platform are a typed repository for models and model data, and a generic editor that acts as an integrated software development environment (IDE). The former enables data integration; the latter serves as a basis for presentation integration. Both parts have an extensible and customizable architecture that makes it possible for developers to adapt the system to their own individual needs. The thesis discusses different data models, explaining why the parsimonious data model was chosen for the repository. A mapping onto the relational data model is given that makes it possible to leverage a RDBMS for data management. On top of the RDBMS, the AP1 system implements new mechanisms for caching, event notification and change control, resulting in a unique architecture. The thesis introduces novel concepts of robustness and reflection for user interfaces, and delineates their implementation in the generic editor. Furthermore, a concept for code generators is presented that offers a particularly high degree of type-safety, which we call generator type-safety.

This thesis describes the AP1 system, which serves as a platform for model-based CASE technology. AP1 is a set of libraries and tools that support different activities in the software development process. It provides different layers of reusable CASE functionality, and thus facilitates CASE tool development and integration. Some key problems of software development are addressed, such as the storage and management of artifacts, their creation and modification, and the generation of program code. The main parts of the abstract platform are a typed repository for models and model data, and a generic editor that acts as an integrated software development environment (IDE). The former enables data integration; the latter serves as a basis for presentation integration. Both parts have an extensible and customizable architecture that makes it possible for developers to adapt the system to their own individual needs. The thesis discusses different data models, explaining why the parsimonious data model was chosen for the repository. A mapping onto the relational data model is given that makes it possible to leverage a RDBMS for data management. On top of the RDBMS, the AP1 system implements new mechanisms for caching, event notification and change control, resulting in a unique architecture. The thesis introduces novel concepts of robustness and reflection for user interfaces, and delineates their implementation in the generic editor. Furthermore, a concept for code generators is presented that offers a particularly high degree of type-safety, which we call generator type-safety.

This thesis describes the AP1 system, which serves as a platform for model-based CASE technology. AP1 is a set of libraries and tools that support different activities in the software development process. It provides different layers of reusable CASE functionality, and thus facilitates CASE tool development and integration. Some key problems of software development are addressed, such as the storage and management of artifacts, their creation and modification, and the generation of program code. The main parts of the abstract platform are a typed repository for models and model data, and a generic editor that acts as an integrated software development environment (IDE). The former enables data integration; the latter serves as a basis for presentation integration. Both parts have an extensible and customizable architecture that makes it possible for developers to adapt the system to their own individual needs. The thesis discusses different data models, explaining why the parsimonious data model was chosen for the repository. A mapping onto the relational data model is given that makes it possible to leverage a RDBMS for data management. On top of the RDBMS, the AP1 system implements new mechanisms for caching, event notification and change control, resulting in a unique architecture. The thesis introduces novel concepts of robustness and reflection for user interfaces, and delineates their implementation in the generic editor. Furthermore, a concept for code generators is presented that offers a particularly high degree of type-safety, which we call generator type-safety.

No description available.

Melhoria de processo de software (SPI) é uma prática de engenharia de software motivada pela necessidade de aumentar a qualidade e a produtividade no desenvolvimento de software. Um fato amplamente reconhecido é que a qualidade do produto de software pode ser, em grande parte, determinada pela qualidade do processo utilizado para desenvolvê-lo e mantê-lo. A avaliação do processo de software ajuda as organizações de software a amadurecerem seus processos, identificando problemas críticos para estabelecer prioridades de melhoria. Essa avaliação pode ser feita por meio da comparação do estado dos processos da organização em relação a um modelo de referência que estabeleça estágios de melhoria. Uma avaliação geralmente se baseia em um modelo de processo de software que fornece um roteiro para melhorias. Este trabalho tem como objetivo estabelecer uma abordagem que: (i) define um conjunto de modelos de abstração (metamodelos) de modelos de maturidade de processo de software para apoiar uma metodologia de avaliação/melhoria de processo de software com o objetivo de certificação; e (ii) permite avaliar os processos de uma organização em comparação com um modelo de maturidade por meio de transformações desses metamodelos. A abordagem é instanciada por meio de um estudo de caso utilizando os modelos MPS.Br e CMMI para exemplificar sua aplicação. Como resultado, é apresentado um comparativo entre as limitações encontradas nas metodologias encontradas na literatura e como a abordagem sugere superá-las. / Software process improvement (SPI) is a software engineering practice motivated by the need to increase the quality and productivity in software development. A fact widely recognized is that the quality of the software product can be largely determined by the quality of the process used to develop and maintain it. The assessment of software process helps software organizations to improve themselves, identifying their critical problems to establish priorities for improvement. This assessment can take place by comparing the state of the organization on their software processes to a reference model that shows stages of improvement in scales. An assessment is usually based on a software process model that provides a roadmap for improvement. This work aims to establish an approach that: (i) defines a set of abstraction models (metamodels) of software process maturity models to support an assessment/improvement methodology aiming software process certification; and (ii) evaluates the organization processes in comparison with the maturity models through transformations of those metamodels. The approach is instantiated through a case study using the MPS.Br and CMMI models to illustrate its application. As a result, a comparison between the limitations found in the methodologies identified in the literature and how the approach suggested overcome them is presented.

Melhoria de processo de software (SPI) é uma prática de engenharia de software motivada pela necessidade de aumentar a qualidade e a produtividade no desenvolvimento de software. Um fato amplamente reconhecido é que a qualidade do produto de software pode ser, em grande parte, determinada pela qualidade do processo utilizado para desenvolvê-lo e mantê-lo. A avaliação do processo de software ajuda as organizações de software a amadurecerem seus processos, identificando problemas críticos para estabelecer prioridades de melhoria. Essa avaliação pode ser feita por meio da comparação do estado dos processos da organização em relação a um modelo de referência que estabeleça estágios de melhoria. Uma avaliação geralmente se baseia em um modelo de processo de software que fornece um roteiro para melhorias. Este trabalho tem como objetivo estabelecer uma abordagem que: (i) define um conjunto de modelos de abstração (metamodelos) de modelos de maturidade de processo de software para apoiar uma metodologia de avaliação/melhoria de processo de software com o objetivo de certificação; e (ii) permite avaliar os processos de uma organização em comparação com um modelo de maturidade por meio de transformações desses metamodelos. A abordagem é instanciada por meio de um estudo de caso utilizando os modelos MPS.Br e CMMI para exemplificar sua aplicação. Como resultado, é apresentado um comparativo entre as limitações encontradas nas metodologias encontradas na literatura e como a abordagem sugere superá-las. / Software process improvement (SPI) is a software engineering practice motivated by the need to increase the quality and productivity in software development. A fact widely recognized is that the quality of the software product can be largely determined by the quality of the process used to develop and maintain it. The assessment of software process helps software organizations to improve themselves, identifying their critical problems to establish priorities for improvement. This assessment can take place by comparing the state of the organization on their software processes to a reference model that shows stages of improvement in scales. An assessment is usually based on a software process model that provides a roadmap for improvement. This work aims to establish an approach that: (i) defines a set of abstraction models (metamodels) of software process maturity models to support an assessment/improvement methodology aiming software process certification; and (ii) evaluates the organization processes in comparison with the maturity models through transformations of those metamodels. The approach is instantiated through a case study using the MPS.Br and CMMI models to illustrate its application. As a result, a comparison between the limitations found in the methodologies identified in the literature and how the approach suggested overcome them is presented.

Tesis por compendio / [ES] Hoy en día, el software existe en casi todo. Las empresas a menudo desarrollan y mantienen colecciones de sistemas de software personalizados que comparten algunas características entre ellos, pero que también tienen otras características particulares. Conforme el número de características y el número de variantes de un producto crece, el mantenimiento del software se vuelve cada vez más complejo. Para hacer frente a esta situación la Comunidad de Ingeniería del Software basada en Modelos está abordando una actividad clave: la Localización de Fragmentos de Modelo. Esta actividad consiste en la identificación de elementos del modelo que son relevantes para un requisito, una característica o un bug. Durante los últimos años se han propuesto muchos enfoques para abordar la identificación de los elementos del modelo que corresponden a una funcionalidad en particular. Sin embargo, existe una carencia a la hora de cómo se reportan las medidas del espacio de búsqueda, así como las medidas de la solución a encontrar. El objetivo de nuestra tesis radica en proporcionar a la comunidad dedicada a la actividad de localización de fragmentos de modelo una serie de medidas (tamaño, volumen, densidad, multiplicidad y dispersión) para reportar los problemas de localización de fragmentos de modelo. El uso de estas novedosas medidas ayuda a los investigadores durante la creación de nuevos enfoques, así como la mejora de aquellos enfoques ya existentes. Mediante el uso de dos casos de estudio reales e industriales, esta tesis pone en valor la importancia de estas medidas para comparar resultados de diferentes enfoques de una manera precisa. Los resultados de este trabajo han sido redactados y publicados en foros, conferencias y revistas especializadas en los temas y contexto de la investigación. Esta tesis se presenta como un compendio de artículos acorde a la regulación de la Universitat Politècnica de València. Este documento de tesis presenta los temas, el contexto y los objetivos de la investigación. Presenta las publicaciones académicas que se han publicado como resultado del trabajo y luego analiza los resultados de la investigación. / [CA] Hui en dia, el programari existix en quasi tot. Les empreses sovint desenrotllen i mantenen col·leccions de sistemes de programari personalitzats que compartixen algunes característiques entre ells, però que també tenen altres característiques particulars. Conforme el nombre de característiques i el nombre de variants d'un producte creix, el manteniment del programari es torna cada vegada més complex. Per a fer front a esta situació la Comunitat d'Enginyeria del Programari basada en Models està abordant una activitat clau: la Localització de Fragments de Model. Esta activitat consistix en la identificació d'elements del model que són rellevants per a un requisit, una característica o un bug. Durant els últims anys s'han proposat molts enfocaments per a abordar la identificació dels elements del model que corresponen a una funcionalitat en particular. No obstant això, hi ha una carència a l'hora de com es reporten les mesures de l'espai de busca, així com les mesures de la solució a trobar. L'objectiu de la nostra tesi radica a proporcionar a la comunitat dedicada a l'activitat de localització de fragments de model una sèrie de mesures (grandària, volum, densitat, multiplicitat i dispersió) per a reportar els problemes de localització de fragments de model. L'ús d'estes noves mesures ajuda als investigadors durant la creació de nous enfocaments, així com la millora d'aquells enfocaments ja existents. Per mitjà de l'ús de dos casos d'estudi reals i industrials, esta tesi posa en valor la importància d'estes mesures per a comparar resultats de diferents enfocaments d'una manera precisa. Els resultats d'este treball han sigut redactats i publicats en fòrums, conferències i revistes especialitzades en els temes i context de la investigació. Esta tesi es presenta com un compendi d'articles d'acord amb la regulació de la Universitat Politècnica de València. Este document de tesi presenta els temes, el context i els objectius de la investigació. Presenta les publicacions acadèmiques que s'han publicat com resultat del treball i després analitza els resultats de la investigació. / [EN] Nowadays, software exists in almost everything. Companies often develop and maintain a collection of custom-tailored software systems that share some common features but also support customer-specific ones. As the number of features and the number of product variants grows, software maintenance is becoming more and more complex. To keep pace with this situation, Model-Based Software Engineering Community is addressing a key-activity: Model Fragment Location (MFL). MFL aims at identifying model elements that are relevant to a requirement, feature, or bug. Many MFL approaches have been introduced in the last few years to address the identification of the model elements that correspond to a specific functionality. However, there is a lack of detail when the measurements about the search space (models) and the measurements about the solution to be found (model fragment) are reported. The goal of this thesis is to provide insights to MFL Research Community of how to improve the report of location problems. We propose using five measurements (size, volume, density, multiplicity, and dispersion) to report the location problems during MFL. The usage of these novel measurements support researchers during the creation of new MFL approaches and during the improvement of those existing ones. Using two different case studies, both real and industrial, we emphasize the importance of these measurements in order to compare results in a deeply way. The results of the research have been redacted and published in forums, conferences, and journals specialized in the topics and context of the research. This thesis is presented as compendium of articles according the regulations in Universitat Politècnica de València. This thesis document introduces the topics, context, and objectives of the research, presents the academic publications that have been published as a result of the work, and then discusses the outcomes of the investigation. / Ballarin Naya, M. (2021). Definition of Descriptive and Diagnostic Measurements for Model Fragment Retrieval [Tesis doctoral]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/171604 / Compendio