Tesis sobre el tema "MDD (Model-Driven Development)"

Test Driven Development (TDD), Model-Driven Development (MDD), and Test Case Generation with their associated practices and tools each in their own right promise to deliver robust higher quality code more economically then other approaches. These process are not mutually exclusive but are not typically used together. This thesis develops a combined approach using complimentary aspects of each of the above three process. Test cases are described, generated, and then injected back into the model, which is then used to produce the test and production code. We have enhanced a model-driven tool to support the approach, adding a test case generator, capable of understanding augmented MDD software model and utilizing the constraints captured in our test-centric language to generate model-level test cases back into the model. Our results show that, with a reduction in overall effort one can produce a tested model-based system in which its test and implementation for multiple platforms such as C and Java, using one of multiple test xUnit frameworks.

O surgimento e o uso crescente de novas tecnologias têm levado à produção e armazenamento de grandes volumes de dados biomédicos. Tais dados são provenientes de diferentes técnicas, armazenados em formatos de representação diversos e utilizados por diferentes ferramentas. Esta heterogeneidade representa um empecilho ao maior uso desses dados em abordagens integrativas de pesquisa como, por exemplo, a biologia sistêmica. Neste cenário, artefatos de modelagem conceitual, tais como ontologias, têm sido utilizados para organizar e integrar dados heterogêneos de uma forma coerente. A OBO Foundry representa, atualmente, o maior esforço no desenvolvimento de ontologias biomédicas de forma colaborativa. Dentre as ontologias desenvolvidas pela OBO Foundry, destaca-se Ontologia de Relacionamentos (RO-OBO). A RO-OBO provê definições formais para um conjunto de relacionamentos de propósito geral utilizados nas ontologias biomédicas e busca promover a criação de ontologias mais corretas e integráveis. Um perfil UML foi proposto para representar formalmente o conjunto de conceitos e relacionamentos existentes na RO-OBO. Este perfil permite desenvolver modelos UML utilizando os conceitos presentes nesta ontologia, bem como torna possível o desenvolvimento de suporte à validação sintática dos modelos criados em relação a um conjunto de restrições formalmente definidas. Adicionalmente, percebe-se na literatura que o suporte à integração de modelos UML e ontologias OBO, em particular as ontologias representadas na linguagem OBO File Format, é limitado. Neste sentido, este trabalho teve como objetivo geral investigar o suporte ao desenvolvimento de ontologias biomédicas na linguagem UML. De forma específica, investigou-se o desenvolvimento de um editor gráfico, chamado OBO-RO Editor, para o suporte à construção de ontologias utilizando o perfil UML proposto, bem como a integração de ontologias desenvolvidas utilizando UML e ontologias desenvolvidas na linguagem OBO File Format. De forma a atingir nossos objetivos, uma arquitetura de referência foi definida e um processo de desenvolvimento orientado a modelos foi utilizado. A arquitetura definida é composta por uma série de artefatos inter-relacionados os quais são transformados (semi) automaticamente em código de aplicação, possibilitando a obtenção de ciclos de desenvolvimento mais rápidos e confiáveis. O OBO-RO Editor disponibiliza um conjunto de elementos gráficos de modelagem definidos a partir do perfil UML proposto, bem como provê mecanismos para a validação sintática (semi) automática de uma ontologia desenvolvida segundo as restrições definidas neste perfil. Adicionalmente, o OBO-RO Editor também provê suporte à integração de modelos UML a outras ontologias da OBO Foundry, permitindo o reuso e o desenvolvimento menos propenso a erros de ontologias no domínio biomédico.
The development and increasing use of new technologies has resulted in the production and storage of a huge amount of biomedical data. These data are produced using different techniques, stored in different formats and consumed by different (software) tools. This heterogeneity hinders effective data usage in integrative research approaches, including systems biology. In this scenario, conceptual modeling artifacts, such as ontologies, have been used to organize and integrate heterogeneous data in a coherent manner. Nowadays, the OBO Foundry represents the most important effort for the collaborative development of ontologies in the biomedical domain. The OBO Relation Ontology (OBO-RO) can be considered one of the most relevant ontologies in the domain. This ontology provides formal definitions for a number of general purpose relationships used in biomedical ontologies, thus facilitating the integration of existing ontologies and the development of new ontologies in the domain. An UML profile has been proposed to formally define the different types of concepts and relationships provided by the OBO-RO. This profile enables the creation of UML models using such concepts and allows the development of support for the automatic validation of these models based on formal constraints. Additionally, the support for the integration between UML models and OBO ontologies, particularly ontologies represented using the OBO File Format, is limited. In this sense, this project aimed at investigating the support for the development of biomedical ontologies using UML. In particular, we investigated the development of a graphical editor, named OBO-RO Editor, to support ontology development using the proposed UML profile. Additionally, we also investigated the integration of ontologies developed using UML and ontologies developed using the OBO File Format. In order to achieve our goals, we have defined a reference architecture and a model-driven development process. The reference architecture consists of a number of related artifacts that are transformed to application code (semi) automatically. Such characteristic allowed us to obtain faster and more reliable development cycles. The OBO-RO Editor provides a number of graphical elements defined in the proposed UML profile for the modeling of biomedical ontologies and support the (semi) automatic syntactic validation of such ontologies against the contraints defined in the profile. Additionally, OBO-RO Editor also provides support for the integration of developed UML models and other OBO ontologies, allowing the reuse and the accurate development of biomedical ontologies.

Este trabalho tem por objetivo propor a utilização de soluções pré-definidas e comprovadas na abordagem MDA, auxiliando o desenvolvedor na resolução de problemas recorrentes ao desenvolvimento de software. A utilização destas soluções pré-definidas leva a um aumento de produtividade no contexto MDA e na geração de software baseado em boas práticas. Para que este objetivo seja cumprido, é empreendida uma análise sobre o MDA e sobre como operacionalizar as transformações entre modelos. Também é empreendida uma análise sobre o suporte fornecido pela UML e sobre reutilização em desenvolvimento orientado a modelos. Por fim este trabalho apresenta partes de uma aplicação protótipo, construída para ser uma prova de conceito de código gerado através da combinação de UML e soluções pré-definidas.
The goal of this work is to propose the use of pre-defined solutions on MDA approach, supporting the developer in solving recurrent problems of software development. The use of these pre-defined solutions leads to an increase of productivity in MDA context, and in the generation of software based on best practices. To reach this goal, an analysis of MDA is undertaken, as well as an analysis of how to enable the transformations between models. It is also undertaken an analysis about the use of UML and the reuse in model driven development. Finally this work presents portions of a prototype application, constructed to be a proof-of-concept of generated code, combining UML and the pre-defined solutions.

The use of models for designing and developing Information Systems (IS) has changed in recent years. Models are no longer considered a peripheral documentation medium that is poorly maintained and often neglected. Rather, models are increasingly seen as essential parts of the final product—as central artifacts that drive and guide the development efforts. The knowledge that modelers rely on when designing models is represented as formal models and clearly defined rules for transforming the models. The flexibility, reliability, and effectiveness offered by the formal models and the transformations are making Model Driven Development (MDD) a popular choice for building IS. Models also serve in describing enterprise design, where enterprise-level models capture organizational knowledge and aid in understanding, improving, and growing the enterprise. Enterprise Modeling (EM) offers a structured and unified view of the enterprise, thereby enabling more informed and accurate decisions to be made. Many MDD approaches have been proposed to tackle a wide range of IS-related issues, but little attention is being paid to the source of the knowledge captured by the IS models. EM approaches capture organizational knowledge and provide the necessary input and underlying context for designing IS. However, the results produced by EM approaches need to be manually analyzed by modelers to create the initial MDD model. This interruption of the MDD process represents a gap between enterprise models and MDD models. Limited research has been done to connect EM to MDD in a systematic and structured manner based on the principles of model-driven development. This thesis proposes a unifying meta-model for integrating EM and MDD. The meta-model captures the inherent links that exist between organizational knowledge and IS design. This helps to improve the alignment between organizational goals and the IS that are created to support them. The research presented herein follows the guidelines of the design science research methodology. It starts with a state-of-the-art survey of the current relationship between MDD and prior stages of development. The findings of the survey are used to elicit a set of necessary properties for integrating EM and MDD. The unifying meta-model is then proposed as the basis for an integrated IS development approach that applies the principles of MDD and starts on the enterprise level by considering enterprise models in the development process. The design of the meta-model supports the elicited integration properties. The unifying meta-model is based on the Enterprise Knowledge Development (EKD) approach to EM. A prototype tool is developed to support the unifying meta-model, following a study to choose a suitable implementation environment. The use of the unifying meta-model is demonstrated through the implemented tool platform using an example case study, revealing its advantages and highlighting the potential for improvement and future development.

Submitted by Irene Nascimento (irene.kessia@ufpe.br) on 2016-08-22T18:54:13Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) DissertacaoCD_LuizFelipeLiborio.pdf: 3777707 bytes, checksum: a7937e9fc359d5b560c37ea3abf5e74c (MD5)
Made available in DSpace on 2016-08-22T18:54:13Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) DissertacaoCD_LuizFelipeLiborio.pdf: 3777707 bytes, checksum: a7937e9fc359d5b560c37ea3abf5e74c (MD5) Previous issue date: 2014-08-27
Capes
Atualmente, é cada vez mais exigido como critério competitivo a aderência do processo de software de uma organização a um modelo ou norma de qualidade. Alcançar altos níveis de aderência é uma tarefa complexa para as organizações, pois a atividade de avaliar essa aderência exige cuidado ao ser realizada. Com isso, busca-se cada vez mais o apoio de ferramentas de avaliação computadorizadas, cujo objetivo é agilizar e tornar mais confiável o processo de avaliação dos processos de software. Ainda assim, um dos fatores que tendem a dificultar a utilização e propagação do uso de ferramentas é a atualização das normas de qualidade e dos métodos de avaliação associados, que visam se adequar constantemente às boas práticas do mercado. Ora, se uma ferramenta é criada baseada na norma de qualidade e no seu método de avaliação, qualquer mudança em algum dos dois componentes significa mudanças na ferramenta, gerando custos de manutenção e de distribuição da nova versão da ferramenta. Este trabalho busca criar uma engine de geração que seja sensível a esses mudanças, sem que seu processo de desenvolvimento necessite ser executado novamente. Para isto, utiliza o processo MDD (Model-Driven Development) para atender a esses requisitos, dado que o seu objetivo é transformar elementos mais abstratos em elementos mais concretos utilizando uma sucessão de transformações, através de modelos. O objetivo deste trabalho é, então, aplicar as regras de MDD aos modelos de qualidade e métodos de avaliação. Isto torna possível a criação de ferramentas para avaliação baseada nos modelos necessários à avaliação. Ou seja, através de um modelo de processo e de um metamodelo da norma de qualidade, além do método de avaliação, é possível criar de forma automática via MDD uma ferramenta que possa ser atualizada sob demanda, sem que seu código-fonte precise ser alterado manualmente.
Nowadays, it is increasingly required as a competitive criteria the adherence of an organization to a software model or quality standard process. Achieving high levels of adherence is a complex task for organizations, because the activity of evaluating this adherence requires care to be performed. Thus, it is increasing the nedd of computerized evaluation tools whose goal is to speed up and make more reliable the process of evaluating software processes.Still, one of the factors that tend to hamper the use and propagation of tool use is the change of the quality standards and assessment methods, which aim to adapt constantly to best practices in the market. So, if a tool is created based on quality standard and its evaluation method, any change in any of the two components mean changes in the tool, generating costs of maintaining and distributing the new version of the tool. This work seeks to develop a tool that is sensitive to that changes, but without the need of performing its development process again. For that, it uses MDD (Model- Driven Development) processes meet these requirements, since their goal is to transform more abstract elements into more concrete elements using a succession of transformations, through models. So, the goal of this work is to apply the rules of MDD to quality models and assessment methods. It makes possible to create tools based on models. In other words, through a process model and a metamodel quality standard, besides the evaluation method, it is possible to create automatically via MDD a tool that can be updated on demand, without its source code need to be changed manually.

Made available in DSpace on 2014-06-12T15:50:30Z (GMT). No. of bitstreams: 2 arquivo1972_1.pdf: 2696080 bytes, checksum: 69e35c3af53ec4eeb4876270ddb417ad (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2008
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior
No mundo globalizado e competitivo, a sobrevivência de uma organização está relacionada a atrair e, principalmente, manter clientes (consumidores) através da prestação de serviços de qualidade. Atualmente, a forma mais usual de comunicação direta entre as organizações e seus (possíveis) clientes é através de aplicações baseadas na Web. Entre as vantagens deste tipo de aplicação estão a disponibilidade em tempo integral (24/7/365) e a facilidade de acesso, tendo em vista que o requisito inicial é apenas um computador com acesso à Internet. No contexto da disciplina de Engenharia de Software, as aplicações Web possuem características específicas que as diferem de aplicações tradicionais, especialmente no que se refere à interação com os usuários, e que devem ser consideradas adequadamente no processo de desenvolvimento. Entretanto, os processos de software tradicionais são dirigidos à funcionalidade e a parte do sistema responsável pela interação com os usuários é tratada com menor ênfase usualmente apenas na etapa de Implementação, ocasionando deficiências no produto e insatisfação dos usuários quanto ao uso do sistema. Neste cenário, este trabalho apresenta o método WE4UIV (Web Engineering User Interaction View), dirigido a modelos e baseado em componentes, cujo propósito é tratar os aspectos relacionados à visão de interação com os usuários de aplicações Web, nos níveis de análise e projeto, de modo a fornecer subsídios para orientar a etapa de Implementação. Além disso, visando acelerar e tornar menos manual a etapa de Implementação, este trabalho também apresenta uma ferramenta integrada a um ambiente de desenvolvimento para geração de código fonte a partir de artefatos de projeto descritos em UML. A abordagem apresentada neste trabalho pressupõe melhorias quantitativas no processo de desenvolvimento da visão de interação com os usuários, especificamente redução do tempo da etapa de Implementação e do índice de trabalho adicional causado por solicitações de mudança. A abordagem proposta é validada através de um processo de experimentação no contexto de um projeto real de desenvolvimento de software

Submitted by Alison Vanceto (alison-vanceto@hotmail.com) on 2017-02-07T10:21:15Z No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5)
Approved for entry into archive by Camila Passos (camilapassos@ufscar.br) on 2017-02-08T12:04:07Z (GMT) No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5)
Approved for entry into archive by Camila Passos (camilapassos@ufscar.br) on 2017-02-08T12:08:22Z (GMT) No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5)
Made available in DSpace on 2017-02-08T12:09:45Z (GMT). No. of bitstreams: 1 DissBFA.pdf: 12687971 bytes, checksum: 19789fb95e5c01987f5067e083d04248 (MD5) Previous issue date: 2016-03-08
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)
Model-Driven Development (MDD) is proposed to reduce the semantic gap between problem and solution/implementation domains. Some tools are used, and the code generator is commonly used in this context. These generators are often implemented using templates. A Reference Implementation (RI) favoring the development/ maintenance of software facilitates this implementation’s types. However, RI requires a code migration process which consists in artifacts’ synchronization, and it is responsible for 20% to 25% of the time spent on development. The literature has no describe automatic solutions, but the group that this reaserch was included has develop tools that automate this process and reduce the time spent on some tasks. But each task has a different performance in relation to time spent, so automation of some tasks can be disadvantageous. Few reports describe such tasks and which ones are capable of automatic code migration. The aim of this study is to investigate the maintain and evolution process to identify and describe the types of maintain and evolution tasks that are essentially. Based on this study, a method (MME-MDD) that drives the developer during that proccess to guide the developer during the realization of each task, with the aim to maximize the benefits of this approach. The MME-MDD was validated by a case study and a empirical study and the method showed effective in most of tasks. In addition, studies show that using the proposed method brought a gain in the quality of the source code.
O MDD (Model-Driven Development) tem como proposta a redução da distância semântica entre os domínios problema e solução/implementação. Para isso, são utilizadas algumas ferramentas, sendo o gerador de código comumente usado neste contexto. Os geradores de código são frequentemente implementados com a utilização de templates. Para facilitar este tipo de implementação, usualmente é empregado uma Implementação de Referência (IR), favorecendo a evolução/ manutenção do software. Contudo, a IR traz a necessidade do processo de migração de código, que consiste na sincronização entre o seu código-fonte e os templates, sendo que este é responsável por 20 a 25% do tempo gasto no desenvolvimento. Na literatura não há relatos de solução automatizada, mas o grupo no qual esta pesquisa se insere vem desenvolvendo ferramentas que automatizam este processo e reduzem o tempo aplicado em algumas tarefas testadas. Porém, cada tarefa tem um desempenho diferente em relação ao tempo gasto e, portanto, a automação de algumas tarefas pode ser desvantajosa. Existem poucos relatos na literatura descrevendo tais tarefas e quais são os passos necessários para realizá-las. O objetivo deste estudo foi a investigação do processo de manutenção e evolução de sistemas baseados em MDD com a finalidade de identificar e descrever os tipos de tarefas de manutenção e evolução. Com base nesse estudo, foi elaborado o método MMEMDD que conduz o desenvolvedor durante o processo de manutenção e evolução de sistemas, visando guiar o desenvolvedor durante a realização de cada um dos tipos de tarefas, com o intuito de maximizar os benefícios da utilização dessa abordagem. O método foi validado por meio de um estudo de caso e um estudo experimental, sendo que o método se mostrou efetivo em grande parte das tarefas testadas. Além disso, os estudos apontaram que a utilização do método proposto trouxe ganho na qualidade do código-fonte.

O desenvolvimento orientado a modelos (Model Driven Development - MDD) é uma abordagem que tem ganhado cada vez mais espaço na indústria e na academia, trazendo grandes benefícios, como o aumento de produtividade. Uma forma de se trabalhar usando MDD em equipe é usando uma IDE (Integrated Development Environment) associada a um sistema de versionamento. Entretanto, trabalhar colaborativamente usando uma IDE associada a um sistema de versionamento pode trazer algumas complicações para o desenvolvimento como: conflitos de modelos, documentação descontinuada, dificuldades por parte dos interessados em usar sistemas de versionamento, etc. Nesse contexto, este trabalho propõe uma abordagem de uso de wiki para desenvolvimento de MDD, de modo que o desenvolvedor seja capaz de criar modelos, gerar código fonte, compartilhar e versionar os modelos e ainda documentar colaborativamente, de maneira mais simples e fácil do que abordagens tradicionais. Isso possibilita que mais usuários não desenvolvedores possam participar mais no processo de desenvolvimento e ainda permite o aumento de produtividade. Para tentar evidenciar de que é possível uma wiki ser usada para desenvolver software, foi criada uma Domain Specific Language - DSL em uma wiki e foram realizados três estudos de caso: um com estudantes do ensino médio e que representam os não desenvolvedores, um com quatro alunos de pós-graduação com experiência de desenvolvimento na indústria e o último estudo de caso foi realizado com 48 participantes entre desenvolvedores e alunos de pósgraduação em Ciências da Computação. Os estudos de caso mostraram que é viável usar uma wiki para desenvolvimento, que não desenvolvedores se adaptam bem à abordagem e que 86% dos desenvolvedores usariam a abordagem proposta se tivessem que trabalhar com MDD. Os estudos de caso também levantaram as principais barreiras para aumentar a aceitação da abordagem. Com isso, este trabalho apresenta além de uma abordagem relativamente inédita na literatura, resultados sobre uso de sistemas de versionamento, de IDEs e de desenvolvimento colaborativo
The Model Driven Development (MDD) is an approach that has gained more space in industry and academia, bringing great benefits such as increased productivity. One way of working in teams with MDD is using an IDE (Integrated Development Environment) with a versioning system. However, to collaboratively work with an IDE and a versioning system may have implications and problems for the development as: conflicts of models, documentation discontinued, difficulties for stakeholders to use versioning systems, etc. In this context, this work proposes an approach to use a wiki to develop MDD, so that the developer is able to create models, generate source code, sharing and versioning models and also to collaboratively document, in a more simple and easy way than the traditional approaches. This enables non developers can participate more in the development process and also allows increasing productivity. To try to show that a wiki can be used to develop software, we created a Domain Specific Language (DSL) in a wiki and were performed three case studies: one with high school students and represent the non developers, another one with four graduate students with experience in software development in the industry, and the last case study was conducted with 48 participants among developers and graduate students in Computer Science. The case studies showed the feasibility of using a wiki for development, that non developers adapted well to the approach and 86 % of the developers would use a wiki to develop MDD. The study also raised the main barriers to increase the acceptance of the approach. Therefore, this work presents also a relatively new approach in the literature and results on the use of versioning systems, IDEs and collaboratively development

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-02-13T15:18:50Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) [dsc] Edson Alves v.1.5.6.pdf: 4201919 bytes, checksum: c682b493376c27a9896e5215c62283a1 (MD5)
Made available in DSpace on 2017-02-13T15:18:50Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) [dsc] Edson Alves v.1.5.6.pdf: 4201919 bytes, checksum: c682b493376c27a9896e5215c62283a1 (MD5) Previous issue date: 2015-03-02
CNPq
Model Driven Development (MDD) é um paradigma para geração automática de código executável que utiliza modelos como o seu artefato primário. No escopo de Banco de Dados, apesar das regras para transformação de esquemas Enhanced Entity Relationship (EER) em código da Structured Query Language (SQL)-Relacional já terem sido amplamente exploradas na literatura, não se encontrou um trabalho que ao mesmo tempo especifique tradutores MDD capazes de transformar, automaticamente, esquemas EER em códigos SQL-Relacional e aborde restrições como: Participação em Relacionamento, Disjunção e Completude em Herança ou Categoria são transformadas em estruturas SQL-Relacional. Neste contexto, visando dar uma contribuição às limitações mencionadas, esta dissertação apresenta duas macros contribuições: 1) um Catálogo de regras para transformar um esquema EER em um esquema Relacional e este em código SQL; e 2) um algoritmo que especifica uma ordem correta para a execução automática destas regras. De modo a mostrar a viabilidade e aplicação prática deste trabalho, o Catálogo de regras de transformação e o algoritmo para automatização do Catálogo são codificados na linguagem Query/View/Transformation-Relations (QVT-R) e implementados na ferramenta EERCASE. A avaliação do trabalho foi feita a partir da transformação de esquemas EER (não triviais) em códigos SQLRelacional, os quais são conferidos por especialistas de Banco de Dados. Por fim, comparando o trabalho proposto com os trabalhos relacionados investigados, constatou-se que o trabalho desta dissertação avança o estado da arte, pois é o único que é baseado em MDD e garante que as restrições de Participação em Relacionamento, Disjunção e Completude em Herança ou Categoria sejam automaticamente geradas para serem garantidas diretamente pelo Sistema de Gerenciamento de Banco de Dados.
Model Driven Development (MDD) is a paradigm for automatic generation of executable code that uses models as its primary artifact. In the database scope, despite the rules for transformation of Enhanced Entity Relationship (EER) schemas in code of Structured Query Language (SQL)-Relational have already been widely explored in the literature, we did not find a work that, at the same time, specifies MDD translators capable of transforming, automatically, EER schemas in SQL-Relational codes and addresses restrictions such as: Participation in Relationship, Disjunction and Completeness in Inheritance or Category are transformed into SQL-relational structures. In this context, in order to contribute for the mentioned limitations, this dissertation presents two macro contributions: 1) a rule Catalog to transform an EER schema into a Relational schema and this SQL code; and 2) an algorithm that specifies a correct order for the automatic enforcement of these rules. In order to show the feasibility and practical application of this work, the Catalog of transformation rules and the algorithm for Catalog automation are encoded in Query/View/TransformationRelations (QVT-R) language and implemented in EERCASE tool. The evaluation of the work was made from the processing of EER schemas (nontrivial) in SQL-Relational codes, which are conferred by database experts. Finally, comparing the proposed work with the related work investigated, it was found that the proposed work advances the state of the art, as it is the only one that is based on MDD and ensures that the restrictions on Participation in Relationship, Disjunction in Inheritance and Completeness in Inheritance or Category are guaranteed by the Database Management System.

Esta tese apresenta um processo para a criação de um catálogo de modelos de computação para apoiar o design de DSMLs, e a primeira versão do catálogo, com atributos que ajudam a selecionar os modelos de computação mais adequados para cada desenvolvimento de DSML, e as características dos sistemas de software para os quais esses modelos de computação são mais adequados. O contexto de aplicação desse catálogo é o Model-Driven Development (MDD desenvolvimento dirigido por modelos) a abordagem em que o desenvolvimento de software é baseado em modelos gráficos que são posteriormente traduzidos (transformados) em modelos de nível mais baixo e, no final, em código de linguagens de programação, tais como Java ou C#. A aplicação do processo gerou uma versão inicial do catálogo com os seguintes modelos de computação: diagramas BPMN, diagramas de classe da UML e regras de negócio. Visa-se contribuir para popularizar a abordagem de MDD com base em DSMLs e, em particular, a elaboração do design das DSMLs a partir de modelos de domínio, para o que o uso do catálogo efetivamente contribui.
This thesis presents a process for the creation of a catalog of models of computation to support the design of Domain-Specific Modeling Languages (DSMLs), and the first version of the catalog, which comprises attributes that aim to help the selection of the most suitable models of computation for each DSML development, and characteristics of software systems for which these models of computation are more appropriate. The context for the use of the catalog is the Model-Driven Development (MDD) - the approach where software development is based on graphical models that are subsequently translated (transformed) into lower-level models and, in the end, in source code in programming languages, such as Java or C #. The process was applied to generate an initial version of the catalog with the following models of computation: BPMN diagrams, UML class diagrams and business rules. It aims to contribute to popularize the MDD approach based in DSMLs, and in particular, the development of the DSMLs design from domain models, for which the use of the catalog effectively contributes.

Made available in DSpace on 2014-12-17T15:48:02Z (GMT). No. of bitstreams: 1 LidianeOSS_DISSERT.pdf: 4948473 bytes, checksum: f3f2d84880d3d969d6a1a9ec6252b0ff (MD5) Previous issue date: 2012-05-23
Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior
The approach Software Product Line (SPL) has become very promising these days, since it allows the production of customized systems on large scale through product families. For the modeling of these families the Features Model is being widely used, however, it is a model that has low level of detail and not may be sufficient to guide the development team of LPS. Thus, it is recommended add the Features Model to other models representing the system from other perspectives. The goals model PL-AOVgraph can assume this role complementary to the Features Model, since it has a to context oriented language of LPS's, which allows the requirements modeling in detail and identification of crosscutting concerns that may arise as result of variability. In order to insert PL-AOVgraph in development of LPS's, this paper proposes a bi-directional mapping between PL-AOVgraph and Features Model, which will be automated by tool ReqSys-MDD. This tool uses the approach of Model-Driven Development (MDD), which allows the construction of systems from high level models through successive transformations. This enables the integration of ReqSys-MDD with other tools MDD that use their output models as input to other transformations. So it is possible keep consistency among the models involved, avoiding loss of informations on transitions between stages of development
A abordagem de Linha de Produto de Software (LPS) tem se tornado bastante promissora nos dias de hoje, uma vez que permite a produ??o de sistemas customizados em larga escala, atrav?s de fam?lias de produtos. Para a modelagem destas fam?lias o Modelo de Features tem sido muito utilizado, no entanto, se trata de um modelo que apresenta baixo n?vel de detalhamento, podendo n?o ser suficiente para orientar a equipe de desenvolvimento da LPS. Dessa forma, ? recomend?vel agregar o Modelo de Features a outros modelos que representem o sistema sob outras perspectivas. O Modelo de Metas PL-AOVgraph pode assumir esta fun??o complementar ao Modelo de Features, uma vez que possui uma linguagem voltada para o contexto das LPS s, que permite a modelagem de requisitos de forma detalhada e a identifica??o de caracter?sticas transversais, que podem surgir em decorr?ncia da variabilidade. Com o objetivo de inserir PL-AOVgraph no processo de desenvolvimento das LPS s, este trabalho prop?e um mapeamento bi-direcional entre PLAOVgraph e Modelo de Features, que ser? automatizado pela ferramenta ReqSys-MDD. Esta ferramenta utiliza a abordagem de Desenvolvimento Orientado a Modelos (Model-Driven Development MDD), que permite a constru??o de sistemas a partir de modelos de alto n?vel, atrav?s de transforma??es sucessivas. Isto possibilita a integra??o de ReqSys-MDD com outras ferramentas MDD que utilizem seus modelos de sa?da como entrada para outras transforma??es. Assim, ? poss?vel manter a consist?ncia entre os modelos envolvidos, evitando a perda de informa??es nas transi??es entre as etapas de desenvolvimento

Made available in DSpace on 2014-12-17T15:47:59Z (GMT). No. of bitstreams: 1 EbertonSM_DISSERT.pdf: 4801479 bytes, checksum: 4ff5d2fe556a6d3554decf638f20261c (MD5) Previous issue date: 2010-08-02
Aspect-Oriented Software Development (AOSD) is a technique that complements the Object- Oriented Software Development (OOSD) modularizing several concepts that OOSD approaches do not modularize appropriately. However, the current state-of-the art on AOSD suffers with software evolution, mainly because aspect definition can stop to work correctly when base elements evolve. A promising approach to deal with that problem is the definition of model-based pointcuts, where pointcuts are defined based on a conceptual model. That strategy makes pointcut less prone to software evolution than model-base elements. Based on that strategy, this work defines a conceptual model at high abstraction level where we can specify software patterns and architectures that through Model Driven Development techniques they can be instantiated and composed in architecture description language that allows aspect modeling at architecture level. Our MDD approach allows propagate concepts in architecture level to another abstraction levels (design level, for example) through MDA transformation rules. Also, this work shows a plug-in implemented to Eclipse platform called AOADLwithCM. That plug-in was created to support our development process. The AOADLwithCM plug-in was used to describe a case study based on MobileMedia System. MobileMedia case study shows step-by-step how the Conceptual Model approach could minimize Pointcut Fragile Problems, due to software evolution. MobileMedia case study was used as input to analyses evolutions on software according to software metrics proposed by KHATCHADOURIAN, GREENWOOD and RASHID. Also, we analyze how evolution in base model could affect maintenance on aspectual model with and without Conceptual Model approaches
O Desenvolvimento de Software Orientado a Aspectos (DSOA) ? uma t?cnica que complementa o Desenvolvimento de Software Orientado a Objetos (DSOO) modularizando diversos conceitos que as abordagens para suporte ao DSOO n?o conseguiam modularizar adequadamente. No entanto, o estado da arte atual do DSOA sofre com a evolu??o de software, principalmente porque as defini??es de aspectos podem deixar de funcionar corretamente quando elementos do Modelo Base evoluem. Uma abordagem promissora para tratar este problema ? a defini??o de pontos de corte (pointcuts) baseados em modelos (model based-pointcuts), onde pontos de corte s?o definidos em termos de elementos de um Modelo Conceitual que s?o menos suscept?veis a evolu??o que elementos do Modelo Base. Com base nessa estrat?gia, este trabalho define um Modelo Conceitual em um alto n?vel de abstra??o onde se podem definir padr?es de software e de arquiteturas que atrav?s de t?cnicas de Desenvolvimento Dirigido a Modelos (Model Driven Development -MDD) podem ser instanciados e compostos em linguagens de descri??o arquitetural que suportem a modelagem de aspectos em n?vel de arquitetura. A abordagem MDD empregada permite ainda a propaga??o de conceitos descritos no Modelo Conceitual para outros n?veis de abstra??es como o de projeto com o uso de regras de transforma??o MDA (Model Driven Architecture). Este trabalho tamb?m mostra o plug-in para a plataforma Eclipse chamado de AOADLwithCM que foi implementado para dar suporte ao processo de desenvolvimento abordado. Esse plug-in foi utilizado para implementar um estudo de caso baseado no Sistema MobileMedia. Tal estudo de caso ilustra passo-a-passo a t?cnica que utiliza um Modelo Conceitual no DSOA para minimizar problemas de evolu??o (mais especificamente a Fragilidade de Pontos de Corte). O MobileMedia tamb?m foi usado como fonte para an?lise da abordagem sob m?tricas de software propostas por KHATCHADOURIAN, GREENWOOD e RASHID, e sob a perspectiva de manutenabilidade de software com e sem o Modelo Conceitual

Made available in DSpace on 2014-12-17T15:47:47Z (GMT). No. of bitstreams: 1 AnaLFM.pdf: 903790 bytes, checksum: 70d26a43bc5418b76d2ecdc1716d862c (MD5) Previous issue date: 2008-06-09
Aspect Oriented approaches associated to different activities of the software development process are, in general, independent and their models and artifacts are not aligned and inserted in a coherent process. In the model driven development, the various models and the correspondence between them are rigorously specified. With the integration of aspect oriented software development (DSOA) and model driven development (MDD) it is possible to automatically propagate models from one activity to another, avoiding the loss of information and important decisions established in each activity. This work presents MARISA-MDD, a strategy based on models that integrate aspect-oriented requirements, architecture and detailed design, using the languages AOV-graph, AspectualACME and aSideML, respectively. MARISA-MDD defines, for each activity, representative models (and corresponding metamodels) and a number of transformations between the models of each language. These transformations have been specified and implemented in ATL (Atlas Definition Language), in the Eclipse environment. MARISA-MDD allows the automatic propagation between AOV-graph, AspectualACME, and aSideML models. To validate the proposed approach two case studies, the Health Watcher and the Mobile Media have been used in the MARISA-MDD environment for the automatic generation of AspectualACME and aSideML models, from the AOV-graph model
As abordagens orientadas a aspectos relacionadas a diferentes atividades do processo de desenvolvimento de software s?o, em geral, independentes e os seus modelos e artefatos n?o est?o alinhados ou inseridos em um processo coerente. No desenvolvimento orientado a, modelos, os diversos modelos e a correspond?ncia entre eles s?o especificados com rigor. Com a integra??o do desenvolvimento orientado a aspectos (DSOA) e o desenvolvimento baseado em modelos (MDD) pode-se automaticamente propagar modelos de uma atividade para outra atividade, evitando a perda de informa??es e de decis?es importantes estabelecidas em cada atividade. Este trabalho apresenta MARISA-MDD, uma estrat?gia baseada em modelos que integra as atividades de requisitos, arquitetura e projeto detalhado orientado a aspectos, usando as linguagens AOV-graph, AspectualACME e aSideML, respectivamente. MARISA-MDD define, para cada atividade, modelos representativos (e metamodelos correspondentes) e um conjunto de transforma??es entre os modelos de cada linguagem. Tais transforma??es foram especificadas e implementadas em ATL (Atlas Definition Language), no ambiente Eclipse. MARISA-MDD permite a propaga??o autom?tica entre modelos AOV-graph, AspectualACME e aSideML. Para validar a abordagem proposta dois estudos de caso, o Health Watcher e o Mobile Media foram usados no ambienteMARISA-MDD para gera??o autom?tica dos modelos AspectualACME e aSideML, a partir do modelo AOV-graph

Made available in DSpace on 2014-07-29T14:57:53Z (GMT). No. of bitstreams: 1 wilane_mestrado.pdf: 4461079 bytes, checksum: da62fa9aebf506f095f41942a579aecc (MD5) Previous issue date: 2010-04-16
Building and maintaining a Graphical User Interface (GUI) for Enterprise Information Systems usually requires much Software Engineering staff time and effort. This paper describes a model-driven approach to create dynamically and manage these GUIs. In this approach, the Software Engineer designs conceptual models of the information system using object-oriented meta-models. A set of predefined mapping rules is applied to automatically transform and refine the conceptual models in order to generate, in runtime, the look and feel of the GUI, without source code creation. This improves the software usability, assuring consistency and homogeneity of the GUI, increases the productivity of the software engineering staff and simplifies maintenance. In our experiments we have observed an average productivity fifteen times higher than traditional methods of GUI development.
Construir e manter uma Interface Gráfica com Usuário (GUI) para Sistemas de Informação (SI) demanda muito tempo e esforço da equipe de Engenharia de Software. Esta dissertação descreve uma abordagem dirigida por modelos para criar dinamicamente e gerenciar essas interfaces. Nessa abordagem, o Engenheiro de Software projeta um modelo conceitual do sistema de informação usando um meta-modelo orientado a objetos. Um conjunto de regras de mapeamento predefinidas é aplicado para refinar e transformar o modelo conceitual do SI, gerando, em tempo de execução, a sua interface gráfica, com aparência e comportamentos específicos. Esse mecanismo melhora a usabilidade do software, assegurando consistência e homogeneidade das GUIs, aumenta a produtividade da equipe de Engenharia de Software e simplifica a manutenção do SI. Nos experimentos realizados foi observada uma média de produtividade quinze vezes maior do que os métodos tradicionais no desenvolvimento de GUIs.

Made available in DSpace on 2016-06-02T19:06:21Z (GMT). No. of bitstreams: 1 6591.pdf: 8019461 bytes, checksum: 4326ece159964b796f9e5dc900653fb4 (MD5) Previous issue date: 2014-09-17
The electronic gaming industry has recently witnessed an exponential growth in terms of titles and overall complexity of the games. This growth is responsible for many advances in computational technologies. But it also revealed problems related to the development process. It is very common that game projects exceed budget and schedule, not to mention the high number of bugs delivered to the final consumer. Current tools that support the development of games, such as game engines, allow great flexibility and artistic freedom, but require professionals with a high degree of technological knowledge, which means that a high financial investment is often needed. To help solving these problems, the literature suggests the use of Model-Driven Development (MDD). The increased abstraction level made possible through MDD can lead to higher reuse levels, and the automation achieved by code generation helps to reduce development time. But for automation, the developer often has to pay the price of reduced flexibility since the MDD exists a lack of flexibility in designs, but with manual code that can be overcome. Given these challenges, it is proposed an approach for game development that targets models to offer efficiency but without losing the flexibility in projects. This goal can be achieved through the integration of multiple DSLs with handwritten code, with the help of design patterns. To evaluate this approach, it was developed a tool capable of assisting the development of games following the concepts of MDD, which was subsequently subjected to experiments to validate its effectiveness. According to the experimental analysis, it was possible to observe that the proposed approach can provide the desired efficiency and flexibility in game development. It was also noted that due to the automation offered by code generators, inexperienced developers could create their projects with greater ease. However the study indicates that abstraction offered by MDD hinders the learning of the technology used.
Nos últimos anos, a indústria dos jogos eletrônicos tem assistido a um crescimento exponencial em termos de novos títulos e também na complexidade dos jogos. Este crescimento e responsável por muitos avanços nas tecnologias computacionais. Mas também revelou problemas relacionados com o processo de desenvolvimento. E muito comum que projetos de jogos excedam o orçamento e o cronograma, para não mencionar o elevado numero de jogos com defeitos entregues ao consumidor final. As ferramentas atuais que apoiam o desenvolvimento de jogos, tais como motores de jogo, permitem grande flexibilidade e liberdade artística, porem elas necessitam de profissionais com alto grau de conhecimento tecnológico, o que significa que muitas vezes e necessário um alto investimento financeiro. Para ajudar a resolver esses problemas, a literatura sugere o uso de Model-Driven Development (MDD). O aumento do nível de abstração oferecido pelo MDD pode conduzir a maiores níveis de reutilização, e da automação conseguida na geração de código ajudando a reduzir o tempo de desenvolvimento. Mas para ocorrer a automação, o desenvolvedor muitas vezes tem que pagar o preço da redução da flexibilidade ja que no MDD existe a falta de flexibilidade nos projetos, porem com código manual isso pode ser superado. Diante desses desafios é proposta neste trabalho uma abordagem de desenvolvimento de jogos dirigida a modelos capaz de oferecer eficiência sem perder a flexibilidade nos projetos. Esse objetivo pode ser alcançado por meio da integração de multiplas DSLs com códigos escritos a mão através da definição de padrões de projetos específicos. Para avaliar essa abordagem, foi desenvolvida uma ferramenta capaz de auxiliar o desenvolvimento de jogos seguindo os conceitos do MDD, a qual posteriormente foi submetida a experimentos para validar sua eficácia. De acordo com a analise experimental foi possível observar que a abordagem proposta pode oferecer a eficiência e flexibilidade desejada no desenvolvimento de jogos. Também foi notado que devido as automatizações oferecidas pelos geradores de código, desenvolvedores inexperientes puderam criar seus projetos com maior facilidade. Contudo o estudo indica que a abstração oferecida pelo MDD dificulta o aprendizado da tecnologia utilizada.

Model-driven software development (MDSD) and component-based software development are both paradigms for reducing complexity and for increasing abstraction and reuse in software development. In this thesis, we aim at combining the advantages of each by introducing methods from component-based development into MDSD. In MDSD, all artefacts that describe a software system are regarded as models of the system and are treated as the central development artefacts. To obtain a system implementation from such models, they are transformed and integrated until implementation code can be generated from them. Models in MDSD can have very different forms: they can be documents, diagrams, or textual specifications defined in different modelling languages. Integrating these models of different formats and abstraction in a consistent way is a central challenge in MDSD. We propose to tackle this challenge by explicitly separating the tasks of defining model components and composing model components, which is also known as distinguishing programming-in-the-small and programming-in-the-large. That is, we promote a separation of models into models for modelling-in-the-small (models that are components) and models for modelling-in-the-large (models that describe compositions of model components). To perform such component-based modelling, we introduce two architectural styles for developing systems with component-based MDSD (CB-MDSD). For CB-MDSD, we require a universal composition technique that can handle models defined in arbitrary modelling languages. A technique that can handle arbitrary textual languages is universal invasive software composition for code fragment composition. We extend this technique to universal invasive software composition for graph fragments (U-ISC/Graph) which can handle arbitrary models, including graphical and textual ones, as components. Such components are called graph fragments, because we treat each model as a typed graph and support reuse of partial models. To put the composition technique into practice, we developed the tool Reuseware that implements U-ISC/Graph. The tool is based on the Eclipse Modelling Framework and can therefore be integrated into existing MDSD development environments based on the framework. To evaluate the applicability of CB-MDSD, we realised for each of our two architectural styles a model-driven architecture with Reuseware. The first style, which we name ModelSoC, is based on the component-based development paradigm of multi-dimensional separation of concerns. The architecture we realised with that style shows how a system that involves multiple modelling languages can be developed with CB-MDSD. The second style, which we name ModelHiC, is based on hierarchical composition. With this style, we developed abstraction and reuse support for a large modelling language for telecommunication networks that implements the Common Information Model industry standard.

Software development is a complex task. Executable applications comprise a mutlitude of diverse components that are developed with various frameworks, libraries, or communication platforms. The technical complexity in development retains resources, hampers efficient problem solving, and thus increases the overall cost of software production. Another significant challenge in market-driven software engineering is the variety of customer needs. It necessitates a maximum of flexibility in software implementations to facilitate the deployment of different products that are based on one single core. To reduce technical complexity, the paradigm of Model-Driven Software Development (MDSD) facilitates the abstract specification of software based on modeling languages. Corresponding models are used to generate actual programming code without the need for creating manually written, error-prone assets. Modeling languages that are tailored towards a particular domain are called domain-specific languages (DSLs). Domain-specific modeling (DSM) approximates technical solutions with intentional problems and fosters the unfolding of specialized expertise. To cope with feature diversity in applications, the Software Product Line Engineering (SPLE) community provides means for the management of variability in software products, such as feature models and appropriate tools for mapping features to implementation assets. Model-driven development, domain-specific modeling, and the dedicated management of variability in SPLE are vital for the success of software enterprises. Yet, these paradigms exist in isolation and need to be integrated in order to exhaust the advantages of every single approach. In this thesis, we propose a way to do so. We introduce the paradigm of Multi-Domain Engineering (MDE) which means model-driven development with multiple domain-specific languages in variability-intensive scenarios. MDE strongly emphasize the advantages of MDSD with multiple DSLs as a neccessity for efficiency in software development and treats the paradigm of SPLE as indispensable means to achieve a maximum degree of reuse and flexibility. We present HybridMDSD as our solution approach to implement the MDE paradigm. The core idea of HybidMDSD is to capture the semantics of particular DSLs based on properly defined semantics for software models contained in a central upper ontology. Then, the resulting semantic foundation can be used to establish references between arbitrary domain-specific models (DSMs) and sophisticated instance level reasoning ensures integrity and allows to handle partiucular change adaptation scenarios. Moreover, we present an approach to automatically generate composition code that integrates generated assets from separate DSLs. All necessary development tasks are arranged in a comprehensive development process. Finally, we validate the introduced approach with a profound prototypical implementation and an industrial-scale case study
Softwareentwicklung ist komplex: ausführbare Anwendungen beinhalten und vereinen eine Vielzahl an Komponenten, die mit unterschiedlichen Frameworks, Bibliotheken oder Kommunikationsplattformen entwickelt werden. Die technische Komplexität in der Entwicklung bindet Ressourcen, verhindert effiziente Problemlösung und führt zu insgesamt hohen Kosten bei der Produktion von Software. Zusätzliche Herausforderungen entstehen durch die Vielfalt und Unterschiedlichkeit an Kundenwünschen, die der Entwicklung ein hohes Maß an Flexibilität in Software-Implementierungen abverlangen und die Auslieferung verschiedener Produkte auf Grundlage einer Basis-Implementierung nötig machen. Zur Reduktion der technischen Komplexität bietet sich das Paradigma der modellgetriebenen Softwareentwicklung (MDSD) an. Software-Spezifikationen in Form abstrakter Modelle werden hier verwendet um Programmcode zu generieren, was die fehleranfällige, manuelle Programmierung ähnlicher Komponenten überflüssig macht. Modellierungssprachen, die auf eine bestimmte Problemdomäne zugeschnitten sind, nennt man domänenspezifische Sprachen (DSLs). Domänenspezifische Modellierung (DSM) vereint technische Lösungen mit intentionalen Problemen und ermöglicht die Entfaltung spezialisierter Expertise. Um der Funktionsvielfalt in Software Herr zu werden, bietet der Forschungszweig der Softwareproduktlinienentwicklung (SPLE) verschiedene Mittel zur Verwaltung von Variabilität in Software-Produkten an. Hierzu zählen Feature-Modelle sowie passende Werkzeuge, um Features auf Implementierungsbestandteile abzubilden. Modellgetriebene Entwicklung, domänenspezifische Modellierung und eine spezielle Handhabung von Variabilität in Softwareproduktlinien sind von entscheidender Bedeutung für den Erfolg von Softwarefirmen. Zur Zeit bestehen diese Paradigmen losgelöst voneinander und müssen integriert werden, damit die Vorteile jedes einzelnen für die Gesamtheit der Softwareentwicklung entfaltet werden können. In dieser Arbeit wird ein Ansatz vorgestellt, der dies ermöglicht. Es wird das Multi-Domain Engineering Paradigma (MDE) eingeführt, welches die modellgetriebene Softwareentwicklung mit mehreren domänenspezifischen Sprachen in variabilitätszentrierten Szenarien beschreibt. MDE stellt die Vorteile modellgetriebener Entwicklung mit mehreren DSLs als eine Notwendigkeit für Effizienz in der Entwicklung heraus und betrachtet das SPLE-Paradigma als unabdingbares Mittel um ein Maximum an Wiederverwendbarkeit und Flexibilität zu erzielen. In der Arbeit wird ein Ansatz zur Implementierung des MDE-Paradigmas, mit dem Namen HybridMDSD, vorgestellt

Made available in DSpace on 2014-07-29T14:57:47Z (GMT). No. of bitstreams: 1 Dissertacao Valdomeria N de M Morgado 2010.pdf: 793904 bytes, checksum: 6ebfc3ed36711bf080787eaa46eea743 (MD5) Previous issue date: 2010-11-22
An Information System (IS) has three main aspects: a database that contains data which is processed to generate business information; an application functions which transforms data in information; and business rules which control and restrict data manipulated by the functions. An IS evolves continuously to follow the corporation changes, and the database should be change to attend the new requirements. This dissertation presents a model driven approach to generate and evolve IS databases. A software component, called Especialista em Banco de Dados (EBD), was developed. There are two mapping sets for database generation: from Modelo de Meta Objeto (MMO) (used to representing IS) to Relational Model (RM), and from this to DBMS PostgreSQL SQL dialect. The component EBD is a part of a framework for modeling, building and maintaining enterprise information systems software. This component provides services to other framework components. To validate the proposed approach, Software Engineers had developed IS using the component EBD. The Dissertation main contributions are an approach to support IS database life cycle, a software architecture to generate and evolve IS database schema, an IS data representation model (MMO), a mapping specification to generate schema and stored procedures and the definition of automated operation sets to evolve IS database schema.
Um Sistema de Informação (SI) Corporativo tem três aspectos principais: o banco de dados, que contém dados que são processados para gerar informações do negócio; as funções de aplicação, que transformam dados em informações; e as regras de negócio, que controlam e restringem a manipulação dos dados pelas funções. Um SI precisa evoluir continuamente para acompanhar as mudanças na corporação e, consequentemente, o banco de dados deve ser modificado para atender aos novos requisitos de negócio. Esta dissertação apresenta uma abordagem dirigida por modelos para a automatização do processo de transformação na geração e evolução de bancos de dados de Sistema de Informação. Para isso foi criado um componente de software denominado Especialista em Banco de Dados (EBD). Dois conjuntos de mapeamentos são apresentados para a geração de esquemas, um do modelo conceitual chamado Modelo de Meta Objeto (MMO), utilizado para representação de SI, para o Modelo Relacional; e deste para o dialeto SQL do SGBD PostgreSQL. O componente EBD faz parte de um framework que gera, evolui e gerencia Sistemas de Informação. Este componente fornece também serviços para outros componentes deste framework. Uma experimentação foi feita com engenheiros de software com experiência em desenvolvimento de Sistema de Informação para validar a abordagem proposta. As principais contribuições desta dissertação são: abordagem que apoia ciclo de vida de BD de SI, arquitetura de software que permite a geração e evolução de esquema de SI, especificação de um modelo de representação de dados de SI (MMO), especificação de mapeamentos para geração de esquema e procedimentos de manipulação e definição de um conjunto de operações que automatizam o processo de evolução de esquema de BD de SI.

Made available in DSpace on 2016-06-02T19:06:19Z (GMT). No. of bitstreams: 1 6469.pdf: 4680875 bytes, checksum: 348ed33838e264f70033e8383aeaa100 (MD5) Previous issue date: 2014-10-27
The integrated network management system aims to manage the telecommunications network, regardless of network elements technology in order to identify the causes of problems, providing a more assertive decision making to remedy these problems and make the network available and operational. Thus, can to cater to the market that is increasingly demanding with the level of quality telecommunications products and services. Given this need, integrated networks management system belongs to a real company needs to respond quickly to customers' expectations with respect to requests for new functions system, and perform technology upgrades periodically. However, the integrated network management system development use centered-source technologies, and it requires great effort and hinders reuse. In this context, this master's project presents a proposal to facilitate the integrated network management system development using the techniques of MDD (Model Driven Development). MDD emphasizes the use of models in software development. These models specify the rules of business domain at a high level of abstraction, i.e., regardless of the programming language and to run the software platform. With appropriate computational tools transformations of models in the source code are performed. The use of MDD can provide software reuse procedurally, enabling faster development, lower cost, produce a flexible software and enable faster modifications. To apply MDD approach, a Domain Specific Language (DSL) for the configuration management of integrated network management system setting is designed to facilitate the inclusion of a new technology to be managed by the system, while providing faster development and with fewer errors of code. To evaluate the proposal, an experiment was conducted with the participation of software developers that know the system and work in this real company. The results showed that according to the descriptive analyses there was a reduction in the time spent in application development when it was used DSL compared to the specialization of classes. However, hypotheses tests showed no such reduction. The insertion of errors in the code occurred only in applications developed using specialization classes. The use of DSL provided a broader view of the business rule and you do not need knowledge of the programming language, once the code was automatically generated.
Um sistema de gerenciamento integrado de redes tem o objetivo de gerenciar uma rede de telecomunicações, independentemente da tecnologia dos elementos de rede, a fim de identificar as causas de problemas, proporcionando a tomada de decisão mais assertiva para saná-los e deixar a rede disponível e operacional. Dessa forma, o mercado que está cada vez mais exigente com o nível de qualidade dos produtos e serviços de telecomunicações é atendido. Diante dessa necessidade, o sistema de gerenciamento integrado de redes de uma empresa real precisa atender rapidamente às expectativas dos clientes com relação às solicitações de novas funções do sistema, assim como realizar atualizações tecnológicas periodicamente. Porém, o desenvolvimento do sistema de gerenciamento integrado de redes dessa empresa utiliza tecnologias centradas em código-fonte, o que implica em grande esforço e dificulta a sua reutilização. Neste contexto, este projeto de mestrado apresenta uma proposta para facilitar o desenvolvimento do sistema de gerenciamento integrado de redes utilizando as técnicas de MDD (Desenvolvimento Dirigido a Modelos). MDD enfatiza a utilização de modelos no desenvolvimento do software. Esses modelos especificam as regras de negócio de domínio em um alto nível de abstração, ou seja, independentemente da linguagem de programação e da plataforma de execução do software. Com ferramentas computacionais adequadas são realizadas as transformações dos modelos em código-fonte. A utilização de MDD pode proporcionar reúso de software de forma processual, possibilitar um desenvolvimento mais rápido, com menor custo, produzir um software flexível e possibilitar modificações mais rapidamente. Para aplicar a abordagem de MDD, uma linguagem específica de domínio (DSL) para a gerência de configuração do sistema de gerenciamento integrado de redes foi desenvolvida. Tem como objetivo facilitar a inclusão de uma nova tecnologia a ser gerenciada pelo sistema e ao mesmo tempo proporcionar um desenvolvimento mais rápido, com menos erros de código. Para avaliar a proposta foi realizado um experimento com a participação dos atuais desenvolvedores de software de uma empresa real. Os resultados obtidos mostraram que, segundo a análise descritiva, houve redução do tempo gasto no desenvolvimento das aplicações quando foi utilizada a DSL em comparação com o desenvolvimento baseado em especialização das classes. Porém, os testes das hipóteses não apresentaram tal redução. A inserção de erros no código ocorreu somente nas aplicações desenvolvidas utilizando especialização das classes. O uso da DSL proporcionou uma visão mais ampla da regra de negócio e não exigiu conhecimento da linguagem de programação, pois o código foi gerado automaticamente.

Software development is a complex task. Executable applications comprise a mutlitude of diverse components that are developed with various frameworks, libraries, or communication platforms. The technical complexity in development retains resources, hampers efficient problem solving, and thus increases the overall cost of software production. Another significant challenge in market-driven software engineering is the variety of customer needs. It necessitates a maximum of flexibility in software implementations to facilitate the deployment of different products that are based on one single core. To reduce technical complexity, the paradigm of Model-Driven Software Development (MDSD) facilitates the abstract specification of software based on modeling languages. Corresponding models are used to generate actual programming code without the need for creating manually written, error-prone assets. Modeling languages that are tailored towards a particular domain are called domain-specific languages (DSLs). Domain-specific modeling (DSM) approximates technical solutions with intentional problems and fosters the unfolding of specialized expertise. To cope with feature diversity in applications, the Software Product Line Engineering (SPLE) community provides means for the management of variability in software products, such as feature models and appropriate tools for mapping features to implementation assets. Model-driven development, domain-specific modeling, and the dedicated management of variability in SPLE are vital for the success of software enterprises. Yet, these paradigms exist in isolation and need to be integrated in order to exhaust the advantages of every single approach. In this thesis, we propose a way to do so. We introduce the paradigm of Multi-Domain Engineering (MDE) which means model-driven development with multiple domain-specific languages in variability-intensive scenarios. MDE strongly emphasize the advantages of MDSD with multiple DSLs as a neccessity for efficiency in software development and treats the paradigm of SPLE as indispensable means to achieve a maximum degree of reuse and flexibility. We present HybridMDSD as our solution approach to implement the MDE paradigm. The core idea of HybidMDSD is to capture the semantics of particular DSLs based on properly defined semantics for software models contained in a central upper ontology. Then, the resulting semantic foundation can be used to establish references between arbitrary domain-specific models (DSMs) and sophisticated instance level reasoning ensures integrity and allows to handle partiucular change adaptation scenarios. Moreover, we present an approach to automatically generate composition code that integrates generated assets from separate DSLs. All necessary development tasks are arranged in a comprehensive development process. Finally, we validate the introduced approach with a profound prototypical implementation and an industrial-scale case study.
Softwareentwicklung ist komplex: ausführbare Anwendungen beinhalten und vereinen eine Vielzahl an Komponenten, die mit unterschiedlichen Frameworks, Bibliotheken oder Kommunikationsplattformen entwickelt werden. Die technische Komplexität in der Entwicklung bindet Ressourcen, verhindert effiziente Problemlösung und führt zu insgesamt hohen Kosten bei der Produktion von Software. Zusätzliche Herausforderungen entstehen durch die Vielfalt und Unterschiedlichkeit an Kundenwünschen, die der Entwicklung ein hohes Maß an Flexibilität in Software-Implementierungen abverlangen und die Auslieferung verschiedener Produkte auf Grundlage einer Basis-Implementierung nötig machen. Zur Reduktion der technischen Komplexität bietet sich das Paradigma der modellgetriebenen Softwareentwicklung (MDSD) an. Software-Spezifikationen in Form abstrakter Modelle werden hier verwendet um Programmcode zu generieren, was die fehleranfällige, manuelle Programmierung ähnlicher Komponenten überflüssig macht. Modellierungssprachen, die auf eine bestimmte Problemdomäne zugeschnitten sind, nennt man domänenspezifische Sprachen (DSLs). Domänenspezifische Modellierung (DSM) vereint technische Lösungen mit intentionalen Problemen und ermöglicht die Entfaltung spezialisierter Expertise. Um der Funktionsvielfalt in Software Herr zu werden, bietet der Forschungszweig der Softwareproduktlinienentwicklung (SPLE) verschiedene Mittel zur Verwaltung von Variabilität in Software-Produkten an. Hierzu zählen Feature-Modelle sowie passende Werkzeuge, um Features auf Implementierungsbestandteile abzubilden. Modellgetriebene Entwicklung, domänenspezifische Modellierung und eine spezielle Handhabung von Variabilität in Softwareproduktlinien sind von entscheidender Bedeutung für den Erfolg von Softwarefirmen. Zur Zeit bestehen diese Paradigmen losgelöst voneinander und müssen integriert werden, damit die Vorteile jedes einzelnen für die Gesamtheit der Softwareentwicklung entfaltet werden können. In dieser Arbeit wird ein Ansatz vorgestellt, der dies ermöglicht. Es wird das Multi-Domain Engineering Paradigma (MDE) eingeführt, welches die modellgetriebene Softwareentwicklung mit mehreren domänenspezifischen Sprachen in variabilitätszentrierten Szenarien beschreibt. MDE stellt die Vorteile modellgetriebener Entwicklung mit mehreren DSLs als eine Notwendigkeit für Effizienz in der Entwicklung heraus und betrachtet das SPLE-Paradigma als unabdingbares Mittel um ein Maximum an Wiederverwendbarkeit und Flexibilität zu erzielen. In der Arbeit wird ein Ansatz zur Implementierung des MDE-Paradigmas, mit dem Namen HybridMDSD, vorgestellt.

Made available in DSpace on 2016-06-02T19:06:01Z (GMT). No. of bitstreams: 1 4801.pdf: 4117819 bytes, checksum: b4df67024157ee1a2c79256315a97e7d (MD5) Previous issue date: 2012-11-13
Universidade Federal de Sao Carlos
Software development techniques continually evolve in order to improve development and maintenance processes in addition to lower costs and higher quality. The goal of MDD is to reduce the semantic distance between a problem and its solution specification. Therefore MDD focuses on high-level abstraction modeling and successive model transformations, until finally, generate code. Studies assert that model-driven development can be significantly more efficient than traditional source code-driven software development and still reduce the possibility of occurrence of several problems during the software life-cycle. Likewise, Web engineering can also be benefited by MDD adoption, especially when supported by approaches that facilitate MDD use. Web development is usually agile with frequent releases, these approaches must be flexible to adapt to this context. However, generally, the approaches proposed by the academic community have complex processes which involve many different model definitions, programming languages, plug-ins and IDEs. These features contradict the practices adopted by Web developers. This paper presents the MWDA (Model-Driven Web Applications) approach that provides a simple process to support model-driven web development. This approach does not depend on tools, technologies or plug-ins and encourage combination with other forms of reuse and development processes. Furthermore, the Ruby- MDWA was developed with Ruby language and Ruby on Rails framework support, in order to create Web applications with MDWA assistance. This tool provides a set of textual models and defines M2M and M2C transformation tools, maintaining the requirements traceability since its specification to its construction and further maintenance. In order to show the use of the approach and tool, it was performed a real study case with a software company, from São Carlos SP, where a project management system was developed. In parallel, two experiments were conducted with undergraduate students in Computer Science and Computer Engineering and a Masters in Computer Science, to evaluate the gains and limitations of the Ruby-MDWA tool.
As técnicas de desenvolvimento de software evoluem continuamente com a finalidade de melhorar processos de construção e manutenção de software, além de obter ganhos em tempo, custo e qualidade. O objetivo do MDD é reduzir a distância semântica entre um problema e a especificação de sua solução. Para isso, MDD tem enfoque na modelagem de alto nível de abstração e em sucessivos refinamentos dos modelos construídos em artefatos mais detalhados, até enfim, gerar código. Há afirmações de que o desenvolvimento orientado a modelos pode ser significativamente mais eficiente que o desenvolvimento tradicional guiado por código fonte, além de reduzir a possibilidade de ocorrência de uma série de problemas durante o ciclo de vida do software. Da mesma forma, a engenharia de aplicações Web também pode ser beneficiada pela adoção de MDD, em especial com o apoio de abordagens que facilitem sua utilização. Como o desenvolvimento de aplicações Web comumente é ágil e com publicações freqüentes, essas abordagens devem ser flexíveis para que se adaptem a esse contexto. Entretanto, em geral, as abordagens propostas pela comunidade acadêmica apresentam processos complexos que envolvem diversos modelos, linguagens de programação, plug-ins e ambientes de programação. Essas características contrariam as práticas aprovadas pelos desenvolvedores Web. Esta dissertação apresenta a abordagem MDWA (Model-Driven Web Applications) que fornece um processo simples para desenvolvimento de software Web com apoio de MDD. A abordagem não depende de ferramentas, tecnologias ou plug-ins e estimula a combinação com outras formas de reuso e processos de desenvolvimento. Além disso, foi construída uma ferramenta, denominada Ruby-MDWA, baseada na linguagem Ruby e no framework Ruby on Rails destinada à criação de aplicações Web com auxílio da abordagem MDWA. Essa ferramenta fornece um conjunto de quatro modelos textuais e define transformadores M2M e M2C, que mantém a rastreabilidade de um requisito desde sua especificação até sua construção e posterior manutenção. Para mostrar o uso da abordagem e da ferramenta, foi realizado um estudo de caso real em conjunto com uma empresa de software de São Carlos SP, onde um sistema de gerenciamento de projetos foi desenvolvido. De forma paralela, foram conduzidos dois experimentos com alunos de graduação em Bacharelado em Ciência da Computação e Engenharia de Computação e mestrado em computação da UFSCar, visando avaliar os ganhos e as limitações da ferramenta Ruby-MDWA.

Mit dem Wandel des Internets zu einer universellen Softwareplattform sind die Möglichkeiten und Fähigkeiten von Webanwendungen zwar rasant gestiegen. Gleichzeitig gestaltet sich ihre Entwicklung jedoch zunehmend aufwändig und komplex, was dem Wunsch nach immer kürzeren Entwicklungszyklen für möglichst situative, bedarfsgerechte Lösungen entgegensteht. Bestehende Ansätze aus Forschung und Technik, insbesondere im Umfeld der serviceorientierten Architekturen und Mashups, werden diesen Problemen bislang nicht ausreichend gerecht. Deshalb werden in dieser Dissertation neue Konzepte für die modellgetriebene Entwicklung und Bereitstellung von Webanwendungen vorgestellt. Die zugrunde liegende Idee besteht darin, das Paradigma der Serviceorientierung auf die Präsentationsebene zu erweitern. So sollen erstmals – neben Daten- und Geschäftslogik – auch Teile der Anwendungsoberfläche in Form wiederverwendbarer Komponenten über Dienste bereitgestellt werden. Anwendungen sollen somit über alle Anwendungsebenen hinweg nach einheitlichen Prinzipien „komponiert“ werden können. Den ersten Schwerpunkt der Arbeit bilden die entsprechenden universellen Modellierungskonzepte für Komponenten und Kompositionen. Sie erlauben u. a. die plattformunabhängige Beschreibung von Anwendungen als Komposition der o. g. Komponenten. Durch die Abstraktion und entsprechende Autorenwerkzeuge wird die Entwicklung so auch für Domänenexperten bzw. Nicht-Programmierer möglich. Der zweite Schwerpunkt liegt auf dem kontextadaptiven Integrationsprozess von Komponenten und der zugehörigen, serviceorientierten Referenzarchitektur. Sie ermöglichen die dynamische Suche, Bindung und Konfiguration von Komponenten, d. h. auf Basis der o. g. Abstraktionen können genau die Anwendungskomponenten geladen und ausgeführt werden, die für den vorliegenden Nutzer-, Nutzungs- und Endgerätekontext am geeignetsten sind. Der dritte Schwerpunkt adressiert die Kontextadaptivität der kompositen Anwendungen in Form von Konzepten zur aspektorientierten Definition von adaptivem Verhalten im Modell und dessen Umsetzung zur Laufzeit. In Abhängigkeit von Kontextänderungen können so Rekonfigurationen von Komponenten, ihr Austausch oder Veränderungen an der Komposition, z.B. am Layout oder dem Datenfluss, automatisch durchgesetzt werden. Alle vorgestellten Konzepte wurden durch prototypische Implementierungen praktisch untermauert. Anhand diverser Anwendungsbeispiele konnten ihre Validität und Praktikabilität – von der Modellierung im Autorenwerkzeug bis zur Ausführung und dynamischen Anpassung – nachgewiesen werden. Die vorliegende Dissertation liefert folglich eine Antwort auf die Frage, wie zukünftige Web- bzw. Mashup-Anwendungen zeit- und kostengünstig entwickelt sowie zuverlässig und performant ausgeführt werden können. Die geschaffenen Konzepte bilden gleichermaßen die Grundlage für eine Vielzahl an Folgearbeiten.

Graphical modeling is becoming an increasingly important part of software engineering as it provides means of increasing productivity by raising the level of abstraction in software devel-opment. One of the most widely adopted modeling notations is the Unified Modeling Language (UML) which has gained popularity due to its generality and broad applicability. Despite its advantages, this general purpose notation is burdened with the lack of purpose specific model-ing abstractions. The modeling abstractions in the language lack specialized properties and thus models might not precisely express the intentions of the modeler. In consequence, this leads to ineffectiveness of using models in UML. This thesis presents research aimed at improving modeling with UML. By exploiting the language customization mechanisms inherent in UML – stereotypes and profiles – the research presented in the thesis explores such aspects of improving modeling as creating language cus-tomizations or using a customized modeling language. The context, in which the modeling is considered, is delineated by the principles of model driven software development (MDD). The principles recognize the usage of models as the primary artefacts in software development thus providing a solid foundation for considering the use of models in software development. One of the contributions in the thesis is the identification and definition of factors determin-ing the successful realization of MDD in industry. These factors provide means of positioning language customization in the forefront of MDD. Another contribution in the thesis is eliciting and prioritizing a set of criteria for choosing between language customization mechanisms, which is a result of another industrial case study. A series of experiments in academic and industrial environments showed the magnitude of improvements to be expected after replacing a standard modeling language with a customized modeling notation. This series of experiments provided a basis for experimenting with stereo-types and software inspections which indicated a considerable increase in effectiveness of the reading techniques used in software inspections after replacing a standard notation with a cus-tomized one. The results from all empirical studies affected the development of quality assessment crite-ria for stereotypes. The criteria and the exploration of several existing profiles led to the devel-opment of guidelines for creating “good” stereotypes by analyzing existing UML profiles. An additional contribution in the thesis is exploring the usage of an alternative mechanism to stereo-types – model libraries – for adaptation of a modeling language. The way in which model librar-ies can be created in an efficient way is studied by creating a method for extracting knowledge from ontologies into UML domain models. The results of the research presented in the thesis show how to improve modeling with UML by customizing the language with stereotypes. The main contribution is the exploration and evaluation of issues related to creating language customizations and using the customized language.

One important phase in software development process is to create a design model of the system which follows all the architectural rules. Often the architectural rules are defined by the system architect and the system model is designed by the system designer. The architect defines the rules in a text file where no standard or pattern is followed. Therefore, there is always the risk of violating the architectural rules by the designer. So manual reviews on the system model should be done by the architect to ensure the system model is valid.In order to remove this manual checking which can be erroneous and time consuming ArCon (Architecture Conformance Checker) was developed by Combitech AB. ArCon is a tool which lets the architect define the architectural rules in the format of UML (Unified Modeling Language) models where the elements of the model have different meaning than the standard UML. ArCon can read this model and extract architectural rules from it and check the system model against those rules and then print all the rule violations.ArCon is an open source tool i.e. free for everyone to download and use. Currently, it supports Papyrus as the UML modeling tool. Papyrus is integrated to Eclipse platform and is a general purpose modeling tool. It supports users with all types of UML diagrams and elements.The idea for this thesis work was to implement a new feature for ArCon in order to facilitate the design process for system designers. The feature should provide the system designers only those types of elements which they are permitted to add to a specific fraction of the system model. The list of permitted element types should be extracted from the architecture model where all the architectural rules are defined in advance. This new support in ArCon was named Domain Specific Modeling (DSM) support.To evaluate the effect of DSM support on the system designers performance a few test sessions, called usability tests, were performed. The participants in the test sessions were a representative sample of software designers. After analyzing the data collected from the test sessions, the pros and cons of the new support were discovered. Furthermore, a few new ideas for enhancing DSM support were generated.

Requirements Engineering (ER) has an important role in Software Engineering for being an early stage of the software development process. ER serves as the basis for implementation of other activities, contributing decisively to the quality of the final software product. Requirements Elicitation process is among the main concerns of ER. It involves the recognition and description of customer needs, in such a way that it is possible to reflect the business accurately and consistent. Moreover, in general, most problems that occur during the process of software development are caused by failures in the early stages. In this context, emerging approaches such as Model-Driven Developement (MDD) and Business Process Modeling (MPN). Such approaches seek to understand and describe business processes and enable a closer look of the domain. As well, especially when backed by support tools, using approaches such as MDD and MPN can contribute to improving the quality of the requirements and the requirements Elicitation process. This work presents ModelER approach, which seeks to promote improvements in Requirements Elicitation process, through the use of concepts and practices of the MDD and the MPN for identifying software requirements.
A Engenharia de Requisitos (ER) possui um importante papel na Engenharia de Software pelo fato de compreender uma fase inicial do processo de desenvolvimento de software. Ela serve de base para a realização das demais atividades, contribuindo decisivamente para a qualidade do produto de software final. O processo de Elicitação de Requisitos está entre as principais preocupações da ER. Ele envolve o reconhecimento e a descrição das necessidades dos clientes, de tal forma que seja possível refletir o negócio de forma precisa e coerente. Além disso, de maneira geral, a maior parte dos problemas que ocorrem durante o processo de desenvolvimento de software é causada por falhas nas fases iniciais. Diante desse contexto, surgem abordagens tais como o Desenvolvimento Orientado por Modelos (Model-Driven Developement MDD) e a Modelagem de Processos de Negócio (Business Process Modeling MPN1). Tais abordagens tanto buscam compreender e descrever os processos de negócio, quanto permitem uma visão mais próxima do domínio. Assim, sobretudo quando apoiadas por ferramentas de suporte, o uso de abordagens como MDD e MPN pode contribuir para a melhoria da qualidade dos requisitos e do processo de Elicitação de Requisitos. Este trabalho apresenta a abordagem ModelER, a qual busca promover melhorias no processo de Elicitação de Requisitos, através da utilização de conceitos e práticas do MDD e da MPN para identificação de requisitos de software.

The Unified Modelling Language (UML) is intended to express complex ideas in an intuitive and easily understood way. It is important because it is widely used in software engineering and other disciplines. Although an official definition document exists, there is much debate over the precise meaning of UML models. ¶ In response, the academic community have put forward many different proposals for formalising UML, but it is not at all obvious how to decide between them. Indeed, given that UML practitioners are inclined to reject formalisms as non-intuitive, it is not even obvious that the definition should be “formal” at all. Rather than searching for yet another formalisation of UML, our main aim is to determine what would constitute a good definition of UML. ¶ The first chapter sets the UML definition problem in a broad context, relating it to work in logic and the philosophy of science. More specific conclusions about the nature of model driven development are reached in the beginning of Chapter 2. We then develop criteria for a definition of UML. Applying these criteria to the existing definition, we find that it is lacking in clarity. We then set out to test the precision of the definition. The test is to take an apparently inconsistent model, and determine whether it really is inconsistent according to the definition. ¶ Many people have proposed that UML models are graphs, but few have justified this choice using the official definition of UML. We begin Chapter 3 by arguing from the official definition that UML models are graphs and that instantiation is a graph homomorphism into an interpretation functor. The official definition of UML defines the semantics against its abstract syntax, which is in turn defined by a UML model. Chapters 3 and 4 prepare for our test by resolving this apparent circularity. The result is a semantics for the metamodel fragment of the language. ¶ In Chapter 5, we find, contrary to popular belief, that the official definition does provide sufficient semantics to classify the example model as inconsistent. Moreover, the sustained study of the semantics in Chapters 3 to 5 confirms our initial argument that the semantic domain is graphs. The Actions are the building blocks of UML’s prescriptive dynamics. We see that they can be naturally defined as graph transformation rules. Sequence diagrams are the main example of descriptive dynamics, but we find that their official semantics are broken. The “recorded history” approach should be replaced, we suggest, by a graph-oriented dynamic logic. ¶ Chapter 6 presents our early work on dynamic logic for UML sequence diagrams and further explores the proposed semantic repairs. In Chapter 7, guided by the criteria developed in Chapter 2, we critically survey the UML formalisation literature and conclude that an existing body of graph transformation based work known as “dynamic metamodelling” is very close to what is required. ¶ The final chapter draws together our conclusions. It proposes a category theoretic construction to merge models of the syntax and semantic domain, yielding a type graph for the graph transformation system which defines the dynamic semantics of the language. Finally, it outlines the further work required to realise a satisfactory definition of UML.

Atualmente, o projeto de sistemas tempo-real embarcados e distribuídos está crescendo em complexidade devido à sua natureza heterogênea e ao crescente número e diversidade de funções que um único sistema desempenha. Sistemas de automação industrial, sistemas eletrônicos em automóveis e veículos aéreos, equipamentos médicos, entre outros, são exemplos de tais sistemas. Tais sistemas são compostos por componentes distintos (blocos de hardware e software), os quais geralmente são projetados concorrentemente utilizando modelos, ferramentas e linguagens de especificação e implementação diferentes. Além disso, estes sistemas tem requisitos específicos e importantes, os quais não representam (por si só) as funcionalidades esperadas do sistema, mas podem afetar a forma como o sistema executa suas funcionalidades e são muito importantes para a realização do projeto com sucesso. Os chamados requisitos não-funcionais são difíceis de tratar durante todo o ciclo de projeto porque normalmente um único requisito não-funcional afeta vários componentes diferentes. A presente tese de doutorado propõe a integração automatizada das fases de projeto de sistemas tempo-real embarcados e distribuídos focando em aplicações na área da automação. A abordagem proposta usa técnicas de engenharia guiada por modelos (do inglês Model Driven Engineering ou MDE) e projeto orientado a aspectos (do inglês Aspect-Oriented Design ou AOD) juntamente com o uso de plataformas previamente desenvolvidas (ou desenvolvida por terceiros) para projetar os componentes de sistemas tempo-real embarcados e distribuídos. Adicionalmente, os conceitos de AOD permitem a separação no tratamento dos requisitos de naturezas diferentes (i.e. requisitos funcionais e não-funcionais), melhorando a modularização dos artefatos produzidos (e.g. modelos de especificação, código fonte, etc.). Além disso, esta tese propõe uma ferramenta de geração de código, que suporta a transição automática das fases iniciais de especificação para as fases seguintes de implementação. Esta ferramenta usa um conjunto de regras de mapeamento, que descrevem como elementos nos níveis mais altos de abstração são mapeados (ou transformados) em elementos dos níveis mais baixos de abstração. Em outras palavras, tais regras de mapeamento permitem a transformação automática da especificação inicial, as quais estão mais próximo do domínio da aplicação, em código fonte para os componentes de hardware e software, os quais podem ser compilados e sintetizados por outras ferramentas para se obter a realização/implementação do sistema tempo-real embarcado e distribuído.
Currently, the design of distributed embedded real-time systems is growing in complexity due to the increasing amount of distinct functionalities that a single system must perform, and also to concerns related to designing different kinds of components. Industrial automation systems, embedded electronics systems in automobiles or aerial vehicles, medical equipments and others are examples of such systems, which includes distinct components (e.g. hardware and software ones) that are usually designed concurrently using distinct models, tools, specification, and implementation languages. Moreover, these systems have domain specific and important requirements, which do not represent by themselves the expected functionalities, but can affect both the way that the system performs its functionalities as well as the overall design success. The so-called nonfunctional requirements are difficult to deal with during the whole design because usually a single non-functional requirement affects several distinct components. This thesis proposes an automated integration of distributed embedded real-time systems design phases focusing on automation systems. The proposed approach uses Model- Driven Engineering (MDE) techniques together with Aspect-Oriented Design (AOD) and previously developed (or third party) hardware and software platforms to design the components of distributed embedded real-time systems. Additionally, AOD concepts allow a separate handling of requirement with distinct natures (i.e. functional and non-functional requirements), improving the produced artifacts modularization (e.g. specification model, source code, etc.). In addition, this thesis proposes a code generation tool, which supports an automatic transition from the initial specification phases to the following implementation phases. This tool uses a set of mapping rules, describing how elements at higher abstraction levels are mapped (or transformed) into lower abstraction level elements. In other words, suchmapping rules allow an automatic transformation of the initial specification, which is closer to the application domain, in source code for software and hardware components that can be compiled or synthesized by other tools, obtaining the realization/ implementation of the distributed embedded real-time system.

Diese Diplomarbeit behandelt das Themengebiet der automatischen Erzeugung von grafischen Benutzeroberflächen (GUIs) im Kontext von Webservices. Es geht dabei konkret um einen Editor, mit dem Hinweise zur Generierung von Dialogen erstellt werden können. Diese Hinweise sollen dann von den dialogerzeugenden Anwendungen einbezogen werden, um eine dynamische Interaktion mit Webservices durch beliebige Nutzer ohne dienstspezifische Software zu ermöglichen. Die Arbeit führt in die aktuellen Techniken zur GUI-Generierung ein und stellt Transformationsprinzipien vor, die eine Generierung ausgehend von einem formalen Datenmodell ermöglichen. Dabei müssen mangelnde Modellparameter in Beschreibungen von Webservices manuell ausgeglichen werden (WSGUI-Konzepte). Diese Zielstellung führt zum Entwurf des WSGUI-Editors. Die anschließende Implementierung berücksichtigt darüber hinaus Integrationsaspekte wie die Publizierung von WSGUI-Hinweisen, Einbindung von GUI-Übersetzungen und eine Vorschau auf die zu generierenden Dialoge. Abgeschlossen wird die Arbeit mit einer Bewertung des Editors, aber auch einer Reihe von Vorschlägen zur Vereinfachung ähnlich gelagerter zukünftiger Projekte im Umfeld von Webservices.

Even though there are many software development and project management methodologies available, research and practice both show that IT software development projects still fail, and that the quality of software products does not always meet customers' expectations. There might be multiple causes for such failures, but some of these reasons can be seen to influence or create others. Therefore, the larger the project is, the higher its risk of failure, especially if the teams involved work remotely (distributed and outsourced). This increase in project complexity is considered the motivation for this paper. Similarly, there are other factors that can result in a project's failure and customers' dissatisfaction regarding software quality. All such factors identified by research conducted by organizations specializing in this area are analyzed in order to identify a common root of IT project failures. Once the root causes of these failures have been identified and analyzed, the goal of the Interface based software development methodology is to solve them. The solution offered by an Interface based software development methodology is to improve understanding of software requirements and to describe these requirements with interfaces in an object-oriented way. Interface based software development will support and drive development towards service-oriented architecture (SOA) and component-based development (CBD). The goal of interface based software development is to increase software testability and maintainability and to make it more easily feasible to execute various software development processes in parallel.

Interest for business models and business modeling has increased rapidly since the mid-1990‘s and there are numerous approaches used to create business models. The business model concept has many definitions which can lead to confusion and slower progress in the research and development of business models. A business model ontology (BMO) was created in 2004 where the business model concept was conceptualized based on an analysis of existing literature. A few years later the Business Model Canvas (BMC) was published; a popular business modeling approach providing a high-level, semi-formal approach to create and communicate business models. While this approach is easy to use, the informality and high-level approach can cause ambiguity and it has limited computer-aided support available. In order to propose a solution to address this problem and facilitate the development and communication of Business Model Canvas models, two artifacts are created, demonstrated and evaluated; a structured metamodel for the Business Model Canvas and its implementation in an OMG standards-based modeling tool to provide tool support for BMC modeling.This research is carried out following the design science approach where the artifacts are created to better understand and improve the identified problem. The problem and its background are explicated and the planned artifacts and requirements are outlined. The design and development of the artifacts are detailed and the resulting BMC metamodel is presented as a class diagram in Unified Modeling Language (UML) and implemented to provide tool support for BMC modeling. A demonstration with a business model and an evaluation is performed with expert interviews and informed arguments.The creation of a BMC metamodel exposed some ambiguity in the definition and use of the Business Model Canvas and the importance of graphical presentation and flexibility in the tools used.The evaluation of the resulting artifacts suggests that the artifacts do facilitate the development and communication of the Business Model Canvas models by improving the encapsulation and communication of information in a standardized way and thereby the goals of the research are met.

Modeliais grįsta sistemų architektūra (MDA) yra „Object Management Group“ (OMG) konsorciumo iniciatyva apibrėžti naują požiūrį į programų sistemų kūrimą remiantis modeliais ir automatizuota jų transformacija į programinį kodą. Siekdama standartizuoti šį požiūrį, OMG patvirtino visą eilę standartų, bet esminiai MDA principai ir praktikos glūdi modeliais grįstame sistemų kūrimo stiliuje, kuris yra fundamentalus programų sistemų inžinerijoje. MDA idėjos, pradžioje sukėlusios didelį entuziazmą IT bendruomenėje, ilgainiui peraugo į skepticizmą ir kai kurie autoriai atvirai pradėjo abejoti modeliais grįsto sistemų kūrimo perspektyva. Šiame darbe analizuojamos praktinio MDA taikymo programų sistemų kūrimo procese aspektai ir galimybės, analizuojami galimi sprendimai ir kliūtys, dėl kurių MDA požiūris gali būti sunkiai pritaikomas. Įvairių autorių įvardijami praktiniai MDA taikymo programų sistemų kūrimo procese sunkumai, didelės tam reikalingos investicijos, pastangos ir resursai, tinkamų instrumentų trūkumas, didelė standartų įvairovė ir sudėtingos technologijos iš dalies lėmė išaugusį skepticizmą MDA paradigmai. MDA apibrėžia naujus sistemų kūrimo principus ir standartais apibrėžia technologijas, kurios pagrindžia šiuos principus. Tai neišvengiamai įtakoja patį programų sistemų kūrimo procesą, kuris turi pasipildyti naujomis veiklomis, praktikomis ir technologijomis, kaip kurti sistemas taikant MDA požiūrį. Šiame kontekste būtinas tam tikras pragmatinis požiūris į MDA ir su juo... [toliau žr. visą tekstą]
Model Driven Architecture (MDA) is an approach to using models in software development, which states that models and model-based transformations are a key part of effective automated software development. The Object Management Group (OMG) has defined standards for representing MDA models, but the principles and practice of MDA are rooted in model-based styles of development that have been fundamental to software engineering from its earliest days. Unfortunately, early enthusiasm for Model Driven Architecture (MDA) has dissipated to the point that many people are openly skeptical of the value of any model-driven approach. This paper examines the practical realities of MDA, difficulties and challenges in adopting an MDA approach to software engineering process. While MDA requires additional efforts and high investment to be adopted in software engineering process, it doesn’t provide any means or guidelines for this. This paper argues that to be successful, a pragmatic MDA approach must be executed in context of a sound Enterprise Architecture providing an integrated business architecture and governance structure that enables an organization to respond to business requirements quickly and appropriately.

Diese Diplomarbeit behandelt das Themengebiet der automatischen Erzeugung von grafischen Benutzeroberflächen (GUIs) im Kontext von Webservices. Es geht dabei konkret um einen Editor, mit dem Hinweise zur Generierung von Dialogen erstellt werden können. Diese Hinweise sollen dann von den dialogerzeugenden Anwendungen einbezogen werden, um eine dynamische Interaktion mit Webservices durch beliebige Nutzer ohne dienstspezifische Software zu ermöglichen. Die Arbeit führt in die aktuellen Techniken zur GUI-Generierung ein und stellt Transformationsprinzipien vor, die eine Generierung ausgehend von einem formalen Datenmodell ermöglichen. Dabei müssen mangelnde Modellparameter in Beschreibungen von Webservices manuell ausgeglichen werden (WSGUI-Konzepte). Diese Zielstellung führt zum Entwurf des WSGUI-Editors. Die anschließende Implementierung berücksichtigt darüber hinaus Integrationsaspekte wie die Publizierung von WSGUI-Hinweisen, Einbindung von GUI-Übersetzungen und eine Vorschau auf die zu generierenden Dialoge. Abgeschlossen wird die Arbeit mit einer Bewertung des Editors, aber auch einer Reihe von Vorschlägen zur Vereinfachung ähnlich gelagerter zukünftiger Projekte im Umfeld von Webservices.

Les travaux présentés dans cette thèse s’inscrivent dans le cadre du développement logiciel des systèmes temps réel embarqués. Nous définissons dans ce travail une méthodologie nommée DRIM. Cette méthodologie permet de guider le déploiement des applications temps réel sur différents RTOS en suivant la ligne de l’IDM et en assurant le respect des contraintes de temps après le déploiement. L’automatisation de la méthodologie DRIM montre sa capacité à détecter les descriptions non-implémentables de l’application, réalisées au niveau conception, pour un RTOS donné, ce qui présente l’avantage de réduire le temps de mise sur le marché d’une part et de guider l’utilisateur pour un choix approprié de l’RTOS cible d’autre part
The main purpose of this Phd is to contribute to the software development of real-time embedded systems. We define in this work a methodology named DRIM: Design Refinement toward Implementation Methodology. This methodology aims to guide the deployment of a real-time application on to different RTOS while respecting MDE principals and ensuing that the timing properties are still met after deployment. The automation of DRIM shows its ability to detect non-implementable design models describing the real-time application, on aparticular RTOS, which permits to reduce the time-to-market on the one hand and guide the user to the selection of the appropriate RTOS from the other hand

en català:

Un camp de recerca important dins del paradigma del Computer-Supported Collaborative Learning (CSCL) és la importància en la gestió eficaç de la informació d'esdeveniments generada durant l'activitat de l'aprenentatge col·laboratiu virtual, per a proporcionar coneixement sobre el comportament dels membres del grup. Aquesta visió és especialment pertinent en l'escenari educatiu actual que passa d'un paradigma tradicional - centrat en la figura d'un instructor magistral - a un paradigma emergent que considera els estudiants com actors centrals en el seu procés d'aprenentatge. En aquest nou escenari, els estudiants aprenen, amb l'ajuda de professors, la tecnologia i els altres estudiants, el que potencialment necessitaran per a desenvolupar les seves activitats acadèmiques o professionals futures.
Els principals aspectes a tenir en compte en aquest context són, primer de tot, com dissenyar una plataforma sota el paradigma del CSCL, que es pugui utilitzar en situacions reals d'aprenentatge col·laboratiu complexe i a llarg termini, basades en el model d'aprenentatge de resolució de problemes. I que permet al professor una anàlisi del grup més eficaç així com donar el suport adequat als estudiants quan sigui necessari.
En segon lloc, com extreure coneixement pertinent de la col·laboració per donar consciència i retorn als estudiants a nivell individual i de rendiment del grup, així com per a propòsits d'avaluació.
L'assoliment d'aquests objectius impliquen el disseny d'un model conceptual d'interacció durant l'aprenentatge col·laboratiu que estructuri i classifiqui la informació generada en una aplicació col·laborativa en diferents nivells de descripció. A partir d'aquesta aproximació conceptual, els models computacionals hi donen resposta per a proporcionar una extracció eficaç del coneixement produït per l'individu i per l'activitat del grup, així com la possibilitat d'explotar aquest coneixement com una eina metacognitiva pel suport en temps real i regulat del procés d'aprenentatge col·laboratiu.
A més a més, les necessitats dels entorns CSCL han evolucionat en gran mesura durant els darrers anys d'acord amb uns requisits pedagògics i tecnològics cada cop més exigents. Els entorns d'aprenentatge col·laboratius virtuals ara ja no depenen de grups d'estudiants homogenis, continguts i recursos d'aprenentatge estàtics, ni pedagogies úniques, sinó que exigeixen una forta personalització i un alt grau de flexibilitat. En aquest nou escenari, les organitzacions educatives actuals necessiten estendre's i moure's cap a paradigmes d'ensenyament altament personalitzats, amb immediatesa i constantment, on cada paradigma incorpora el seu propi model pedagògic, el seu propi objectiu d'aprenentatge i incorpora els seus propis recursos educatius específics.
Les demandes de les organitzacions actuals també inclouen la integració efectiva, en termes de cost i temps, de sistemes d'aprenentatge llegats i externs, que pertanyen a altres institucions, departaments i cursos. Aquests sistemes llegats es troben implementats en llenguatges diferents, suportats per plataformes heterogènies i distribuïdes arreu, per anomenar alguns dels problemes més habituals. Tots aquests problemes representen certament un gran repte per la comunitat de recerca actual i futura. Per tant, els propers esforços han d'anar encarats a ajudar a desenvolupadors, recercaires, tecnòlegs i pedagogs a superar aquests exigents requeriments que es troben actualment en el domini del CSCL, així com proporcionar a les organitzacions educatives solucions ràpides i flexibles per a potenciar i millorar el rendiment i resultats de l'aprenentatge col·laboratiu. Aquesta tesi proposa un primer pas per aconseguir aquests objectius.
An important research topic in Computer Supported Collaborative Learning (CSCL) is to explore the importance of efficient management of event information generated from group activity in collaborative learning practices for its further use in extracting and providing knowledge on interaction behavior.
The essential issue here is first how to design a CSCL platform that can be used for real, long-term, complex collaborative problem solving situations and which enables the instructor to both analyze group interaction effectively and provide an adequate support when needed. Secondly, how to extract relevant knowledge from collaboration in order to provide learners with efficient awareness and feedback as regards individual and group performance and assessment. The achievement of these tasks involve the design of a conceptual framework of collaborative learning interaction that structures and classifies the information generated in a collaborative application at several levels of description. Computational models are then to realize this conceptual approach for an efficient management of the knowledge produced by the individual and group activity as well as the possibility of exploiting this knowledge further as a metacognitive tool for real-time coaching and regulating the collaborative learning process.
In addition, CSCL needs have been evolving over the last years accordingly with more and more demanding pedagogical and technological requirements. On-line collaborative learning environments no longer depend on homogeneous groups, static content and resources, and single pedagogies, but high customization and flexibility are a must in this context. As a result, current educational organizations' needs involve extending and moving to highly customized learning and teaching forms in timely fashion, each incorporating its own pedagogical approach, each targeting a specific learning goal, and each incorporating its specific resources.
These entire issues certainly represent a great challenge for current and future research in this field. Therefore, further efforts need to be made that help developers, technologists and pedagogists overcome the demanding requirements currently found in the CSCL domain as well as provide modern educational organizations with fast, flexible and effective solutions for the enhancement and improvement of the collaborative learning performance and outcomes. This thesis proposes a first step toward these goals.

Índex foliat:
The main contribution in this thesis is the exploration of the importance of an efficient management of information generated from group activity in Computer-Supported Collaborative Learning (CSCL) practices for its further use in extracting and providing knowledge on interaction behavior. To this end, the first step is to investigate a conceptual model for data analysis and management so as to identify the many kinds of indicators that describe collaboration and learning and classify them into high-level potential categories of effective collaboration. Indeed, there are more evident key discourse elements and aspects than those shown by the literature, which play an important role both for promoting student participation and enhancing group and individual performance, such as, the impact and effectiveness of students' contributions, among others, that are explored in this work. By making these elements explicit, the discussion model proposed accomplishes high students' participation rates and contribution quality in a more natural and effective way. This approach goes beyond a mere interaction analysis of asynchronous discussion in the sense that it builds a multi-functional model that fosters knowledge sharing and construction, develops a strong sense of community among students, provides tutors with a powerful tool for students' monitoring, discussion regulation, while it allows for peer facilitation through self, peer and group awareness and assessment.
The results of the research described so far motivates the development of a computational system as the translation from the conceptual model into a computer system that implements the management of the information and knowledge acquired from the group activity, so as to be efficiently fed back to the collaboration. The achievement of a generic, robust, flexible, interoperable, reusable computational model that meets the fundamental functional needs shared by any collaborative learning experience is largely investigated in this thesis. The systematic reuse of this computational model permits a fast adaptation to new learning and teaching requirements, such as learning by discussion, by relying on the most advanced software engineering processes and methodologies from the field of software reuse, and thus important benefits are expected in terms of productivity, quality, and cost.
Therefore, another important contribution is to explore and extend suitable software reuse techniques, such as Generic Programming, so as to allow the computational model to be successfully particularized in as many as situations as possible without losing efficiency in the process. In particular, based on domain analysis techniques, a high-level computational description and formalization of the CSCL domain are identified and modeled. Then, different specific-platform developments that realize the conceptual description are provided. It is also explored a certain level of automation by means of advanced techniques based on Service-Oriented Architectures and Web-services while passing from the conceptual specification to the desired realization, which greatly facilitates the development of CSCL applications using this computational model.
Based on the outcomes of these investigations, this thesis contributes with computational collaborative learning systems, which are capable of managing both qualitative and quantitative information and transforming it into useful knowledge for all the implicated parties in an efficient and clear way. This is achieved by both the specific assessment of each contribution by the tutor who supervises the discussion and by rich statistical information about student's participation. This statistical data is automatically provided by the system; for instance, statistical data sheds light on the students' engagement in the discussion forum or how much interest drew the student's intervention in the form of participation impact, level of passivity, proactivity, reactivity, and so on. The aim is to provide both a deeper understanding of the actual discussion process and a more objective assessment of individual and group activity.
This information is then processed and analyzed by means of a multivariate statistical model in order to extract useful knowledge about the collaboration. The knowledge acquired is communicated back to the members of the learning group and their tutor in appropriate formats, thus providing valuable awareness and feedback of group interaction and performance as well as may help identify and assess the real skills and intentions of participants. The most important benefit expected from the conceptual model for interaction data analysis and management is a great improvement and enhancement of the learning and teaching collaborative experiences.
Finally, the possibilities of using distributed and Grid technology to support real CSCL environments are also extensively explored in this thesis. The results of this investigation lead to conclude that the features provided by these technologies form an ideal context for supporting and meeting demanding requirements of collaborative learning applications. This approach is taken one step further for enhancing the possibilities of the computational model in the CSCL domain and it is successfully adopted on an empirical and application basis. From the results achieved, it is proved the feasibility of distributed technologies to considerably enhance and improve the collaborative learning experience. In particular, the use of Grid computing is successfully applied for the specific purpose of increasing the efficiency of processing a large amount of information from group activity log files.

Tese de doutoramento em Tecnologias e Sistemas de Informação
Ubiquitous computing is a research field of computing technology with a growing number of researchers and represents a new direction on the thinking about the integration and use of computers in people’s lives. It aims to achieve a new computing paradigm, one in which there is a high degree of pervasiveness and widespread availability of computers or other IT devices, usually with communication capabilities, in the physical environment. Model-Driven Development (MDD) constitutes an approach to software design and development that strongly focuses and relies on models, through which we build software-platform independent models. Several contributions of MDD are: gains of productivity; concepts closer to domain and reduction of semantic gap; automation and less sensitivity to technological changes; and capture of expert knowledge and reuse. This thesis aims to contribute for the appropriate use of model-based/driven development approaches in software development for pervasive information systems (PIS). This work considers a case study research strategy. It uses two projects developed in the field of ubiquitous and mobile computing that directed their software development to a model-based/driven approach. This thesis describes and analyses the projects. Each one of the project is formalized in a SPEM 2.0 model that presents the main elements of the project. This SPEM model allows perceiving the structure and elements of the project, along with some issues and facts of the project. This thesis conceives a development framework that introduces several useful conceptions. Among these conceptions are the dimensions of development, functional profiles, resources categories, functional profile instances, global and elementary development process. In consonance with this development framework, the thesis proposes a SPEM 2.0 Base Plug-In extension and a development framework pattern to assist in the analysis of the projects. The SPEM 2.0 Base Plug-In extension defines elements that are fundamental to the definition and application of the development framework pattern. The development framework pattern is applied to each of the projects to facilitate the analysis. From the analysis of the projects, the thesis synthesizes a set of guidelines and insight related to the adoption of model-based/driven approaches to pervasive information system development.
A computação ubíqua é um campo de investigação de tecnologia de computação com um número crescente de investigadores e representa uma nova direcção no pensamento sobre a integração e o uso de computadores na vida das pessoas. O objectivo é alcançar um novo paradigma de computação em que há um alto grau de abrangência e ampla disponibilidade de computadores ou outros dispositivos de tecnologias de informação, geralmente com recursos de comunicação, no ambiente físico. Model-Driven Development (MDD), constitui uma abordagem de desenho e desenvolvimento de software que se baseia em modelos, através da qual construímos modelos de plataforma de software independentes. Várias contribuições de MDD são: ganhos de produtividade; conceitos mais próximos ao domínio e à redução do salto semântico; automação e menor sensibilidade às mudanças tecnológicas; captura de conhecimento especializado e reutilização. Esta tese visa contribuir para a adequada utilização de abordagens de desenvolvimento baseadas/conduzidas por modelos no desenvolvimento de software para sistemas de informação “pervasive” (PIS). Esta tese apresenta uma estratégia de investigação de estudo de caso. Usa, como estudos de caso, dois projectos desenvolvidos no campo da computação ubíqua e móvel, e os quais dirigiram o seu desenvolvimento de software para uma abordagem baseada/conduzida por modelos. Esta tese descreve e analisa os projectos; cada um dos projectos é formalizado num modelo SPEM 2.0 que apresenta os elementos principais do projecto. Este modelo SPEM permite perceber a estrutura e os elementos do projecto, juntamente com alguns problemas e factos do projecto. Esta tese concebe uma estrutura de desenvolvimento que apresenta várias concepções úteis. Entre essas concepções estão as dimensões de desenvolvimento, os perfis funcionais, as categorias de recursos, instâncias de perfil funcional, os processos de desenvolvimento global e elementar. Em consonância com esta estrutura de desenvolvimento, a tese propõe uma extensão ao SPEM 2.0 Base Plug- In e um padrão de desenvolvimento para auxiliarem a análise dos projectos. A extensão ao SPEM 2.0 Base Plug-In define elementos que são fundamentais para a definição e aplicação do padrão de estrutura de desenvolvimento. O padrão de estrutura de desenvolvimento é aplicado a cada um dos projectos para facilitar a sua análise. A partir da análise dos projectos, a tese sintetiza um conjunto de directrizes e de ilações relacionadas com a adopção de abordagens MDD para o desenvolvimento de PIS.
Programa Operacional Educacional (PRODEP), e do Instituto Politécnico de Bragança, através da sua Escola Superior de Tecnologia e de Gestão.
Instituto Politécnico de Bragança. Escola Superior de Tecnologia e de Gestão

Die modellgetriebene Entwicklung (MDD) ist ein Ansatz, um formale Modelle automatisiert in ausführbare Software zu übersetzen. Obwohl dieses Vorgehen die Häufigkeit von Fehlern im generierten Quellcode verringert, können immer noch die Ausgangsmodelle fehlerhaft sein. Deshalb sind zusätzliche Prüfverfahren, wie z.B. die Verwendung eines Model Checkers sinnvoll. Er stellt automatisiert sicher, dass ein Modell alle gestellten Anforderungen erfüllt. Das Ziel dieser Arbeit ist daher die Integration eines Model Checkers in den modellgetriebenen Entwicklungsprozess, um die Qualität von Software-Produkten zu verbessern. Zu diesem Zweck wird das sogenannte DSL Verification Framework (DVF) vorgestellt. Es stellt Entwicklern vorgefertigte Sprachkonstrukte zur Verfügung, um die Implementierung von Parsern und Transformatoren zu erleichtern. Des Weiteren berücksichtigt es auch die "State Space Explosion", damit auch größere Modelle verifizierbar bleiben. Um die praktische Nutzung des DVF zu evaluieren, werden zwei Industriefallstudien durchgeführt.

Model-driven software development (MDSD) and component-based software development are both paradigms for reducing complexity and for increasing abstraction and reuse in software development. In this thesis, we aim at combining the advantages of each by introducing methods from component-based development into MDSD. In MDSD, all artefacts that describe a software system are regarded as models of the system and are treated as the central development artefacts. To obtain a system implementation from such models, they are transformed and integrated until implementation code can be generated from them. Models in MDSD can have very different forms: they can be documents, diagrams, or textual specifications defined in different modelling languages. Integrating these models of different formats and abstraction in a consistent way is a central challenge in MDSD. We propose to tackle this challenge by explicitly separating the tasks of defining model components and composing model components, which is also known as distinguishing programming-in-the-small and programming-in-the-large. That is, we promote a separation of models into models for modelling-in-the-small (models that are components) and models for modelling-in-the-large (models that describe compositions of model components). To perform such component-based modelling, we introduce two architectural styles for developing systems with component-based MDSD (CB-MDSD). For CB-MDSD, we require a universal composition technique that can handle models defined in arbitrary modelling languages. A technique that can handle arbitrary textual languages is universal invasive software composition for code fragment composition. We extend this technique to universal invasive software composition for graph fragments (U-ISC/Graph) which can handle arbitrary models, including graphical and textual ones, as components. Such components are called graph fragments, because we treat each model as a typed graph and support reuse of partial models. To put the composition technique into practice, we developed the tool Reuseware that implements U-ISC/Graph. The tool is based on the Eclipse Modelling Framework and can therefore be integrated into existing MDSD development environments based on the framework. To evaluate the applicability of CB-MDSD, we realised for each of our two architectural styles a model-driven architecture with Reuseware. The first style, which we name ModelSoC, is based on the component-based development paradigm of multi-dimensional separation of concerns. The architecture we realised with that style shows how a system that involves multiple modelling languages can be developed with CB-MDSD. The second style, which we name ModelHiC, is based on hierarchical composition. With this style, we developed abstraction and reuse support for a large modelling language for telecommunication networks that implements the Common Information Model industry standard.

Mit dem Wandel des Internets zu einer universellen Softwareplattform sind die Möglichkeiten und Fähigkeiten von Webanwendungen zwar rasant gestiegen. Gleichzeitig gestaltet sich ihre Entwicklung jedoch zunehmend aufwändig und komplex, was dem Wunsch nach immer kürzeren Entwicklungszyklen für möglichst situative, bedarfsgerechte Lösungen entgegensteht. Bestehende Ansätze aus Forschung und Technik, insbesondere im Umfeld der serviceorientierten Architekturen und Mashups, werden diesen Problemen bislang nicht ausreichend gerecht. Deshalb werden in dieser Dissertation neue Konzepte für die modellgetriebene Entwicklung und Bereitstellung von Webanwendungen vorgestellt. Die zugrunde liegende Idee besteht darin, das Paradigma der Serviceorientierung auf die Präsentationsebene zu erweitern. So sollen erstmals – neben Daten- und Geschäftslogik – auch Teile der Anwendungsoberfläche in Form wiederverwendbarer Komponenten über Dienste bereitgestellt werden. Anwendungen sollen somit über alle Anwendungsebenen hinweg nach einheitlichen Prinzipien „komponiert“ werden können. Den ersten Schwerpunkt der Arbeit bilden die entsprechenden universellen Modellierungskonzepte für Komponenten und Kompositionen. Sie erlauben u. a. die plattformunabhängige Beschreibung von Anwendungen als Komposition der o. g. Komponenten. Durch die Abstraktion und entsprechende Autorenwerkzeuge wird die Entwicklung so auch für Domänenexperten bzw. Nicht-Programmierer möglich. Der zweite Schwerpunkt liegt auf dem kontextadaptiven Integrationsprozess von Komponenten und der zugehörigen, serviceorientierten Referenzarchitektur. Sie ermöglichen die dynamische Suche, Bindung und Konfiguration von Komponenten, d. h. auf Basis der o. g. Abstraktionen können genau die Anwendungskomponenten geladen und ausgeführt werden, die für den vorliegenden Nutzer-, Nutzungs- und Endgerätekontext am geeignetsten sind. Der dritte Schwerpunkt adressiert die Kontextadaptivität der kompositen Anwendungen in Form von Konzepten zur aspektorientierten Definition von adaptivem Verhalten im Modell und dessen Umsetzung zur Laufzeit. In Abhängigkeit von Kontextänderungen können so Rekonfigurationen von Komponenten, ihr Austausch oder Veränderungen an der Komposition, z.B. am Layout oder dem Datenfluss, automatisch durchgesetzt werden. Alle vorgestellten Konzepte wurden durch prototypische Implementierungen praktisch untermauert. Anhand diverser Anwendungsbeispiele konnten ihre Validität und Praktikabilität – von der Modellierung im Autorenwerkzeug bis zur Ausführung und dynamischen Anpassung – nachgewiesen werden. Die vorliegende Dissertation liefert folglich eine Antwort auf die Frage, wie zukünftige Web- bzw. Mashup-Anwendungen zeit- und kostengünstig entwickelt sowie zuverlässig und performant ausgeführt werden können. Die geschaffenen Konzepte bilden gleichermaßen die Grundlage für eine Vielzahl an Folgearbeiten.:Verzeichnisse vi Abbildungsverzeichnis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Verzeichnis der Codebeispiele . . . . . . . . . . . . . . . . . . . . . . . . . . ix Abkürzungsverzeichnis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x 1 Einleitung 1 1.1 Problemdefinition, Thesen und Forschungsziele . . . . . . . . . . . . . . 3 1.1.1 Probleme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1.2 Thesen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1.1.3 Forschungsziele . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.2 Abgrenzung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3 Aufbau der Arbeit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2 Grundlagen, Szenarien und Herausforderungen 12 2.1 Grundlagen und Begriffsklärung . . . . . . . . . . . . . . . . . . . . . . . 13 2.1.1 Komposite und serviceorientierte Webanwendungen . . . . . . . 13 2.1.2 Mashups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.1.3 Modellgetriebene Software-Entwicklung . . . . . . . . . . . . . . 17 2.1.4 Kontext und kontextadaptive Webanwendungen . . . . . . . . . 18 2.2 Szenarien und Problemanalyse . . . . . . . . . . . . . . . . . . . . . . . 20 2.2.1 Dienstkomposition zur Reiseplanung . . . . . . . . . . . . . . . . . 20 2.2.2 Interaktive Aktienverwaltung . . . . . . . . . . . . . . . . . . . . . 22 2.2.3 Adaptive Touristeninformation . . . . . . . . . . . . . . . . . . . . 23 2.3 Anforderungen und Kriterien der Analyse . . . . . . . . . . . . . . . . . . 25 2.3.1 Anforderungen an Komponenten- und Kompositionsmodell . . . 25 2.3.2 Anforderungen an die Laufzeitumgebung . . . . . . . . . . . . . 27 3 Stand der Forschung und Technik 30 3.1 SOA und Dienstkomposition zur Interaktion mit Diensten . . . . . . . . . 31 3.1.1 Statische Dienstkomposition . . . . . . . . . . . . . . . . . . . . . . 32 3.1.2 Dynamische Dienstauswahl und -Komposition . . . . . . . . . . . 33 3.1.3 Adaptionskonzepte für Dienstkompositionen . . . . . . . . . . . . 45 3.1.4 Interaktions- und UI-Konzepte für Dienstkompositionen . . . . . . 48 3.2 Web Engineering - Entwicklung interaktiver adaptiver Webanwendungen 50 3.2.1 Entwicklung von Hypertext- und Hypermedia-Anwendungen . . 51 3.2.2 Entwicklung von Mashup-Anwendungen . . . . . . . . . . . . . . 54 3.3 Zusammenfassung und Diskussion der Defizite existierender Ansätze . . 67 3.3.1 Probleme und Defizite aus dem Bereich der Dienstkomposition . 67 3.3.2 Probleme und Defizite beim Web- und Mashup-Engineering . . . 69 4 Universelle Komposition adaptiver Webanwendungen 73 4.1 Grundkonzept und Rollenmodell . . . . . . . . . . . . . . . . . . . . . . 74 4.2 Modellgetriebene Entwicklung kompositer Mashups . . . . . . . . . . . 75 4.2.1 Universelles Komponentenmodell . . . . . . . . . . . . . . . . . . 76 4.2.2 Belangorientiertes Kompositionsmodell . . . . . . . . . . . . . . . 76 4.3 Dynamische Integration und Laufzeitumgebung . . . . . . . . . . . . . 78 4.3.1 Kontextsensitiver Integrationsprozess für Mashup-Komponenten . 79 4.3.2 Referenzarchitektur zur Komposition und Ausführung . . . . . . . 80 4.3.3 Unterstützung von adaptivem Laufzeitverhalten in Mashups . . . 81 5 Belangorientierte Modellierung adaptiver, kompositer Webanwendungen 83 5.1 Ein universelles Komponentenmodell für Mashup-Anwendungen . . . . 84 5.1.1 Grundlegende Eigenschaften und Prinzipien . . . . . . . . . . . . 84 5.1.2 Komponententypen . . . . . . . . . . . . . . . . . . . . . . . . . . 86 5.1.3 Beschreibung von Komponenten . . . . . . . . . . . . . . . . . . 87 5.1.4 Nutzung der Konzepte zur Komponentenentwicklung . . . . . . . 99 5.2 Ein belangorientiertes Metamodell für interaktive Mashup-Anwendungen 100 5.2.1 Conceptual Model – Modellierung der Anwendungskonzepte . . 102 5.2.2 Communication Model – Spezifikation von Daten- und Kontrollfluss 107 5.2.3 Layout Model – Visuelle Anordnung von UI-Komponenten . . . . 114 5.2.4 Screenflow Model – Definition von Navigation und Sichten . . . . 115 5.3 Modellierung von adaptivem Verhalten . . . . . . . . . . . . . . . . . . 117 5.3.1 Adaptionstechniken für komposite Webanwendungen . . . . . . 117 5.3.2 Adaptivity Model – Modellierung von Laufzeitadaptivität . . . . . 119 5.4 Ablauf und Unterstützung bei der Modellierung . . . . . . . . . . . . . . 126 5.5 Zusammenfassung und Diskussion . . . . . . . . . . . . . . . . . . . . . . 128 6 Kontextsensitiver Integrationsprozess und Kompositionsinfrastruktur 132 6.1 Ein kontextsensitiver Integrationsprozess zur dynamischen Bindung von Mashup-Komponenten . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 6.1.1 Modellinterpretation oder -transformation . . . . . . . . . . . . . . 134 6.1.2 Suche und Matching . . . . . . . . . . . . . . . . . . . . . . . . . 135 6.1.3 Rangfolgebildung . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 6.1.4 Auswahl und Integration . . . . . . . . . . . . . . . . . . . . . . . . 145 6.2 Kompositionsinfrastruktur und Laufzeitumgebung . . . . . . . . . . . . . 146 6.2.1 Verwaltung von Komponenten und Domänenwissen . . . . . . . 146 6.2.2 Aufbau der Laufzeitumgebung (MRE) . . . . . . . . . . . . . . . . 148 6.2.3 Dynamische Integration und Verwaltung von Komponenten . . . 151 6.2.4 Kommunikationsinfrastruktur und Mediation . . . . . . . . . . . . . 155 6.3 Unterstützung von Adaption zur Laufzeit . . . . . . . . . . . . . . . . . . 162 6.3.1 Kontexterfassung, -modellierung und -verwaltung . . . . . . . . . 163 6.3.2 Ablauf der dynamischen Adaption . . . . . . . . . . . . . . . . . 168 6.3.3 Dynamischer Austausch von Komponenten . . . . . . . . . . . . 170 6.4 Zusammenfassung und Diskussion . . . . . . . . . . . . . . . . . . . . . . 174 7 Umsetzung und Validierung der Konzepte 178 7.1 Realisierung der Modellierungsmittel . . . . . . . . . . . . . . . . . . . . 179 7.1.1 Komponentenbeschreibung in XML und OWL . . . . . . . . . . . 179 7.1.2 EMF-basiertes Kompositionsmodell . . . . . . . . . . . . . . . . . . 180 7.1.3 Modelltransformationen . . . . . . . . . . . . . . . . . . . . . . . . 182 7.1.4 Modellierungswerkzeug . . . . . . . . . . . . . . . . . . . . . . . . 183 7.2 Realisierung der Kompositions- und Laufzeitumgebung . . . . . . . . . . 185 7.2.1 Semantische Verwaltung und Discovery . . . . . . . . . . . . . . 185 7.2.2 Kompositions- bzw. Laufzeitumgebungen . . . . . . . . . . . . . . 192 7.2.3 Kontextverwaltung und Adaptionsmechanismen . . . . . . . . . 201 7.3 Validierung und Diskussion anhand der Beispielszenarien . . . . . . . . . 210 7.3.1 Reiseplanung mit TravelMash . . . . . . . . . . . . . . . . . . . . . 211 7.3.2 Aktienverwaltung mit StockMash . . . . . . . . . . . . . . . . . . . 214 7.3.3 Adaptive Touristeninformation mit TravelGuide . . . . . . . . . . . 216 7.3.4 Weitere Prototypen . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 7.4 Zusammenfassung und Diskussion . . . . . . . . . . . . . . . . . . . . . . 219 8 Zusammenfassung, Diskussion und Ausblick 226 8.1 Zusammenfassung der Kapitel und ihrer Beiträge . . . . . . . . . . . . . 227 8.2 Diskussion und Bewertung . . . . . . . . . . . . . . . . . . . . . . . . . . 231 8.2.1 Wissenschaftliche Beiträge . . . . . . . . . . . . . . . . . . . . . . 231 8.2.2 Einschränkungen und Grenzen . . . . . . . . . . . . . . . . . . . . 236 8.3 Laufende und zukünftige Arbeiten . . . . . . . . . . . . . . . . . . . . . 238 Anhänge 242 A.1 Komponentenbeschreibung in SMCDL . . . . . . . . . . . . . . . . . . . 242 A.2 Komponentenmodell in Form der MCDO . . . . . . . . . . . . . . . . . . 243 A.3 Kompositionsmodell in EMF . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Verzeichnis eigener Publikationen 246 Webreferenzen 249 Literaturverzeichnis 253