El propósito de esta Tesis es llevar a cabo un proceso en el que se aplique la práctica de la integración continua en un desarrollo de software dirigido por modelos de forma eficiente, mediante el cual los desarrollos de software puedan beneficiarse conjuntamente de las mejoras y ventajas que proporcionan la aproximación de desarrollo de la ingeniería dirigida por modelos y la práctica de la integración continua. La aproximación de la ingeniería dirigida por modelos es el último salto natural de la ingeniería del software en cuanto a la búsqueda de métodos de desarrollo que elevan el nivel de abstracción hasta el punto en el que los expertos de un dominio de conocimiento, ajenos al mundo informático, son capaces de guiar y cambiar la lógica de los sistemas informáticos. La práctica de la integración continua es una recomendación de las principales metodologías de desarrollo, que tiene como objetivo la realización de integraciones automáticas del software en etapas tempranas del desarrollo, ofreciendo ventajas como la reducción del riesgo intrínseco que, dado su carácter temporal y único, tienen todos los proyectos. Con la unión de la ingeniería dirigida por modelos y de la práctica de la integración continua se busca ofrecer, a los equipos de desarrollo que trabajan utilizando algún tipo de iniciativa de la ingeniería dirigida por modelos, la posibilidad de integrar de forma continua y distribuida sus desarrollos. Al mismo tiempo, los clientes, verdaderos expertos del dominio de conocimiento en su ámbito de negocio, se benefician del aumento del nivel de abstracción de las técnicas de desarrollo para que ellos mismos, y de forma transparente, sean capaces de modificar su propio sistema informático sin la ayuda de personal técnico ajeno a su negocio, ahorrando así tiempo y costes. Para cumplir con el objetivo de esta Tesis doctoral se construye un prototipo que salva los impedimentos actuales que no permiten la unión entre estos dos nuevos activos de la ingeniería del software. Los principales problemas encontrados están relacionados con la selección de una iniciativa de desarrollo apropiada, los sistemas de control de versiones especialmente adaptados para trabajar con modelos, la generación incremental de artefactos a partir de modelos y la adaptación a las herramientas actuales de integración continua de forma optimizada. La separación del trabajo realizado en diferentes bloques permite ofrecer soluciones de forma tanto aislada como en conjunto, dando lugar a un trabajo iterativo e incremental de comienzo a fin. Para analizar las ventajas que ofrece la propuesta de este trabajo frente a otras posibilidades de desarrollo, se realiza una evaluación mediante la creación de diferentes casos de prueba en los que la medición de diferentes parámetros ofrecen una estimación numérica de las ventajas reales obtenidas. El análisis descriptivo, el contraste de hipótesis y las técnicas de regresión permiten una mejor interpretación de los resultados. Finalmente, se define el proceso, objetivo último de este trabajo, mediante la respuesta a diferentes preguntas planteadas, que facilitan su comprensión y entendimiento. / The purpose of this Thesis is to create a process in which the continuous integration practice can be applied to a model-driven software development in an e ective way, through which software developments can bene t jointly and simultaneously from the improvements and advantages provided by the model-driven engineering development approach and the continuous integration practice. The model-driven engineering approach is the last natural step of software engineering in the search for development approaches that raise the level of abstraction to the point that experts in a domain of knowledge, outside the computer world, are able to guide and change the logic of computer systems. The continuous integration practice is a recommendation of the most widely accepted development methodologies that aims to carry out automatic software integrations in early stages of development, o ering bene ts such as reducing the inherent risk that, given its unique nature, every project has. By merging the model-driven engineering and the continuous integration practice, the aim is to provide to development teams that work using some kind of model-driven engineering initiative, the possibility to integrate their developments in a continuous and distributed way. At the same time, customers, the real experts in the domain of knowledge in their eld of business, can bene t from the increased level of abstraction in developing techniques. Thus, they, in a transparent manner, are able to modify their own computer system without the help of external technical sta , so saving time and costs. To meet the objective of this Thesis, a prototype which saves all the current constraints that do not allow the union between these two new tools of software engineering is build. The main problems found were related to the selection of an appropriate development initiative, the version control systems specially adapted to working with models, the incremental generation of artifacts from models, and the optimized adaptation to existing continuous integration tools. The separation of work in di erent blocks can provide solutions, both in isolation or in conjunction, resulting in an iterative and incremental work from beginning to end. To analyze the bene ts of the proposal in this work compared to other development possibilities, an evaluation is performed by creating di erent test cases in which the measurement of di erent parameters can give a numerical estimate of the real bene ts obtained. The descriptive analysis, the hypothesis testing, and regression techniques allow a better interpretation of results. Finally, the process, the main objective of this work, is de ned by answering various questions posed to facilitate its comprehension and understanding.

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.

Submitted by Johnny Rodrigues (johnnyrodrigues@ufcg.edu.br) on 2018-08-16T14:52:23Z No. of bitstreams: 1 CAMILA DE LUNA MACIEL - DISSERTAÇÃO PPGCC 2010..pdf: 7464974 bytes, checksum: 6d1dbd48857a3fa1c75047b6ab0a2016 (MD5) / Made available in DSpace on 2018-08-16T14:52:23Z (GMT). No. of bitstreams: 1 CAMILA DE LUNA MACIEL - DISSERTAÇÃO PPGCC 2010..pdf: 7464974 bytes, checksum: 6d1dbd48857a3fa1c75047b6ab0a2016 (MD5) Previous issue date: 2010-08-06 / CNPq / Dentro da Engenharia de Software, novos paradigmas de desenvolvimento vêm surgindo no intuito de oferecer uma maior produtividade sem perda de qualidade aos softwares desenvolvidos. Um desses paradigmas é o MDD (Model-Driven Development), cuja principal finalidade é a introdução de modelos rigorosos durante todo o processo de desenvolvimento de software oferecendo, dentre outras vantagens, a geração automática de código a partir dos modelos. Contudo, mesmo em processos de desenvolvimento que seguem este paradigma, a atividade de teste de software ainda é fundamental, principalmente teste de integração, cujo objetivo é verificar que os componentes do software, implementados e testados individualmente, provêem a funcionalidade pretendida quando colocados para interagir uns com os outros. Embora classes individuais possam funcionar corretamente, várias novas faltas podem surgir quando os componentes são integrados. No entanto, em teste de integração, dependendo da complexidade do sistema, o número de casos de teste pode ser muito grande. Nesse contexto, o uso de padrões de teste, ou seja, estratégias que já foram utilizadas e se mostraram efetivas em teste de software, pode guiar a escolha de casos de teste mais efetivos e adequados dentre um número muito grande de possíveis casos de teste. Este trabalho tem como objetivo principal fornecer uma nova abordagem de teste de integração, definida dentro de um processo integrado de desenvolvimento e teste dirigidos por modelos (MDD/MDT - Model-Driven Testing), para a geração automática de casos de teste a partir de modelos, utilizando padrões de teste como base para o processo de geração. Para automatizar este processo, foi desenvolvida uma ferramenta baseada em transformações entre modelos segundo práticas da MDA (Model-DrivenArchitecture). Além disso, a abordagem proposta utiliza o perfil de teste da UML para a documentação de todos os artefatos de teste gerados. Adicionalmente, estudos experimentais preliminares foram realizados no intuito de avaliar a abordagem e, consequentemente, a ferramenta de suporte desenvolvida. / Within the Software Engineering, new development paradigms are emerging in order to offer greater productivity without sacrificing quality to the developed software. MDD (Model-Driven Development) is one of these paradigms, whose main purpose is to introduce rigorous models along all the software development process offering, among other advantages, automatic code generation from models. However, even in development processes that follow this paradigm, the software testing activity is still essential, especially integration testing, whose purpose is to verify that the software components, implemented and tested separately, provide the desired functionality when placed to interact with each other. While individual components may function correctly, several new faults can arise when the components are integrated. However, in integration testing, depending on the system complexity, the number of test cases can be very large. In this context, the use of test patterns, i. e., strategies that have been used and proved effective in software testing, can guide the user at choosing test cases more effective and appropriate among a very large number of possible cases test. The main objective of this work is to propose a new approach to integration testing, defined with in an integrated model driven development and test process (MDD/MDT - Model-Driven Testing) for automatically generating test case from models adopting test patterns as basis for the generation process. To automate this process, we have developed a tool based on model transformations according to MDA (Model-Driven Architecture) practices. Furthermore, the proposal approach uses the UML testing profile to document all generated test artifacts. Additionally, preliminary experimental case studies were performed in order to evaluate the proposed approach and hence the developed tool support.

Made available in DSpace on 2016-08-17T14:53:04Z (GMT). No. of bitstreams: 1 Simone Melo.pdf: 2880047 bytes, checksum: c872dc02c29d736c1cca896ec5a17ea2 (MD5) Previous issue date: 2007-05-02 / In this work, we develop a medical information system to support medical diagnosis based on an approach oriented to models, in which the system allows sharing of information between physically scattered specialists. The development of a medical information system is done using MDA (Model Drive Architecture) in which the PIM (Platform Independent Model) is created with UML (Unified Modeling Language), and the PSMs (Platform Specific Model) is done according to Web Services Platforms. To implement this system, we devised meta model s for the Web Services, JWSDP (Java Web Services Developement Pack) and WSOracle. Thus, we provide definitions of transformation of UML for the Web Services, JWSDP and WSOracle. The development of the system puts in evidence the process of transformation of PIM for PSM used in MDA. / Neste trabalho, desenvolvemos um sistema de informação médica de auxílio no diagnóstico médico, baseado em uma abordagem orientada a modelos, no qual o sistema permite o compartilhamento de informações entre especialistas fisicamente dispersos. O desenvolvimento do sistema de informação médica foi feito usando MDA (Arquitetura Dirigida a Modelo) em que o PIM (Modelo Independente da Plataforma) foi feito conforme a UML (Linguagem de Modelagem Unificada), e os PSMs (Modelos Específico da Plataforma) conforme as Plataformas dos Web Services. Para implementar este sistema de informação médica, provemos metamodelos para os Web Services, JWSDP (Java Web Services Developer Pack) e WSOracle. Assim, provemos definições de transformação de UML para os Web Services, JWSDP e WSOracle. O desenvolvimento do sistema coloca em evidência o processo de transformação de PIM para PSM, utilizado em MDA.

It is widely recognised that information and communication technologies development is a risky activity. Despite the advances in software engineering, many software development projects fail to satisfy the clients' needs, to deliver on time or to stay within budget. Among the various factors that are considered to cause failure, an inadequate requirements practice stands out. Model-driven development is a relatively recent paradigm with the potential to solve some of the dragging problems of software development. Models play a paramount role in model-driven development: several modelling layers allow defining views of the system under construction at different abstraction levels, and model transformations facilitate the transition from one layer to the other. However, how to effectively integrate requirements engineering within model-driven development is still an open research challenge. This thesis integrates Communication Analysis, a communication-oriented business process modelling and requirements engineering method for information systems development, and the OO Method, an object-oriented model-driven software development method provides automatic software generation from conceptual models. We first provide a detailed specification of Communication Analysis intended to facilitate the integration; among other improvements to the method, we build an ontology-based set of concept definitions in which to ground the method, we provide precise methodological guidelines, we create a metamodel for the modelling languages included in the method, and we provide tools to support the creation of Communication Analysis requirements models. Then we perform the integration by providing a technique to systematically derive OO-Method conceptual models from Communication Analysis requirements models. The derivation technique is offered in two flavours: a set of rules to be manually applied by a human analyst, and an ATL model transformation that automates this task. / España Cubillo, S. (2011). METHODOLOGICAL INTEGRATION OF COMMUNICATION ANALYSIS INTO A MODEL-DRIVEN SOFTWARE DEVELOPMENT FRAMEWORK [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/14572 / Palancia

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.

The Master's thesis presents specification, analyze and design phase of software development. The most stress is putted on Model Driven Development. It contains brief description of almost all UML 2.0 diagrams (use case diagram, class diagram, sequence diagram, activity diagram, state chart, component diagram and deployment diagram). Those principles have been extended to executable UML which can be used for model-driven software architecture. The design of such architecture is one of the current projects of Faculty of Information Technology, BUT. The part of that project is statechart simulator. The thesis discusses whole design of state chart simulator system step by step. It starts with specification, walk thought use case diagram and class diagram to collaboration diagram. In the last chapter, we mention the biggest implementation problems and specificities of Squeak Smalltalk programming language. Finally, it considers possibilities for extension and it evaluates results.

Business organisations today are faced with the complex problem of dealing with evolution in their software information systems. This effectively concerns the accommodation and facilitation of change, in terms of both changing user requirements and changing technological requirements. An approach that uses the software development life-cycle as a vehicle to study the problem of evolution is adopted. This involves the stages of requirements analysis, system specification, design, implementation, and finally operation and maintenance. The problem of evolution is one requiring proactive as well as reactive solutions for any given application domain. Measuring evolvability in conceptual models and the specification of changing requirements are considered. However, even "best designs" are limited in dealing with unanticipated evolution, and require implementation phase paradigms that can facilitate an evolution correctly (semantic integrity), efficiently (minimal disruption of services) and consistently (all affected parts are consistent following the change). These are also discussed / Computing / M. Sc. (Information Systems)

Mit der stetigen Konsolidierung der Web Service Standards vollzieht sich in der Diskussion zu serviceorientierten Architekturen ein Wechsel weg von der Implementierung und dem Deployment von Services hin zum Service Management. Die Indikatoren: Anzahl der Standardisierungsanfragen und die Menge großer Forschungsprogramme in diesem Bereich sind evident für einen wachsenden Bedarf an Managementmethoden für die Abbildung von Geschäftsanforderungen auf Servicekompositionen. Die Verwendung von semiformalen Modellen sowie die verteilte Entwicklung von SOA Services machen eine an Konventionen orientierte konstruktive Einschränkung der Freiheitsgrade bei der Prozess- und Servicemodellierung notwendig. In dieser Arbeit wird eine generische Methode vorgestellt, welche durch die Einführung von „Beschreibungsrahmen“ (Description Kits) sowohl eine Einschränkung der Modellierungsfreiheit in Bezug auf natürlichsprachliche Aspekte in fachkonzeptuellen Modellen erlaubt, als auch eine restriktive Benutzung bestehender Modellierungssprachen ermöglicht. Als Anwendungsfall wird die Konfiguration serviceorientierter Architekturen diskutiert. - (Die Dissertation ist veröffentlicht im Logos Verlag Berlin GmbH, http://www.logos-verlag.de, ISBN: 978-3-8325-2402-9) / With Service-oriented Architectures (SOA) companies are facing a paradigm shift towards services as the key unit of their enterprise architectures. An exploitation of the potential of Service-oriented Architectures is up to the applicability of semi-formal business models for a transformation into service compositions. However, several conceptual shortcomings prevent semi-formal models from being a suitable resource of an automated transformation process. Problems result from a multitude of modeling aims, objects, and procedures. Enhancements in order to solve these problems require both systematic preparation, and a methodical approach. This thesis provides a modeling method for business process-oriented SOA design using a meta-model based approach. An integrated modeling environment gives an overview of business requirements and allows appropriate assignment of SOA services to the business functions at the same time. The research refers to the example of process-oriented analysis and optimization of administrative procedures in German universities.

Business organisations today are faced with the complex problem of dealing with evolution in their software information systems. This effectively concerns the accommodation and facilitation of change, in terms of both changing user requirements and changing technological requirements. An approach that uses the software development life-cycle as a vehicle to study the problem of evolution is adopted. This involves the stages of requirements analysis, system specification, design, implementation, and finally operation and maintenance. The problem of evolution is one requiring proactive as well as reactive solutions for any given application domain. Measuring evolvability in conceptual models and the specification of changing requirements are considered. However, even "best designs" are limited in dealing with unanticipated evolution, and require implementation phase paradigms that can facilitate an evolution correctly (semantic integrity), efficiently (minimal disruption of services) and consistently (all affected parts are consistent following the change). These are also discussed / Computing / M. Sc. (Information Systems)