Spelling suggestions: "subject:"model deriven"" "subject:"model dcdriven""
401 |
Transformation by exampleKessentini, Marouane 02 1900 (has links)
La transformation de modèles consiste à transformer un modèle source en un modèle cible conformément à des méta-modèles source et cible. Nous distinguons deux types de transformations. La première est exogène où les méta-modèles source et cible représentent des formalismes différents et où tous les éléments du modèle source sont transformés. Quand elle concerne un même formalisme, la transformation est endogène. Ce type de transformation nécessite généralement deux étapes : l’identification des éléments du modèle source à transformer, puis la transformation de ces éléments. Dans le cadre de cette thèse, nous proposons trois principales contributions liées à ces problèmes de transformation. La première contribution est l’automatisation des transformations des modèles. Nous proposons de considérer le problème de transformation comme un problème d'optimisation combinatoire où un modèle cible peut être automatiquement généré à partir d'un nombre réduit d'exemples de transformations. Cette première contribution peut être appliquée aux transformations exogènes ou endogènes (après la détection des éléments à transformer). La deuxième contribution est liée à la transformation endogène où les éléments à transformer du modèle source doivent être détectés. Nous proposons une approche pour la détection des défauts de conception comme étape préalable au refactoring. Cette approche est inspirée du principe de la détection des virus par le système immunitaire humain, appelée sélection négative. L’idée consiste à utiliser de bonnes pratiques d’implémentation pour détecter les parties du code à risque. La troisième contribution vise à tester un mécanisme de transformation en utilisant une fonction oracle pour détecter les erreurs. Nous avons adapté le mécanisme de sélection négative qui consiste à considérer comme une erreur toute déviation entre les traces de transformation à évaluer et une base d’exemples contenant des traces de transformation de bonne qualité. La fonction oracle calcule cette dissimilarité et les erreurs sont ordonnées selon ce score. Les différentes contributions ont été évaluées sur d’importants projets et les résultats obtenus montrent leurs efficacités. / Model transformations take as input a source model and generate as output a target model. The source and target models conform to given meta-models. We distinguish between two transformation categories. Exogenous transformations are transformations between models expressed using different languages, and the whole source model is transformed. Endogenous transformations are transformations between models expressed in the same language. For endogenous transformations, two steps are needed: identifying the source model elements to transform and then applying the transformation on them. In this thesis, we propose three principal contributions. The first contribution aims to automate model transformations. The process is seen as an optimization problem where different transformation possibilities are evaluated and, for each possibility, a quality is associated depending on its conformity with a reference set of examples. This first contribution can be applied to exogenous as well as endogenous transformation (after determining the source model elements to transform). The second contribution is related precisely to the detection of elements concerned with endogenous transformations. In this context, we present a new technique for design defect detection. The detection is based on the notion that the more a code deviates from good practice, the more likely it is bad. Taking inspiration from artificial immune systems, we generate a set of detectors that characterize the ways in which a code can diverge from good practices. We then use these detectors to determine how far the code in the assessed systems deviates from normality. The third contribution concerns transformation mechanism testing. The proposed oracle function compares target test cases with a base of examples containing good quality transformation traces, and assigns a risk level based on the dissimilarity between the two. The traces help the tester understand the origin of an error. The three contributions are evaluated with real software projects and the obtained results confirm their efficiencies.
|
402 |
Software Visualization in 3DMüller, Richard 20 April 2015 (has links) (PDF)
The focus of this thesis is on the implementation, the evaluation and the useful application of the third dimension in software visualization. Software engineering is characterized by a complex interplay of different stakeholders that produce and use several artifacts. Software visualization is used as one mean to address this increasing complexity. It provides role- and task-specific views of artifacts that contain information about structure, behavior, and evolution of a software system in its entirety. The main potential of the third dimension is the possibility to provide multiple views in one software visualization for all three aspects. However, empirical findings concerning the role of the third dimension in software visualization are rare. Furthermore, there are only few 3D software visualizations that provide multiple views of a software system including all three aspects. Finally, the current tool support lacks of generating easy integrateable, scalable, and platform independent 2D, 2.5D, and 3D software visualizations automatically.
Hence, the objective is to develop a software visualization that represents all important structural entities and relations of a software system, that can display behavioral and evolutionary aspects of a software system as well, and that can be generated automatically.
In order to achieve this objective the following research methods are applied. A literature study is conducted, a software visualization generator is conceptualized and prototypically implemented, a structured approach to plan and design controlled experiments in software visualization is developed, and a controlled experiment is designed and performed to investigate the role of the third dimension in software visualization.
The main contributions are an overview of the state-of-the-art in 3D software visualization, a structured approach including a theoretical model to control influence factors during controlled experiments in software visualization, an Eclipse-based generator for producing automatically role- and task-specific 2D, 2.5D, and 3D software visualizations, the controlled experiment investigating the role of the third dimension in software visualization, and the recursive disk metaphor combining the findings with focus on the structure of software including useful applications of the third dimension regarding behavior and evolution.
|
403 |
A Methodology for Building Service-Oriented Applications in the Presence of Non-Functional PropertiesSouza Neto, Pl?cido Ant?nio de 11 December 2012 (has links)
Made available in DSpace on 2014-12-17T15:47:00Z (GMT). No. of bitstreams: 1
PlacidoASN_TESE.pdf: 5575988 bytes, checksum: b29fc882ea45700b3c27d134527a79ed (MD5)
Previous issue date: 2012-12-11 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / This thesis presents ⇡SOD-M (Policy-based Service Oriented Development Methodology),
a methodology for modeling reliable service-based applications using policies. It proposes a
model driven method with: (i) a set of meta-models for representing non-functional constraints
associated to service-based applications, starting from an use case model until a service composition
model; (ii) a platform providing guidelines for expressing the composition and the
policies; (iii) model-to-model and model-to-text transformation rules for semi-automatizing
the implementation of reliable service-based applications; and (iv) an environment that implements
these meta-models and rules, and enables the application of ⇡SOD-M. This thesis
also presents a classification and nomenclature for non-functional requirements for developing
service-oriented applications. Our approach is intended to add value to the development of
service-oriented applications that have quality requirements needs. This work uses concepts
from the service-oriented development, non-functional requirements design and model-driven
delevopment areas to propose a solution that minimizes the problem of reliable service modeling.
Some examples are developed as proof of concepts / Esta tese apresenta ⇡SOD-M (Policy-based Service Oriented Development Methodology),
uma metodologia para a modelagem de aplica??es orientadas a servi?os a qual usa Pol?ticas de
qualidade. O trabalho prop?e um m?todo orientado a modelos para desenvolvimento de aplica??es
confi?veis. ⇡SOD-M consiste de: (i) um conjunto de meta-modelos para representa??o
de requisitos n?o-funcionais associados a servi?os nos diferentes n?veis de modelagem, a partir
de um modelo de caso de uso at? um modelo de composi??o de servi?o, (ii) um meta-modelo de
plataforma espec?fica que representa a especifica??o das composi?oes e as pol?ticas, (iii) regras
de transforma??o model-to-model e model-to-text para semi-automatizar a implementa??o de
composi?oes de servi?os confi?veis, e (iv) um ambiente que implementa estes meta-modelos e
regras, representando assim aspectos transversais e limita??es associadas a servi?os, que devem
ser respeitados. Esta tese tamb?m apresenta uma classifica??o e nomenclatura de requisitos
n?o-funcionais para o desenvolvimento de aplica??es orientadas a servi?os. Nossa abordagem
visa agregar valor ao desenvolvimento de aplica??es orientadas a servi?os que t?m necessidades
de garantias de requisitos de qualidade. Este trabalho utiliza conceitos das ?reas de desenvolvimento
orientado a servi?os, design de requisitos n?o-funcionais e desenvolvimento dirigido a
modelos para propor uma solu??o que minimiza o problema de modelagem de servi?os web
confi?veis
|
404 |
MARISA-MDD: uma abordagem para transforma??es entre modelos orientados a aspectos: dos requisitos ao projeto detalhadoMedeiros, Ana Luisa Ferreira de 09 June 2008 (has links)
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
|
405 |
Model-Driven requirements engineering process aided by ontologies and natural controlled languagesCobe, Raphael Mendes de Oliveira 29 June 2009 (has links)
Made available in DSpace on 2014-12-17T15:47:51Z (GMT). No. of bitstreams: 1
RaphaelMOCpdf.pdf: 3833849 bytes, checksum: fc73f8956766c49a68d58575132da8f2 (MD5)
Previous issue date: 2009-06-29 / Researches in Requirements Engineering have been growing in the latest few years. Researchers are concerned with a set of open issues such as: communication between several user profiles involved in software engineering; scope definition;
volatility and traceability issues. To cope with these issues a set of works are concentrated in (i) defining processes to collect client s specifications in order to solve scope issues; (ii) defining models to represent requirements to address communication and traceability issues; and (iii) working on mechanisms and processes to be applied to requirements modeling in order to facilitate requirements evolution and
maintenance, addressing volatility and traceability issues. We propose an iterative Model-Driven process to solve these issues, based on a double layered CIM to communicate
requirements related knowledge to a wider amount of stakeholders. We also present a tool to help requirements engineer through the RE process. Finally we present a case study to illustrate the process and tool s benefits and usage / Pesquisas em Engenharia de Requisitos tem crescido ao longo dos ?ltimos anos. Pesquisadores est?o preocupados com uma s?rie de problemas em aberto como: comunica??o entre diversos perfıs envolvidos na engenharia de requisito; problemas na defini??o de escopo; problemas de volatilidade e ratreabilidade de requisitos. Para lidar com este conjunto de problemas em aberto, um conjunto de trabalhos est?o
concentrados em (i) definir processos para coletar especifica??es de clientes para lidar com prolemas de escopo; (ii) definir modelos para representar requisitos para lidar
com problemas de comunica??o e rastreabilidade; e (iii) defini??o de mecanismos e processos para serem aplicados a modelagem de requisitos para facilitar a evolu??o
e manuten??o de requisitos, lidando com problemas de volatilidade e rastreabilidade em requisitos. Neste trabalho ? proposto um processo dirigido por modelo para solucionar estes problemas em aberto. Este processo ? baseado na ideia de um CIM dividido em duas camadas de forma que se consiga difundir o conhecimento relacionado ao requisitos para um n?mero maior de stakeholders. Durante este trabalho tamb?m foi desenvolvida uma ferramenta que tem como objetivo auxiliar a execu??o de tal processo. Por fim apresentamos um estudo de caso para ilustrar os benef?cios do uso da ferramenta e do processo
|
406 |
CrossMDA-SPL: uma abordagem para ger?ncia de variabilidades dirigida por modelos e aspectosFilgueira, Geam Carlos de Ara?jo 11 August 2009 (has links)
Made available in DSpace on 2014-12-17T15:47:51Z (GMT). No. of bitstreams: 1
GeamCA_3.pdf: 4100171 bytes, checksum: a5754ac2b6b60fbd217e904c104737e4 (MD5)
Previous issue date: 2009-08-11 / This paper proposes a systematic approach to management of variability modelsdriven and aspects using the mechanisms of approaches Aspect-Oriented Software Development (AOSD) and Model-Driven Development (MDD). The main goal of the approach, named CrossMDA-SPL, is to improve the management(ger?ncia), modularization and isolation ou separation of the variability of the LPSs of architecture in a high level of abstraction (model) at the design and implementing phases of development Software Product Lines (SPLs), exploiting the synergy between AOSD and MDD. The CrossMDA-SPL approach defines some artifacts basis for advance the separation clear in between the mandatory (bounden) and optional features in the architecture of SPL. The artifacts are represented by two models named: (i) core model (base domain) - responsible for specify the common features the all members of the SPL, and (ii) variability model - responsible for represent the variables features of SPL. In addition, the CrossMDA-SPL approach is composed of: (i) guidelines for modeling and representation of variability, (ii) CrossMDA-SPL services and process, and (iii) models of the architecture of SPL or product instance of SPL. The guidelines use the advantages of AOSD and MDD to promote a better modularization of the variable features of the architecture of SPL during the creation of core and variability models of the approach. The services and sub-processes are responsible for combination automatically, through of process of transformation between the core and variability models, and the generation of new models that represent the implementation of the architecture of SPL or a instance model of SPL. Mechanisms for effective modularization of variability for architectures of SPL at model level. The concepts are described and measured with the execution of a case study of an SPL for management systems of transport electronic tickets / Este trabalho prop?e uma abordagem sistem?tica para ger?ncia de variabilidades dirigida por Modelos e Aspectos usando os mecanismos das abordagens de Desenvolvimento de Software Orientado a Aspectos (DSOA) e Desenvolvimento Dirigido por Modelos (DDM). O objetivo central da abordagem, denominada CrossMDA-SPL, ? melhorar a ger?ncia, modulariza??o e isolamento das variabilidades da arquitetura de LPSs em um n?vel de abstra??o alto (modelo) nas fases de projeto e implementa??o de dom?nio de desenvolvimento de Linhas de Produto de Software (LPSs), explorando a sinergia entre o DSOA e DDM. A abordagem CrossMDA-SPL define alguns artefatos base para promover a separa??o clara entres as features mandat?rias (obrigat?rias) e opcionais na arquitetura da LPS. Os artefatos s?o representados por dois modelos denominados: (i) modelo do n?cleo (dom?nio base) respons?vel por especificar as features comuns a todos os membros da LPS; e (ii) modelo de variabilidades respons?vel por representar as features vari?veis da LPS. Em adi??o, a abordagem CrossMDA-SPL ? composta por: (i) diretrizes para modelagem e representa??o das variabilidades; (ii) servi?os e processo CrossMDA-SPL; e (iii) modelos da arquitetura da LPS ou inst?ncia do produto da LPS. As diretrizes utilizam as vantagens de DSOA e DDM para promover uma melhor modulariza??o das features vari?veis da arquitetura da LPS durante a cria??o dos modelos do n?cleo e de variabilidades da abordagem. Os servi?os e subprocessos s?o respons?veis pela combina??o autom?tica, atrav?s de processos de transforma??o, entre os modelos de n?cleo e variabilidades, e a gera??o dos novos modelos que representam a implementa??o da arquitetura de LPS ou um modelo de inst?ncia da LPS. Apresentamos mecanismos para uma eficaz modulariza??o de variabilidades para arquiteturas de LPS no n?vel de modelo. Os conceitos s?o mostrados e avaliados com a execu??o de um estudo de caso de uma LPS para sistemas de gerenciamento de bilhetes eletr?nicos de transporte.
|
407 |
MaRISA-AOCode: uma abordagem gen?rica para gera??o de c?digo orientado a aspectosGuimar?es, Everton Tavares 04 March 2010 (has links)
Made available in DSpace on 2014-12-17T15:47:52Z (GMT). No. of bitstreams: 1
EvertonTG_DISSERT.pdf: 4234791 bytes, checksum: c40151c48849ad62c0cc34be8c3b56eb (MD5)
Previous issue date: 2010-03-04 / Currently there are several aspect-oriented approaches that are related to different stages of software development process. These approaches often lack integration with each other and their models and artifacts are not aligned in a coherent process. The integration of Aspect-Oriented Software development (AOSD) and Model-Driven Development (MDD) enables automatic propagation of models from one phase to another, avoiding loss of important information and decisions established in each. This paper presents a model driven approach, called Marisa-AOCode, which supports the processing of detailed design artifacts to code in different Aspect-Oriented Programming languages. The approach proposed by Maris- AOCode defines transformation rules between aSideML, a modeling language for aspectoriented
detailed design, and Metaspin, a generic metamodel for aspect-oriented programming languages. The instantiation of the generic metamodel (Metaspin) provided by the approach
of Maris-AOCode is illustrated by the transformation of Metaspin for two languages: AspectLua and CaesarJ. We illustrate the approach with a case study based on the Health
Watcher System / Atualmente existem diversas abordagens orientadas a aspectos que est?o relacionadas ?s diferentes fases do processo de desenvolvimento de software. Essas abordagens geralmente n?o possuem integra??o entre si e seus modelos e artefatos n?o est?o alinhados dentro de um processo coerente. A integra??o entre o desenvolvimento de software orientado a aspectos (DSOA) e o desenvolvimento dirigido a modelos (MDD) permite propaga??o autom?tica entre modelos de uma fase para outra, evitando perda de informa??es e decis?es importantes estabelecidas em cada uma delas. Este trabalho apresenta uma abordagem dirigida a modelos, denominada MaRiSA-AOCode, que suporta a transforma??o de artefatos de projeto detalhado em c?digo para diferentes linguagens de Programa??o Orientada a Aspectos. A abordagem proposta por MaRiSA-AOCode define regras de transforma??o entre aSideML, uma linguagem de modelagem para projeto detalhado orientado a aspectos, e Metaspin, um
metamodelo gen?rico para linguagens de programa??o orientadas a aspectos. A instancia??o do metamodelo gen?rico (Metaspin) provido pela abordagem de MaRiSA-AOCode ? ilustrada atrav?s da transforma??o do Metaspin para duas linguagens: AspectLua e CaesarJ. Ilustramos a abordagem com um estudo de caso baseado no sistema Health Watcher
|
408 |
Uma abordagem dirigida por modelos para desenvolvimento de middlewares auto-adaptativos para transmiss?o de fluxo de dados baseado em restri??es de QoS / Uma abordagem dirigida por modelos para desenvolvimento de middlewares auto-adaptativos para transmiss?o de fluxo de dados baseado em restri??es de QoSSilva, Andre Gustavo Pereira da 15 March 2010 (has links)
Made available in DSpace on 2014-12-17T15:47:52Z (GMT). No. of bitstreams: 1
AndreGPS_DISSERT.pdf: 1357503 bytes, checksum: e140d06d3ffeafa9c2f772fa5796fc4d (MD5)
Previous issue date: 2010-03-15 / The use of middleware technology in various types of systems, in order to abstract low-level details related to the distribution of application logic, is increasingly common. Among several systems that can be benefited from using these components, we highlight the distributed systems, where it is necessary to allow communications between software components located on different physical machines. An important issue related to the communication between distributed components is the provision of mechanisms for managing the quality of service. This work presents a metamodel for modeling middlewares based on components in order to provide to an application the abstraction of a communication between components involved in a data stream, regardless their location. Another feature of the metamodel is the possibility of self-adaptation related to the communication mechanism, either by updating the values of its configuration parameters, or by its replacement by another mechanism, in case of the restrictions of quality of service specified are not being guaranteed. In this respect, it is planned the monitoring of the communication state (application of techniques like feedback control loop), analyzing performance metrics related. The paradigm of Model Driven Development was used to generate the implementation of a middleware that will serve as proof of concept of the metamodel, and the configuration and reconfiguration policies related to the dynamic adaptation processes. In this sense was defined the metamodel associated to the process of a communication configuration. The MDD application also corresponds to the definition of the following transformations: the architectural model of the middleware in Java code, and the configuration model to XML / A utiliza??o da tecnologia de middleware em diversos tipos de sistemas, com a finalidade de abstrair detalhes de baixo n?vel relacionados com a distribui??o da l?gica da aplica??o, ? cada vez mais frequente. Dentre diversos sistemas que podem ser beneficiados com a utiliza??o desses componentes, podemos destacar os sistemas distribu?dos, onde ? necess?rio viabilizar a comunica??o entre componentes de software localizados em diferentes m?quinas f?sicas. Uma importante quest?o relacionada ? comunica??o entre componentes distribu?dos ? o fornecimento de mecanismos para gerenciamento da qualidade de servi?o. Este trabalho apresenta um metamodelo para modelagem de middlewares baseados em componentes que prov?em ? aplica??o a abstra??o da comunica??o entre componentes envolvidos em um fluxo de dados, independente da sua localiza??o. Outra caracter?stica do metamodelo ? a possibilidade de auto-adapta??o relacionada ao mecanismo de comunica??o utilizado, seja atrav?s da atualiza??o dos valores dos seus par?metros de configura??o, ou atrav?s da sua substitui??o por outro mecanismo, caso as restri??es de qualidade de servi?o especificadas n?o estejam sendo garantidas. Nesse prop?sito, ? previsto o monitoramento do estado da comunica??o (aplica??es de t?cnicas do tipo feedback control loop), analisando-se m?tricas de desempenho relacionadas. O paradigma de Desenvolvimento Dirigido por Modelos foi utilizado para gerar a implementa??o de um middleware que servir? como prova de conceito do metamodelo, e as pol?ticas de configura??o e reconfigura??o relacionadas com o processo de adapta??o din?mica; neste sentido, foi definido o metamodelo associado ao processo de configura??o de uma comunica??o. A aplica??o da t?cnica de MDD corresponde ainda ? defini??o das seguintes transforma??es: do modelo arquitetural do middleware para c?digo em linguagem Java, e do modelo de configura??o para c?digo XML
|
409 |
GingaForAll: linha de Produtos do Middleware GingaPereira, Lucas Silva 16 December 2010 (has links)
Made available in DSpace on 2014-12-17T15:47:55Z (GMT). No. of bitstreams: 1
LucasSP_DISSERT.pdf: 4412437 bytes, checksum: 1797ce9cec4016d1d5518d6d933435d2 (MD5)
Previous issue date: 2010-12-16 / Many challenges have been imposed on the middleware to support applications for
digital TV because of the heterogeneity and resource constraints of execution
platforms. In this scenario, the middleware must be highly configurable so that it can
be customized to meet the requirements of applications and underlying platforms.
This work aims to present the GingaForAll, a software product line developed for the
Ginga - the middleware of the Brazilian Digital TV (SBTVD). GingaForAll adds the
concepts of software product line, aspect orientation and model-driven development
to allow: (i) the specification of the common characteristics and variables of the
middleware, (ii) the modularization of crosscutting concerns - both mandatory and
concepts variables - through aspects, (iii) the expression of concepts as a set of
models that increase the level of abstraction and enables management of various
software artifacts in terms of configurable models. This work presents the
architecture of the software product line that implements such a tool and architecture
that supports automatic customization of middleware. The work also presents a tool
that implements the process of generating products GingaForAll / V?rios desafios t?m sido impostos a middleware para suporte a aplica??es de
TV digital devido a heterogeneidade e restri??es de recursos das plataformas de
execu??o. Nesse cen?rio, o middleware deve ser altamente configur?vel de forma a
poder ser customizado para atender aos requisitos das aplica??es e das plataformas
subjacentes. Esse trabalho tem como objetivo apresentar o GingaForAll, uma linha
de produtos de software desenvolvida para o Ginga o middleware do Sistema
Brasileiro de TV Digital (SBTVD). GingaForAll agrega os conceitos de linha de
produtos de software, orienta??o a aspectos e desenvolvimento dirigido a modelos
de forma a permitir: (i) a especifica??o das caracter?sticas comuns e vari?veis do
middleware; (ii) a modulariza??o dos conceitos transversais tanto conceitos
obrigat?rios quanto vari?veis atrav?s de aspectos; (iii) a express?o de conceitos
como um conjunto de modelos que aumentam o n?vel de abstra??o e permite o
gerenciamento de diferentes artefatos de software em termos de modelos
configur?veis. Esse trabalho apresenta a arquitetura da linha de produtos de
software e uma ferramenta que implementa tal arquitetura e que oferece suporte
para customiza??es autom?ticas do middleware. O trabalho tamb?m apresenta uma
ferramenta que implementa o processo de gera??o de produtos GingaForAll
|
410 |
Uma abordagem dirigida por modelos para ger?ncia de variabilidade e execu??o de processos de softwareSantos, Wanderson C?mara dos 23 February 2011 (has links)
Made available in DSpace on 2014-12-17T15:47:58Z (GMT). No. of bitstreams: 1
WandersonCS_DISSERT.pdf: 4290121 bytes, checksum: 50ada3cdab9dc8f8edb8464d66f255e9 (MD5)
Previous issue date: 2011-02-23 / This dissertation presents a model-driven and integrated approach to variability management,
customization and execution of software processes. Our approach is founded
on the principles and techniques of software product lines and model-driven engineering.
Model-driven engineering provides support to the specification of software processes and
their transformation to workflow specifications. Software product lines techniques allows
the automatic variability management of process elements and fragments. Additionally,
in our approach, workflow technologies enable the process execution in workflow engines.
In order to evaluate the approach feasibility, we have implemented it using existing
model-driven engineering technologies. The software processes are specified using
Eclipse Process Framework (EPF). The automatic variability management of software
processes has been implemented as an extension of an existing product derivation tool.
Finally, ATL and Acceleo transformation languages are adopted to transform EPF process
to jPDL workflow language specifications in order to enable the deployment and execution
of software processes in the JBoss BPM workflow engine. The approach is evaluated
through the modeling and modularization of the project management discipline of the
Open Unified Process (OpenUP) / Este trabalho apresenta uma abordagem dirigida por modelos para ger?ncia de variabilidades
em processos de software, assim como sua implanta??o em sistemas de workflow.
A abordagem ? fundamentada nos princ?pios e t?cnicas de linhas de produto de
software e engenharia dirigida por modelos. Engenharia dirigida por modelos fornece
suporte para a especifica??o de processos de software e sua transforma??o em especifica??es
de fluxo de trabalho. T?cnicas de linhas de produto de software permitem a ger?ncia
autom?tica de variabilidades de elementos do processo e fragmentos. Al?m disso, em
nossa abordagem, tecnologias de workflows permitem a execu??o do processo em motores
de workflow. Para avaliar a viabilidade abordagem, a implementamos utilizando
tecnologias existentes de engenharia dirigida por modelos. Os processos de software s?o
especificados usando Eclipse Processo Framework (EPF). O gerenciamento autom?tico
das variabilidades de processos de software foi implementado como uma extens?o de
uma ferramenta de deriva??o produtos j? existente. Finalmente, as linguagens de transforma??o
ATL e Acceleo s?o adotadas para transformar o processo EPF para a linguagem
de especifica??es de fluxo de trabalho jPDL, a fim de permitir a implanta??o e execu??o
de processos de software no motor de workflow JBoss BPM. A abordagem ? avaliada
atrav?s da modelagem e modulariza??o da disciplina de gerenciamento de projetos do
processo aberto Unificado (OpenUP)
|
Page generated in 0.2995 seconds