Submitted by JOSIANE SANTOS DE OLIVEIRA (josianeso) on 2018-04-25T16:10:27Z No. of bitstreams: 1 Maicon dos Santos_.pdf: 3747706 bytes, checksum: ef8b81f35d6d19fc23c56bfba79044c5 (MD5) / Made available in DSpace on 2018-04-25T16:10:27Z (GMT). No. of bitstreams: 1 Maicon dos Santos_.pdf: 3747706 bytes, checksum: ef8b81f35d6d19fc23c56bfba79044c5 (MD5) Previous issue date: 2018-01-18 / Nenhuma / Engenharia reversa de código desempenha um papel fundamental em várias atividades de Engenharia de Software, tais como geração de modelos a partir de código legado e recuperação de funcionalidades (ou features) de sistemas. No contexto de Linha de Produto de Software (LPS), por exemplo, um produto de software é formado por um conjunto de features que são constantemente alteradas para acomodar mudanças de regras de negócio. Consequentemente, o modelo (por exemplo, diagrama de classes da UML) que representa toda LPS precisa ser modificado para refletir as atualizações realizadas. Neste contexto, várias ferramentas têm sido propostas nas últimas décadas, por exemplo, Astah e ArgoUML. Porém, as ferramentas (e suas técnicas) não dão suporte à engenharia reversa orientada a features, são imprecisas no que se refere à completude dos diagramas gerados, bem como exige um alto esforço para atualização dos modelos pois são manuais ou semiautomáticas. Para mitigar esta problemática, este trabalho propõe a TechREF, uma técnica de engenharia reversa orientada a features. De forma automática, a TechREF captura o fluxo de execução do código associado a uma feature, identifica as informações estruturais e comportamentais do código, e gera diagramas de classes UML, bem como persiste tais diagramas. A TechREF foi avaliada através de um estudo de caso tendo cenários reais de engenharia reversa. Esta avaliação buscou verificar o esforço e a corretude das atividades que serão realizadas no experimento com o uso dos modelos orientados a features. / Reverse code engineering plays a key role in various Software Engineering activities, such as model generation from legacy code and retrieval of system features. In the context of Software Product Line (LPS), for example, a software product is composed of a set features that are constantly changed to accommodate changes in business rules. Consequently, the model (for example, UML class diagram) that represents the entire LPS needs to be modified to reflect the updates made. In this context, several tools have been proposed in the last decades, for example, Astah and ArgoUML. However, the tools (and their techniques) do not support feature-oriented reverse engineering, are imprecise in terms of the completeness of the generated diagrams, as well as requiring a high effort to update the models because they are manual or semiautomatic. To mitigate this problem, this paper proposes TechREF, a reverse engineering technique oriented to features. Automatically, TechREF captures the execution flow of code associated with a feature, identifies the structural and behavioral information of the code, and generates diagrams of UML classes, as well as persists such diagrams. TechREF was evaluated through a case study having real reverse engineering scenarios. This evaluation sought to verify the effort and correctness of the activities that will be carried out in the experiment with the use of the models oriented to features.

Les logiciels s'orientent de plus en plus vers des architectures évolutives, capables de s'adapter facilement aux changements et d'intégrer de nouvelles fonctionnalités. Ceci est important pour plusieurs classes d'applications qui ont besoin d‘évoluer sans que cela implique d'interrompre leur exécution. Des plateformes dynamiques à composants autorisent ce type d'évolution à l'exécution, en permettant aux composants d'être chargés et exécutés sans requérir le redémarrage complet de l'application en service. Toutefois, la flexibilité d'un tel mécanisme introduit de nouveaux défis qui exigent de gérer les possibles erreurs dues à des incohérences dans le processus de mise à jour, ou en raison du comportement défectueux de composants survenant pendant l'exécution de l'application. Des composants tiers dont l'origine ou la qualité sont inconnus peuvent être considérées à priori comme peu fiables, car ils peuvent potentiellement introduire des défauts d'applications lorsqu'il est combiné avec d'autres composants. Nous sommes intéressés à la réduction de l'impact de ces composants considérés comme non fiables et qui sont susceptibles de compromettre la fiabilité de l'application en cours d'exécution. Cette thèse porte sur l'application de techniques pour améliorer la fiabilité des applications dynamiques à composants. Pour cela, nous proposons l'utilisation des frontières d'isolation pouvant fournir du contingentement de fautes. Le composant ainsi isolé ne perturbe pas le reste de l'application quand il est défaillant. Une telle approche peut être vu sous trois perspectives présentées: (i) l'isolement des composants dynamiques, régi par une politique d'exécution reconfigurable, (ii) l'autoréparation de conteneurs d‘isolement, et (iii) l'utilisation des aspects pour séparer les préoccupations de fiabilité à partir du code fonctionnel. / Software is moving towards evolutionary architectures that are able to easily accommodate changes and integrate new functionality. This is important in a wide range of applications, from plugin-based end user applications to critical applications with high availability requirements. Dynamic component-based platforms allow software to evolve at runtime, by allowing components to be loaded, and executed without forcing applications to be restarted. However, the flexibility of such mechanism demands applications to cope with errors due to inconsistencies in the update process, or due to faulty behavior from components introduced during execution. This is mainly true when dealing with third-party components, making it harder to predict the impacts (e.g., runtime incompatibilities, application crashes) and to maintain application dependability when integrating such third-party code into the application. Components whose origin or quality attributes are unknown could be considered as untrustworthy since they can potentially introduce faults to applications when combined with other components, even if unintentionally. The quality of components is harder to evaluate when components are combined together, especially if it happens on-the-fly. We are interested in reducing the impact that can be brought by untrustworthy components deployed at runtime and that would potentially compromise application dependability. This thesis focuses on applying techniques for moving a step forward towards dependable dynamic component-based applications by addressing different dependability attributes namely reliability, maintainability and availability. We propose the utilization of strong component isolation boundaries, by providing a fault-contained environment for separately running untrustworthy components. Our solution combines three approaches: (i) the dynamic isolation of components, governed by a runtime reconfigurable policy; (ii) a self-healing component isolation container; and (iii) the usage of aspects for separating dependability concerns from functional code.

O paradigma orientado a objetos não dispõe de abstrações adequadas à modularização de interesses transversais - interesses cuja implementação encontra-se entrelaçada e espalhada por todos os módulos de um sistema. Com o surgimento da Programação Orientada a Aspectos e a disponibilidade de abstrações adequadas à modularização de interesses transversais, o reúso desses interesses foi facilitado. Nesta tese são apresentados alguns resultados de esforços de pesquisa que visam a tornar o reúso de interesses transversais mais efetivo. Definições e classificações para frameworks desenvolvidos no contexto da POA - frameworks transversais - são apresentadas com o objetivo de facilitar a comunicação entre usuários e pesquisadores. Uma arquitetura de referência para o projeto e implementação de frameworks transversais, que torna sua estrutura mais clara e facilita a integração de vários frameworks quando a intenção é criar um repositório de aspectos reusáveis, é proposta. Três famílias de frameworks transversais: de persistência, de segurança e de regras de negócio foram desenvolvidas. Cada família de frameworks transversais constitui uma linha de produtos de software, em que membros podem ser configurados com características (features) distintas. Um processo de desenvolvimento, denominado ProFT/PU, baseado no Processo Unificado (PU), que considera as famílias de frameworks ao longo de todo o processo é apresentado, juntamente com um exemplo de sua utilização para uma aplicação típica. Um estudo de caso para comparar o tempo requerido para reusar um framework transversal de persistência e um framework orientado a objetos de persistência é também apresentado e discutido. / The object-oriented paradigm does not provide adequate abstractions to modularize crosscutting concerns - concerns whose implementation end up tangling and spreading throughout the modules of a system. With the emerging of Aspect-Oriented Programming (AOP) and the availability of abstractions suitable to modularize crosscutting concerns, the reuse of such concerns is facilitated. In this thesis, some results of research efforts to make the reuse of crosscutting concerns more effective are presented. Definitions and classifications for frameworks developed in the context of AOP - crosscutting frameworks - with the objective of improving understanding and communication among users and researchers are presented. An architecture specifically to design and implement this type of framework, which makes its structure clearer and facilitates the integration of several frameworks, is proposed. Three families of crosscutting frameworks for persistence, security and business rules, were developed. Each crosscutting framework family is a software product line, in which members can be instantiated with distinct characteristics. A development process, named ProFT/PU, based on Unifed Process (UP), which takes into account the families during the process, is presented, along with an example of its use for a typical application. A case study to compare the time required to reuse a persistence crosscutting framework and a persistence object-oriented framework is also presented and discussed.

This thesis proposes a privacy protection framework for the controlled distribution and use of personal private data. The framework is based on the idea that privacy policies can be set directly by the data owner and can be automatically enforced against the data user. Data privacy continues to be a very important topic, as our dependency on electronic communication maintains its current growth, and private data is shared between multiple devices, users and locations. The growing amount and the ubiquitous availability of personal private data increases the likelihood of data misuse. Early privacy protection techniques, such as anonymous email and payment systems have focused on data avoidance and anonymous use of services. They did not take into account that data sharing cannot be avoided when people participate in electronic communication scenarios that involve social interactions. This leads to a situation where data is shared widely and uncontrollably and in most cases the data owner has no control over further distribution and use of personal private data. Previous efforts to integrate privacy awareness into data processing workflows have focused on the extension of existing access control frameworks with privacy aware functions or have analysed specific individual problems such as the expressiveness of policy languages. So far, very few implementations of integrated privacy protection mechanisms exist and can be studied to prove their effectiveness for privacy protection. Second level issues that stem from practical application of the implemented mechanisms, such as usability, life-time data management and changes in trustworthiness have received very little attention so far, mainly because they require actual implementations to be studied. Most existing privacy protection schemes silently assume that it is the privilege of the data user to define the contract under which personal private data is released. Such an approach simplifies policy management and policy enforcement for the data user, but leaves the data owner with a binary decision to submit or withhold his or her personal data based on the provided policy. We wanted to empower the data owner to express his or her privacy preferences through privacy policies that follow the so-called Owner-Retained Access Control (ORAC) model. ORAC has been proposed by McCollum, et al. as an alternate access control mechanism that leaves the authority over access decisions by the originator of the data. The data owner is given control over the release policy for his or her personal data, and he or she can set permissions or restrictions according to individually perceived trust values. Such a policy needs to be expressed in a coherent way and must allow the deterministic policy evaluation by different entities. The privacy policy also needs to be communicated from the data owner to the data user, so that it can be enforced. Data and policy are stored together as a Protected Data Object that follows the Sticky Policy paradigm as defined by Mont, et al. and others. We developed a unique policy combination approach that takes usability aspects for the creation and maintenance of policies into consideration. Our privacy policy consists of three parts: A Default Policy provides basic privacy protection if no specific rules have been entered by the data owner. An Owner Policy part allows the customisation of the default policy by the data owner. And a so-called Safety Policy guarantees that the data owner cannot specify disadvantageous policies, which, for example, exclude him or her from further access to the private data. The combined evaluation of these three policy-parts yields the necessary access decision. The automatic enforcement of privacy policies in our protection framework is supported by a reference monitor implementation. We started our work with the development of a client-side protection mechanism that allows the enforcement of data-use restrictions after private data has been released to the data user. The client-side enforcement component for data-use policies is based on a modified Java Security Framework. Privacy policies are translated into corresponding Java permissions that can be automatically enforced by the Java Security Manager. When we later extended our work to implement server-side protection mechanisms, we found several drawbacks for the privacy enforcement through the Java Security Framework. We solved this problem by extending our reference monitor design to use Aspect-Oriented Programming (AOP) and the Java Reflection API to intercept data accesses in existing applications and provide a way to enforce data owner-defined privacy policies for business applications. / Im Rahmen der Dissertation wurde ein Framework für die Durchsetzung von Richtlinien zum Schutz privater Daten geschaffen, welches darauf setzt, dass diese Richtlinien oder Policies direkt von den Eigentümern der Daten erstellt werden und automatisiert durchsetzbar sind. Der Schutz privater Daten ist ein sehr wichtiges Thema im Bereich der elektronischen Kommunikation, welches durch die fortschreitende Gerätevernetzung und die Verfügbarkeit und Nutzung privater Daten in Onlinediensten noch an Bedeutung gewinnt. In der Vergangenheit wurden verschiedene Techniken für den Schutz privater Daten entwickelt: so genannte Privacy Enhancing Technologies. Viele dieser Technologien arbeiten nach dem Prinzip der Datensparsamkeit und der Anonymisierung und stehen damit der modernen Netznutzung in Sozialen Medien entgegen. Das führt zu der Situation, dass private Daten umfassend verteilt und genutzt werden, ohne dass der Datenbesitzer gezielte Kontrolle über die Verteilung und Nutzung seiner privaten Daten ausüben kann. Existierende richtlinienbasiert Datenschutztechniken gehen in der Regel davon aus, dass der Nutzer und nicht der Eigentümer der Daten die Richtlinien für den Umgang mit privaten Daten vorgibt. Dieser Ansatz vereinfacht das Management und die Durchsetzung der Zugriffsbeschränkungen für den Datennutzer, lässt dem Datenbesitzer aber nur die Alternative den Richtlinien des Datennutzers zuzustimmen, oder keine Daten weiterzugeben. Es war daher unser Ansatz die Interessen des Datenbesitzers durch die Möglichkeit der Formulierung eigener Richtlinien zu stärken. Das dabei verwendete Modell zur Zugriffskontrolle wird auch als Owner-Retained Access Control (ORAC) bezeichnet und wurde 1990 von McCollum u.a. formuliert. Das Grundprinzip dieses Modells besteht darin, dass die Autorität über Zugriffsentscheidungen stets beim Urheber der Daten verbleibt. Aus diesem Ansatz ergeben sich zwei Herausforderungen. Zum einen muss der Besitzer der Daten, der Data Owner, in die Lage versetzt werden, aussagekräftige und korrekte Richtlinien für den Umgang mit seinen Daten formulieren zu können. Da es sich dabei um normale Computernutzer handelt, muss davon ausgegangen werden, dass diese Personen auch Fehler bei der Richtlinienerstellung machen. Wir haben dieses Problem dadurch gelöst, dass wir die Datenschutzrichtlinien in drei separate Bereiche mit unterschiedlicher Priorität aufteilen. Der Bereich mit der niedrigsten Priorität definiert grundlegende Schutzeigenschaften. Der Dateneigentümer kann diese Eigenschaften durch eigene Regeln mittlerer Priorität überschrieben. Darüber hinaus sorgt ein Bereich mit Sicherheitsrichtlinien hoher Priorität dafür, dass bestimmte Zugriffsrechte immer gewahrt bleiben. Die zweite Herausforderung besteht in der gezielten Kommunikation der Richtlinien und deren Durchsetzung gegenüber dem Datennutzer (auch als Data User bezeichnet). Um die Richtlinien dem Datennutzer bekannt zu machen, verwenden wir so genannte Sticky Policies. Das bedeutet, dass wir die Richtlinien über eine geeignete Kodierung an die zu schützenden Daten anhängen, so dass jederzeit darauf Bezug genommen werden kann und auch bei der Verteilung der Daten die Datenschutzanforderungen der Besitzer erhalten bleiben. Für die Durchsetzung der Richtlinien auf dem System des Datennutzers haben wir zwei verschiedene Ansätze entwickelt. Wir haben einen so genannten Reference Monitor entwickelt, welcher jeglichen Zugriff auf die privaten Daten kontrolliert und anhand der in der Sticky Policy gespeicherten Regeln entscheidet, ob der Datennutzer den Zugriff auf diese Daten erhält oder nicht. Dieser Reference Monitor wurde zum einen als Client-seitigen Lösung implementiert, die auf dem Sicherheitskonzept der Programmiersprache Java aufsetzt. Zum anderen wurde auch eine Lösung für Server entwickelt, welche mit Hilfe der Aspekt-orientierten Programmierung den Zugriff auf bestimmte Methoden eines Programms kontrollieren kann. In dem Client-seitigen Referenzmonitor werden Privacy Policies in Java Permissions übersetzt und automatisiert durch den Java Security Manager gegenüber beliebigen Applikationen durchgesetzt. Da dieser Ansatz beim Zugriff auf Daten mit anderer Privacy Policy den Neustart der Applikation erfordert, wurde für den Server-seitigen Referenzmonitor ein anderer Ansatz gewählt. Mit Hilfe der Java Reflection API und Methoden der Aspektorientierten Programmierung gelang es Datenzugriffe in existierenden Applikationen abzufangen und erst nach Prüfung der Datenschutzrichtlinie den Zugriff zuzulassen oder zu verbieten. Beide Lösungen wurden auf ihre Leistungsfähigkeit getestet und stellen eine Erweiterung der bisher bekannten Techniken zum Schutz privater Daten dar.

Made available in DSpace on 2014-12-17T15:47:00Z (GMT). No. of bitstreams: 1 AnaLFM_TESE.pdf: 3970701 bytes, checksum: 513ce9d2a22c9323df778dcf23fb1033 (MD5) Previous issue date: 2012-07-30 / Model-oriented strategies have been used to facilitate products customization in the software products lines (SPL) context and to generate the source code of these derived products through variability management. Most of these strategies use an UML (Unified Modeling Language)-based model specification. Despite its wide application, the UML-based model specification has some limitations such as the fact that it is essentially graphic, presents deficiencies regarding the precise description of the system architecture semantic representation, and generates a large model, thus hampering the visualization and comprehension of the system elements. In contrast, architecture description languages (ADLs) provide graphic and textual support for the structural representation of architectural elements, their constraints and interactions. This thesis introduces ArchSPL-MDD, a model-driven strategy in which models are specified and configured by using the LightPL-ACME ADL. Such strategy is associated to a generic process with systematic activities that enable to automatically generate customized source code from the product model. ArchSPLMDD strategy integrates aspect-oriented software development (AOSD), modeldriven development (MDD) and SPL, thus enabling the explicit modeling as well as the modularization of variabilities and crosscutting concerns. The process is instantiated by the ArchSPL-MDD tool, which supports the specification of domain models (the focus of the development) in LightPL-ACME. The ArchSPL-MDD uses the Ginga Digital TV middleware as case study. In order to evaluate the efficiency, applicability, expressiveness, and complexity of the ArchSPL-MDD strategy, a controlled experiment was carried out in order to evaluate and compare the ArchSPL-MDD tool with the GingaForAll tool, which instantiates the process that is part of the GingaForAll UML-based strategy. Both tools were used for configuring the products of Ginga SPL and generating the product source code / Estrat?gias dirigidas a modelos t?m sido usadas para facilitar a customiza??o de produtos no contexto de Linhas de Produtos de Software (LPS) e gera??o de c?digo fonte desses produtos derivados atrav?s do gerenciamento de variabilidades. A maioria dessas estrat?gias faz uso da especifica??o de modelos baseados em UML (Unified Modeling Language), que apesar de ser amplamente aplicada, possui algumas limita??es por ser essencialmente gr?fica, apresentar defici?ncia em descrever precisamente a sem?ntica da representa??o da arquitetura do sistema e gerar um modelo extenso, o que dificulta a visualiza??o e compreens?o dos elementos do sistema. J? as linguagens de descri??o arquiteturais (ADLs) oferecem suporte textual e gr?fico para representa??o estrutural dos elementos arquiteturais, suas restri??es e intera??es. Essa tese apresenta ArchSPL-MDD, uma estrat?gia dirigida a modelos especificados e configurados usando a ADL LightPL-ACME. Tal estrat?gia est? associada a um processo gen?rico com atividades sistem?ticas que permitem a gera??o autom?tica do c?digo fonte customizados a partir do modelo do produto. A estrat?gia ArchSPL-MDD integra o desenvolvimento orientado a aspectos (DSOA), desenvolvimento dirigido a modelos (DDM), e LPS, o que permite a modelagem expl?cita e modulariza??o de variabilidades e caracter?sticas transversais. O processo ? instanciado pela ferramenta ArchSPL-MDD, que oferece suporte para a especifica??o, em LightPL-ACME dos modelos de dom?nio que s?o o foco do desenvolvimento. O ArchSPL-MDD usa como estudo de caso o middleware de TV Digital Ginga. De forma a avaliar a efici?ncia, aplicabilidade, expressividade e complexidade da estrat?gia ArchSPL-MDD, foi realizado um experimento controlado que avalia e compara a ferramenta ArchSPL-MDD, com a ferramenta GingaForAll, que instancia o processo que faz parte da estrat?gia GingaForAll, baseada em UML. Ambas as ferramentas foram usadas para configura??o do produto da LPS do do middlelare Ginga e gera??o de c?digo fonte do produto

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-12-17T15:47:49Z (GMT). No. of bitstreams: 1 IsanioLAS.pdf: 1324306 bytes, checksum: 06b1bb191919f02b1e6524146d71c0d3 (MD5) Previous issue date: 2008-11-10 / Ubiquitous computing systems operate in environments where the available resources significantly change during the system operation, thus requiring adaptive and context aware mechanisms to sense changes in the environment and adapt to new execution contexts. Motivated by this requirement, a framework for developing and executing adaptive context aware applications is proposed. The PACCA framework employs aspect-oriented techniques to modularize the adaptive behavior and to keep apart the application logic from this behavior. PACCA uses abstract aspect concept to provide flexibility by addition of new adaptive concerns that extend the abstract aspect. Furthermore, PACCA has a default aspect model that considers habitual adaptive concerns in ubiquitous applications. It exploits the synergy between aspect-orientation and dynamic composition to achieve context-aware adaptation, guided by predefined policies and aim to allow software modules on demand load making possible better use of mobile devices and yours limited resources. A Development Process for the ubiquitous applications conception is also proposed and presents a set of activities that guide adaptive context-aware developer. Finally, a quantitative study evaluates the approach based on aspects and dynamic composition for the construction of ubiquitous applications based in metrics / Aplica??es para a computa??o ub?qua operam em ambientes onde a disponibilidade de recursos muda significativamente durante a sua opera??o. Tal caracter?stica demanda que aplica??es sejam adaptativas e cientes do seu contexto de execu??o. Visando atender esses requisitos, ? proposto o PACCA (Projeto de Aplica??es Ciente ao Contexto e Adaptativas), um arcabou?o para desenvolvimento e execu??o de aplica??es adaptativas cientes de contexto. O paradigma de orienta??o a aspectos ? usado no PACCA para modularizar o comportamento adaptativo e dissoci?-lo da l?gica da aplica??o. Para prover maior flexibilidade o PACCA utiliza o conceito de aspecto abstrato para permitir a extens?o e adi??o de novos interesses adaptativos, al?m de um modelo de aspectos default que contempla interesses adaptativos comuns a grande parte das aplica??es ub?quas. A orienta??o a aspectos aliada ? composi??o din?mica de software oferece suporte para adapta??o ciente ao contexto, guiada por pol?ticas previamente definidas e tem por objetivo permitir a carga de m?dulos de software sob demanda possibilitando melhor utiliza??o dos recursos limitados de um dispositivo m?vel. Um Processo de Desenvolvimento para a constru??o de aplica??es ub?quas tamb?m ? proposto e visa demonstrar um conjunto de atividades a serem executadas para a concep??o de aplica??es ub?quas. Por fim, ? realizado um estudo quantitativo com o intuito de avaliar com base em m?tricas a abordagem baseada em aspectos e composi??o din?mica para a constru??o de aplica??es ub?quas

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.

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

Made available in DSpace on 2014-12-17T15:47:58Z (GMT). No. of bitstreams: 1 DanielleGFM_DISSERT.pdf: 2687890 bytes, checksum: b53115296e0be43418332dfb089a931a (MD5) Previous issue date: 2011-05-13 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / The World Wide Web has been consolidated over the last years as a standard platform to provide software systems in the Internet. Nowadays, a great variety of user applications are available on the Web, varying from corporate applications to the banking domain, or from electronic commerce to the governmental domain. Given the quantity of information available and the quantity of users dealing with their services, many Web systems have sought to present recommendations of use as part of their functionalities, in order to let the users to have a better usage of the services available, based on their profile, history navigation and system use. In this context, this dissertation proposes the development of an agent-based framework that offers recommendations for users of Web systems. It involves the conception, design and implementation of an object-oriented framework. The framework agents can be plugged or unplugged in a non-invasive way in existing Web applications using aspect-oriented techniques. The framework is evaluated through its instantiation to three different Web systems / A World Wide Web, ou simplesmente Web, se consolidou ao longo dos ?ltimos anos como uma plataforma padr?o para disponibilizar sistemas de software de diferentes naturezas na Internet. Atualmente, uma grande variedade de aplica??es est? dispon?vel na plataforma Web, variando desde aplica??es corporativas do dom?nio banc?rio, governamental e at? com?rcio eletr?nico. Dada a quantidade de informa??o disponibilizada e de usu?rios usando seus servi?os, muitos sistemas Web tem buscado apresentar recomenda??es como parte de suas funcionalidades, com o objetivo de permitir ao usu?rio um melhor uso dos servi?os dispon?veis, baseado no perfil do usu?rio e no seu hist?rico de navega??o e uso do sistema. Neste contexto, este trabalho de disserta??o prop?e o desenvolvimento de um framework de agentes de usu?rio que ofere?am recomenda??es para usu?rios de sistemas Web. Este trabalho envolve a concep??o, projeto e implementa??o de um framework orientado a objetos que permite o desenvolvimento de agentes de usu?rio de recomenda??o para sistemas Web. Os agentes do framework podem ser plugados ou desplugados de forma n?o invasiva em aplica??es Web existentes, atrav?s de uma implementa??o orientada a aspectos. O framework foi avaliado atrav?s da sua instancia??o para tr?s sistemas Web de naturezas distinta