Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2017-10-18T19:35:37Z No. of bitstreams: 1 DemostenesSantosDeSena_TESE.pdf: 4593790 bytes, checksum: 3e0845d816f16e3a8f7659744e28f8ad (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2017-10-19T19:11:29Z (GMT) No. of bitstreams: 1 DemostenesSantosDeSena_TESE.pdf: 4593790 bytes, checksum: 3e0845d816f16e3a8f7659744e28f8ad (MD5) / Made available in DSpace on 2017-10-19T19:11:30Z (GMT). No. of bitstreams: 1 DemostenesSantosDeSena_TESE.pdf: 4593790 bytes, checksum: 3e0845d816f16e3a8f7659744e28f8ad (MD5) Previous issue date: 2017-02-13 / Os mecanismos de tratamento de exce??es s?o recursos fornecidos pelas principais linguagens de programa??o para auxiliar no desenvolvimento de sistemas robustos. A pol?tica de tratamento de exce??es corresponde ao conjunto de regras de design do tratamento excepcional e definem os elementos de c?digo (m?todos, classes ou pacotes) respons?veis pela sinaliza??o, propaga??o, captura das exce??es e as respectivas a??es de tratamento. Alguns estudos emp?ricos demonstraram que o tratamento inadequado de exce??es, consequ?ncia da falta da pol?tica documentada, ? uma poss?vel fonte de defeitos. Por outro lado, devido ? natureza impl?cita dos fluxos de exce??es, a identifica??o e corre??o dos tratamentos de exce??es tornam-se tarefas complexas. Para amenizar os problemas decorrentes do tratamento inadequado devido ? falta de documenta??o do tratamento de exce??es, algumas abordagens definiram linguagens de especifica??o das regras de tratamento com suporte ferramental para auxiliar na defini??o e checagem das regras. Entretanto, historicamente, as pol?ticas de tratamento de exce??es dos sistemas s?o postergadas ou ignoradas no processo de desenvolvimento. Adicionalmente, nenhuma das abordagens propostas oferece suporte ? defini??o das regras, de forma a auxiliar o arquiteto a extrair as regras a partir da an?lise de c?digo fonte pr?-existente, e este ? o objetivo da abordagem apresentada neste trabalho. Para apoiar a execu??o da abordagem proposta, foi desenvolvida uma ferramenta de an?lise est?tica que permite: (i) a coleta dos fluxos excepcionas e das respectivas a??es de tratamentos; (ii) a identifica??o e defini??o dos agrupamentos, que s?o os elementos de c?digo que possuem os mesmos comportamentos em rela??o ao tratamento de exce??es; (iii) a extra??o das regras; e, (iv) a checagem das regras e identifica??o das causas das viola??es ? pol?tica. A abordagem ? demonstrada em dois estudos emp?ricos. No primeiro estudo emp?rico foram analisadas 656 bibliotecas (libs) Java do reposit?rio central Maven com objetivo de extrair e caracterizar a pol?tica de tratamento de exce??es destas libs. Este estudo revelou que 80,9% das bibliotecas possuem fluxos excepcionais que implementam pelo menos um anti-pattern do tratamento excepcional. O segundo estudo emp?rico teve como objetivo investigar os benef?cios da extra??o das regras excepcionais a partir do c?digo pr?-existente no processo de defini??o e checagem da pol?tica de tratamento de exce??es. Dois sistemas de informa??o Web (i.e., IProject e SIGAA) foram utilizados neste segundo estudo. Neste estudo pudemos observar que todas as regras reportadas pelos arquitetos foram extra?das pelo suporte ferramental, e que os resultados do processo de extra??o permitiram que novas regras fossem adicionadas pelos arquitetos. Essas regras adicionadas foram as regras n?o definidas pelos arquitetos e corresponderam ? 57,1% (IProject) e 52,8% (SIGAA/Gradua??o) das regras da pol?tica dos sistemas analisados. O processo de checagem das regras definidas com o apoio da abordagem mostrou que 35,6% e 45,7% dos fluxos excepcionais do IProject e SIGAA/Gradua??o, respectivamente, violavam alguma das regras de tratamento de exce??es. / The Exception handling (EH) mechanism is a technique embedded in most of the mainstream programming languages to support the development of robust systems. The exception handling policy is composed by the set of exception handling design rules and which specify the elements (methods, classes and packages) or that contains the elements responsible for raising, propagating and catching of exceptions as well as the handling actions. Empirical studies have demonstrated that an inappropriate exception handling as consequence of undocumented exception handling policy is a source of bug hazards. On the other hand, due to the implicit nature of exception flows, the identification of exception handling code is a complex task. To address the problems resulting from the not-understood or inadequate exception handling, some approaches have been proposed languages to specify exception handling rules as well as a set of support tool to verify the constraints and checking the rules. However, historically, the exception handling policies are postponed or ignored in the software process development. Additionally, none of the proposed approaches provide support to the phase of exception policy definition. This work proposes an approach that helps the architect to extract the EH rules by performing an analysis on the existing code. Doing so, this approach fills the previous gap the EH policy definition. To support the proposed approach, a static tool suite was developed, which performs: (i) the discovery of exception flows and its handling actions; (ii) the definition of compartments; (iii) the semi-automatic rule extraction process; and (iv) the rule checking and identification of rule violation causes. This approach was assessed in two empirical studies. In the first study, 656 libraries from Maven central repository were analyzed. The main goal of this study was to reveal and to characterize the exception handling policy of the analyzed libraries. This study revealed that 80.9% of the analyzed libraries have exception flows that implement at least one exception handling anti-pattern. In the second study, we investigated the benefits of rule extraction process in the definition and checking of exception handling rules. Two web information systems (i.e., IProject and SIGAA) were analyzed in this second study. We found that all set of rules reported by the architects were extracted by our tool and the result of extraction process allowed that new rules were added to the policy. These added rules were not defined by architects and they corresponded to 57.1% (IProject) and 52.8% (SIGAA/Gradua??o) of the rules of analyzed systems. The checking process of defined rules supported by our approach verified that 35.6% (IProject) and 45.7% (SIGAA/Gradua??o) of exception flows violated some defined rule.

Made available in DSpace on 2014-12-17T15:48:10Z (GMT). No. of bitstreams: 1 EliezioSSN_DISSERT.pdf: 2190104 bytes, checksum: 2908609aa5c1ba4f1490b02210bf4470 (MD5) Previous issue date: 2014-04-25 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior / Mainstream programming languages provide built-in exception handling mechanisms to support robust and maintainable implementation of exception handling in software systems. Most of these modern languages, such as C#, Ruby, Python and many others, are often claimed to have more appropriated exception handling mechanisms. They reduce programming constraints on exception handling to favor agile changes in the source code. These languages provide what we call maintenance-driven exception handling mechanisms. It is expected that the adoption of these mechanisms improve software maintainability without hindering software robustness. However, there is still little empirical knowledge about the impact that adopting these mechanisms have on software robustness. This work addresses this gap by conducting an empirical study aimed at understanding the relationship between changes in C# programs and their robustness. In particular, we evaluated how changes in the normal and exceptional code were related to exception handling faults. We applied a change impact analysis and a control flow analysis in 100 versions of 16 C# programs. The results showed that: (i) most of the problems hindering software robustness in those programs are caused by changes in the normal code, (ii) many potential faults were introduced even when improving exception handling in C# code, and (iii) faults are often facilitated by the maintenance-driven flexibility of the exception handling mechanism. Moreover, we present a series of change scenarios that decrease the program robustness / As linguagens de programa??o convencionais fornecem mecanismos de tratamento de exce??es internos a fim de prover implementa??o de tratamento de exce??es em sistemas de software robusto e manuten?vel. A maioria dessas linguagens modernas, tais como C#, Ruby, Python e muitas outras, frequentemente afirmaram ter mecanismos de tratamento de exce??o mais apropriados. Elas reduzem as restri??es de programa??o no tratamento de exce??o buscando agilizar mudan?as no c?digo fonte. Essas linguagens suportam o que chamamos de mecanismos de tratamento de exce??es dirigidos a manuten??o. Espera-se que a ado??o desses mecanismos aumentem a manutenibilidade dos softwares sem impactar na robustez. Entretanto ainda existe pouco conhecimento emp?rico acerca do impacto que a ado??o desses mecanismos tem na robustez de softwares. Este trabalho busca preencher essa lacuna conduzindo um estudo emp?rico direcionado ao entendimento da rela??o entre mudan?as em programas C# e sua robustez. Em particular, n?s avaliamos como mudan?as nos c?digos normal e excepcional se relacionam com faltas no tratamento de exce??o. N?s aplicamos uma an?lise de impacto de mudan?a e uma an?lise de fluxo de controle em 100 vers?es de 16 programas escritos em C#. A partir dos dados coletados, este trabalho identificou os elementos do trade-off entre manutenibilidade e robustez

Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2017-01-12T13:24:40Z No. of bitstreams: 1 JoilsonVidalAbrantes_DISSERT.pdf: 2404682 bytes, checksum: d60333810463c26554d8e41bfe6683fb (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2017-01-16T15:05:25Z (GMT) No. of bitstreams: 1 JoilsonVidalAbrantes_DISSERT.pdf: 2404682 bytes, checksum: d60333810463c26554d8e41bfe6683fb (MD5) / Made available in DSpace on 2017-01-16T15:05:25Z (GMT). No. of bitstreams: 1 JoilsonVidalAbrantes_DISSERT.pdf: 2404682 bytes, checksum: d60333810463c26554d8e41bfe6683fb (MD5) Previous issue date: 2016-02-25 / A pol?tica de tratamento de exce??es de um sistema compreende o conjunto de regras de design que especificam o comportamento e tratamento das condi??es excepcionais, ou seja, define como as exce??es devem ser manuseadas e disparadas. Essa pol?tica geralmente n?o ? documentada e fica definida implicitamente pelo arquiteto do sistema. Por essa raz?o os desenvolvedores podem pensar que apenas inserindo blocos try-cach em todos locais onde exce??es podem potencialmente ser lan?adas est?o lidando adequadamente com as condi??es excepcionais de um sistema. Por?m este comportamento pode transformar o tratamento das condi??es excepcionais em uma generaliza??o do mecanismo "goto", tornando o programa mais complexo e menos confi?vel. Este trabalho prop?e uma linguagem espec?fica de dom?nio, chamada ECL (Exception Contract Language) para especificar a pol?tica de tratamento de exce??es e uma ferramenta de monitoramento em tempo de execu??o que verifica dinamicamente a pol?tica de tratamento de exce??es. Essa ferramenta ? chamada de DAEH (Dynamic Analysis of Exception Handling e ? implementada na forma de uma biblioteca de aspectos, que pode ser adicionada a uma aplica??o Java sem a necessidade de alterar o c?digo fonte da mesma. Esta abordagem foi aplicada a dois sistemas WEB, a quatro vers?es do framework JUnit e a uma aplicatica??o m?vel. Os resultados indicam que esta abordagem pode ser usada para expressar e automaticamente verificar a pol?tica de tratamento de exce??es de sistemas, e, consequentemente apoiar o desenvolvimento de sistemas Java mais robustos. / The exception handling policy of a system comprises the set of design rules that specify its exception handling behavior how exceptions should be handled and thrown. Such policy is usually undocumented and implicitly defined by the system architect. For that reason, the developers may think that by just sprinkling the with catch-blocks in all places where exceptions may potentially be released they are adequately dealing with the exceptional conditions of a system. This lack of information may turn the exception handling into a generalized "goto"mechanism making the program more complex and less reliable. This work proposes a domain - specific language called ECL (Exception Contract Language) to specify the exception handling policy and a runtime monitoring tool which dynamically checks thise policy. This tool is called DAEH (Dynamic Analysis Of Exception Handling). It is implemented in the form of an aspect library, which can added to any Java system without the need to change the application source code. We applied this approach to two large-scale WEB systems and to the a set of versions to the well-known JUnit framework and a mobile application. The results indicate that this approach can be used to express and automatically check the exception handling policy of a system, and consequently support the development of more robust Java systems and more robust.

Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2017-06-02T19:19:17Z No. of bitstreams: 1 TaizaRabelloMontenegro_DISSERT.pdf: 2317460 bytes, checksum: 372e57740f0bdb5c6fc0cdd5a279c949 (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2017-06-05T20:02:53Z (GMT) No. of bitstreams: 1 TaizaRabelloMontenegro_DISSERT.pdf: 2317460 bytes, checksum: 372e57740f0bdb5c6fc0cdd5a279c949 (MD5) / Made available in DSpace on 2017-06-05T20:02:53Z (GMT). No. of bitstreams: 1 TaizaRabelloMontenegro_DISSERT.pdf: 2317460 bytes, checksum: 372e57740f0bdb5c6fc0cdd5a279c949 (MD5) Previous issue date: 2017-02-20 / Na medida em que aumenta a depend?ncia da sociedade com os sistemas de software, aumenta tamb?m a demanda pela robustez destes sistemas. O tratamento de exce??es ? uma das t?cnicas mais utilizadas para a constru??o de sistemas de software robustos. A pol?tica de tratamento de exce??es ? o conjunto de regras que define como as exce??es devem ser manuseadas. Por?m, na maioria dos casos, essa pol?tica n?o est? definida de forma expl?cita, sendo um desafio para o desenvolvedor criar o c?digo de tratamento de exce??es. Este trabalho prop?e uma ferramenta em formato de plug-in do Eclipse, denominada ExceptionPolicyExpert, que tem o objetivo de orientar o desenvolvedor na implementa??o desse tipo de c?digo de forma a atender uma pol?tica previamente definida. Esta ferramenta analisa o c?digo fonte e verifica se h? alguma viola??o ? pol?tica de tratamento de exce??es, alertando o desenvolvedor para n?o conformidade, caso exista. Para auxiliar o levantamento dos requisitos da ferramenta, foi realizado um estudo explorat?rio com desenvolvedores, utilizando t?cnicas de Grounded Theory, que buscou entender quais eram os principais desafios deles no momento da implementa??o do c?digo de tratamento de exce??es. O estudo mostrou que a maioria deles n?o recebem orienta??es a respeito da pol?tica de tratamento de exce??es e nem tem acesso ? pol?tica de tratamento de exce??es a ser seguida. Consequentemente, muitas vezes lidam com esse c?digo de forma indevida. Dessa forma, foi proposta uma ferramenta que visa trazer informa??es sobre a pol?tica de tratamento de exce??es para a IDE, de forma que auxilie o desenvolvedor na implementa??o do c?digo excepcional sem violar a pol?tica. A avalia??o da ferramenta mostrou que ela auxilia o desenvolvedor a tomar decis?es no momento da implementa??o do c?digo de tratamento de exce??es. / As our society becomes more and more dependent of software systems the demand robustness requirements increases. The exception handling mechanism is one of the most used techniques to enable the development of robust software systems develop. The exception handling policy comprises the set of rules that specify how exceptions should be thrown and handled inside a system. But usually the policy is not explicitly defined. As a consequence, it becomes a challenge for developers to create the exception handling code according to it. This work proposes an Eclipse plug-in, called ExceptionPolicyExpert, to guide the developer on how to implement this kind of code by checking policy violations and providing recommendations to developers concerning how to exceptions should be handled and signaled. In order to support the creation of such tool, we performed an exploratory study, using Grounded Theory techniques, to understand which are the main challenges that the developers have during the implementation of the exception handling code. This study showed that most of the developers did not receive any instructions regarding the exception handling policy and they often handle exceptions in a wrong way. Therefore, the proposed tool aims to provide information to developer regarding the exception handling policy integrated to the IDE - helping him/her to develop exception handling code and preventing policy violations. The tool evaluation showed that the tool helps the developer to make decisions when implementing the exception handling code.

Submitted by Caroline Xavier (caroline.xavier@pucrs.br) on 2017-06-30T14:12:14Z No. of bitstreams: 1 DIS_LUCAS_E_SILVA_BATISTA_PILAU_PARCIAL.pdf: 667865 bytes, checksum: b9e4029677e6d1a430ed423abfda23f3 (MD5) / Approved for entry into archive by Caroline Xavier (caroline.xavier@pucrs.br) on 2017-06-30T14:12:22Z (GMT) No. of bitstreams: 1 DIS_LUCAS_E_SILVA_BATISTA_PILAU_PARCIAL.pdf: 667865 bytes, checksum: b9e4029677e6d1a430ed423abfda23f3 (MD5) / Made available in DSpace on 2017-06-30T14:12:29Z (GMT). No. of bitstreams: 1 DIS_LUCAS_E_SILVA_BATISTA_PILAU_PARCIAL.pdf: 667865 bytes, checksum: b9e4029677e6d1a430ed423abfda23f3 (MD5) Previous issue date: 2016-09-26 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior - CAPES / This master?s dissertation has as principal goal to question the existance of a police dispositive, that operationalizes throught the subjectivation and the desubjectivation of individuals and places itself far beyond the modern police institution, affecting not only the operators, in general, of the criminal system, but also the social relations. To confirm this hypothesis, the search initially focus on the Brazilian criminal system and it contemporary double frame, trying to trace, not only the pulsing mass encarceration since the end of the XX century, but also the state crimes against the black and poor population. Furthermore, other goal is to question about the emergency of the modern police, liking it with elementary features of its activities, as well to trace the birth and development of the Brazilian police, not forgetting to localize it on the exception paradigm of Giorgio Agamben, in other words, displacins from a contractualist vision of its activities and showing that Brazilian police are linked both to a fouding and to a conservative violence, spectral quintessentially. Thus, from the police, institution that concetrates the security power in modern democracies, is that seeks to think what represents a police dispositive in power relations and which are the possible interminglings of its crossings. / O presente trabalho vincula-se ? linha de pesquisa Viol?ncia, Crime e Seguran?a P?blica, do Programa de P?s-Gradua??o em Ci?ncias Criminais da Pontif?cia Universidade Cat?lica do Rio Grande do Sul. A pesquisa tem como objetivo interrogar a exist?ncia de um dispositivo policial, o qual operacionaliza-se atrav?s da subjetiva??o e dessubjetiva??o dos indiv?duos e se coloca para muito al?m da institui??o policial moderna, afetando n?o s? os operadores do sistema penal em geral, mas tamb?m as pr?prias rela??es na sociedade. Para confirmar tal hip?tese, a investiga??o se foca inicialmente no sistema penal brasileiro e sua dupla face contempor?nea, tentando tra?ar n?o s? o encarceramento em massa latente desde o final do s?culo XX mas tamb?m os crimes praticados pelo Estado contra a popula??o negra e pobre. Al?m disso, interroga-se o momento de emerg?ncia da pol?cia moderna, vinculando-a a caracter?sticas elementares de sua atua??o, assim como tra?a-se o pr?prio nascimento e desenvolvimento da pol?cia brasileira, sem deixar de localiz?-la, em geral, sob um paradigma de exce??o agambeniano, ou seja, deslocando-se uma vis?o contratualista da sua atua??o e demonstrando estar essa vinculada tanto ? uma viol?ncia fundadora quanto conservadora, espectral por excel?ncia. Assim, a partir da pol?cia, institui??o que concentra o poder de realizar a seguran?a nas democracias modernas, ? que se buscar pensar o que representa um dispositivo policial nas rela??es de poder e quais as imbrica??es poss?veis de seus atravessamentos.

Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2017-04-03T21:33:40Z No. of bitstreams: 1 DaniguiReniguiMartinsDeSouza_DISSERT.pdf: 915908 bytes, checksum: 4d2e4aa8ff487752ec8f6522aad615e8 (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2017-04-10T18:23:44Z (GMT) No. of bitstreams: 1 DaniguiReniguiMartinsDeSouza_DISSERT.pdf: 915908 bytes, checksum: 4d2e4aa8ff487752ec8f6522aad615e8 (MD5) / Made available in DSpace on 2017-04-10T18:23:44Z (GMT). No. of bitstreams: 1 DaniguiReniguiMartinsDeSouza_DISSERT.pdf: 915908 bytes, checksum: 4d2e4aa8ff487752ec8f6522aad615e8 (MD5) Previous issue date: 2017-02-03 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior (CAPES) / O conceito de biopol?tica tem se tornado um rico instrumento de an?lise ou uma esclarecedora chave hermen?utica para a reflex?o contempor?nea sobre a l?gica do poder, a genealogia do governo e o significado da pol?tica no mundo moderno. As diferentes concep??es de biopol?tica t?m cada qual suas especificidades. O foco da abordagem do presente estudo ser? exclusivamente o diagn?stico biopol?tico do presente elaborado por Agamben, no qual o conceito de biopol?tica est? centrado na politiza??o da vida biol?gica. Procuramos mostrar o modo como a ?arqueologia da biopol?tica? empreendida por Agamben pode ser compreendida a partir da an?lise de quatro no??es fundamentais, quais sejam: poder soberano, vida nua, estado de exce??o e campo. Analisamos, primeiro, de que modo Agamben pensou a associa??o entre o dom?nio pol?tico e a animaliza??o do homem a partir das lacunas deixadas pelas investiga??es de Arendt e Foucault. Em um segundo momento, examinamos a rela??o entre a organiza??o soberana dos corpos e o estado de exce??o. No terceiro passo de nosso percurso, analisamos a politiza??o da vida nua e a produ??o do homo sacer, a sacralidade da vida. Em uma quarta e ?ltima etapa, esclarecemos de que modo Agamben pensou o ?campo? como ?n?mos? secreto da biopol?tica na modernidade. Trata-se de explicitar de que forma a reflex?o de Agamben sobre o nexo existente entre poder pol?tico e vida nua se articula em torno desses quatro aspectos estruturantes. Buscamos evidenciar a relevante contribui??o que o pensamento de Agamben oferece para o diagn?stico cr?tico da racionalidade pol?tica nas sociedades contempor?neas, aprimorando nossa compreens?o sobre as novas formas do poder na modernidade tardia. / The concept of biopolitics is a rich instrument of analysis and interpretation of the logic of power, the genealogy of government and the meaning of politics in the modern world. The different conceptions of biopolitics each have their specificities. The focus of the present study will be exclusively the biopolitical diagnosis of the present elaborated by Agamben, in which the concept of biopolitics is centered on the politicization of biological life. We seek to show how Agamben's ?archeology of biopolitics? can be understood from the analysis of four fundamental notions: sovereign power, bare life, state of exception, and field. We first analyze how Agamben thought the association between the political domain and the animalization of man from the gaps left by the investigations of Arendt and Foucault. In a second moment, we examine the relationship between the sovereign organization of bodies and the state of exception. In the third chapter, we analyze the politicization of natural life and the production of homo sacer, the sacred life. In the fourth chapter, we clarified how Agamben thought of the ?field? as a secret ?notion? of biopolitics in modernity. Therefore, we seek to show how Agamben's reflection on the nexus between political power and bare life is articulated around these four structuring aspects. We seek to highlight the relevant contribution that Agamben's thinking offers to the critical diagnosis of political rationality in contemporary societies, enhancing our understanding of the new forms of power in late modernity.

Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2017-11-01T21:17:48Z No. of bitstreams: 1 TeresaDoCarmoBarretoFernandes_DISSERT.pdf: 5261298 bytes, checksum: 1a7e32ec8483e6e7e31101df7f8675f9 (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2017-11-07T21:08:03Z (GMT) No. of bitstreams: 1 TeresaDoCarmoBarretoFernandes_DISSERT.pdf: 5261298 bytes, checksum: 1a7e32ec8483e6e7e31101df7f8675f9 (MD5) / Made available in DSpace on 2017-11-07T21:08:03Z (GMT). No. of bitstreams: 1 TeresaDoCarmoBarretoFernandes_DISSERT.pdf: 5261298 bytes, checksum: 1a7e32ec8483e6e7e31101df7f8675f9 (MD5) Previous issue date: 2017-06-30 / Exce??es n?o capturadas (do ingl?s: uncaught) n?o s?o cen?rios excepcionais nas aplica??es Java atuais. Eles s?o, na verdade, uma das principais causas de falha das aplica??es Java - que podem originar-se de erros de programa??o (e.g., acesso a refer?ncias nulas); falhas no hardware ou em APIs utilizadas. Essas exce??es uncaught resultam em stack traces que s?o frequentemente usados pelos desenvolvedores como fonte de informa??es para a depura??o. Atualmente, essa informa??o ? frequentemente usada pelos desenvolvedores em mecanismos de busca ou sites de perguntas e respostas (do ingl?s: Question and Answer - Q&A) para tentar compreender melhor a causa do crash e assim poder resolv?lo. Este estudo fez a minera??o de stack traces inclu?das nas perguntas e respostas do StackOverflow (SOF). O objetivo deste estudo foi: (i) identificar caracter?sticas das stack traces mineradas do SOF e (ii) investigar como tais informa??es podem ser usadas para evitar exce??es uncaught durante o desenvolvimento de software. Neste estudo, 121.253 stack traces foram extra?das e analisadas em combina??o com inspe??es de postagens do SOF. Tamb?m ? proposta a ferramenta ExMinerSOF, que alerta o desenvolvedor sobre as exce??es que podem ser potencialmente sinalizadas por um m?todo de API. Essas informa??es s?o descobertas aplicando uma estrat?gia de minera??o apresentada neste trabalho. Ao faz?-lo, a ferramenta permite que o desenvolvedor evite falhas com base em falhas relatadas por outros desenvolvedores. / Uncaught exceptions are not an exceptional sce- nario in current Java applications. They are actually one of the main causes of applications crashes, which can originate from programming errors on the application itself (null pointer dereferences); faults in underlying hardware or re-used APIs. Such uncaught exceptions result in exception stack traces that are often used by developers as a source of information for debugging. Currently, this information is ofttimes used by developers on search engines or Question and Answer sites while the developer tries to: better understand the cause of the crash and solve it. This study mined the exception stack traces embedded on StackOverflow (SOF) questions and answers. The goal of this work was to two-fold: to identify characteristics of stack traces mined from SOF and to investigate how such information can be used to prevent uncaught exceptions during software development. Overall 121.253 exception stack traces were extracted and analyzed in combination with Q&A inspections. Hence, this study proposes ExMinerSOF tool, which alerts the developer about the exceptions that can be potentially signaled by an API method but are not part of the API documentation - and was discovered by applying a mining strategy in SOF repository. Doing so, the tool enable the developer to prevent faults based on failures reported by the crowd.

Submitted by Sandra Pereira (srpereira@ufrrj.br) on 2016-10-04T15:05:57Z No. of bitstreams: 1 2011 - Fernanda Maria da Costa Vieira.pdf: 2529012 bytes, checksum: 8d720183f132a0a02064c33bb6f76838 (MD5) / Made available in DSpace on 2016-10-04T15:05:57Z (GMT). No. of bitstreams: 1 2011 - Fernanda Maria da Costa Vieira.pdf: 2529012 bytes, checksum: 8d720183f132a0a02064c33bb6f76838 (MD5) Previous issue date: 2012-02-28 / Coordena??o de Aperfei?oamento de Pessoal de N?vel Superior - CAPES / In 2007, as the dossier prepared by the Military Police which aimed to investigate the Movement of Landless Rural Workers and their links with the Revolutionary Armed Forces of Colombia in the north of Rio Grande do Sul, a series of legal actions have been developed , which disclose a conflict that surpasses the competition for territory and political projects and land from the Agricultural Federation of the State of Rio Grande do Sul X MST, with the significant role of the State and Federal Judiciary and the Ministry of Carazinho State and Federal Public , which features the criminal action based on the National Security Law (Law No. 7170/83) and public civil actions that aimed to reduce the performance of the MST, and the resolution of the Board of the Public Prosecutor decided that the extinction of the MST. We understand that the rescue of history that the criminal act is indicative of the current scenario of growth of speeches punitive brand of neoliberal hegemony, where there is an expansion of the processes of criminalization of poverty in general and social movements vindicated, territories marked by the unveiling concept of state of exception, while presenting a line (not so) continued with the colonial past, which is based on the notion of control and submission of the popular classes through the criminal statute. / Em 2007, a partir do dossi? elaborado pelo Brigada Militar, que se propunha a investigar o Movimento dos Trabalhadores Rurais Sem Terra e seus v?nculos com as For?as Armadas Revolucion?rias da Col?mbia na regi?o Norte do Rio Grande do Sul, uma s?rie de a??es jur?dicas foram desenvolvidas, que desvelam um conflito que ultrapassa a disputa pelo territ?rio e de projetos pol?ticos e agr?rios entre Federa??o da Agricultura do Estado do Rio Grande do Sul X MST, contando com a atua??o significativa dos Judici?rios Estadual e Federal de Carazinho e do Minist?rio P?blico Estadual e Federal, onde se destacam a a??o penal com base na Lei de Seguran?a Nacional (Lei n? 7170/83) e A??es Civis P?blicas que objetivavam reduzir a atua??o do MST, bem como a delibera??o do Conselho Superior do Minist?rio P?blico que deliberou pela extin??o do MST. Entendemos que o resgate da hist?ria que gestou a a??o penal ? reveladora do cen?rio atual de crescimento dos discursos punitivos, marca da hegemonia neoliberal, onde se percebe uma amplia??o dos processos de criminaliza??o da pobreza em geral e dos movimentos sociais reivindicat?rios, desvelando territ?rios marcados pelo conceito de estado de exce??o, ao mesmo tempo em que apresenta uma linha (n?o t?o) cont?nua com o passado colonial, que se assenta na no??o de controle e submiss?o das classes populares por meio do estatuto penal.

Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2016-03-09T23:06:18Z No. of bitstreams: 1 JoseAlexMedeirosDeLima_DISSERT.pdf: 2415458 bytes, checksum: 5a42b81151bcf9ace7867b8305c4dc65 (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2016-03-11T19:45:39Z (GMT) No. of bitstreams: 1 JoseAlexMedeirosDeLima_DISSERT.pdf: 2415458 bytes, checksum: 5a42b81151bcf9ace7867b8305c4dc65 (MD5) / Made available in DSpace on 2016-03-11T19:45:39Z (GMT). No. of bitstreams: 1 JoseAlexMedeirosDeLima_DISSERT.pdf: 2415458 bytes, checksum: 5a42b81151bcf9ace7867b8305c4dc65 (MD5) Previous issue date: 2015-02-27 / Alta confiabilidade, disponibilidade e toler?ncia ? falha ainda s?o problemas em aberto em arquiteturas orientadas a servi?os (SOA). A possibilidade de gera??o de aplica??es de software, integrando servi?os de dom?nios heterog?neos, de uma forma mais confi?vel, faz valer a pena enfrentar os desafios inerentes a esse paradigma. Para garantir a qualidade na composi??o desses servi?os, algumas pesquisas se esfor?am para propor a ado??o de t?cnicas de verifica??o para identificar e corrigir os erros. Nesse contexto, manipula??o de exce??o ? um poderoso mecanismo para incrementar a qualidade em SOA. Diversos trabalhos de pesquisa s?o concentrados em mecanismos para propaga??o de exce??o em servi?os web, implementados em muitas linguagens e frameworks. No entanto, para a extens?o do nosso conhecimento, n?o s?o encontrados trabalhos que avaliam esses mecanismos em SOA no que diz respeito ao framework .NET. A principal contribui??o desse trabalho ? avaliar e propor mecanismos de propaga??o de exce??o em SOA para aplica??es desenvolvidas com o framework .NET. Nessa dire??o, esse trabalho: (i) estende um estudo anterior, mostrando a necessidade de se propor uma solu??o para a propaga??o de exce??o em SOA para aplica??es desenvolvidas em .NET, e (ii) apresenta uma solu??o, tomando como base um modelo obtido a partir dos resultados encontrados em (iii) e implementa e avalia a solu??o proposta em duas aplica??es reais. / High dependability, availability and fault-tolerance are open problems in Service-Oriented Architecture (SOA). The possibility of generating software applications by integrating services from heterogeneous domains, in a reliable way, makes worthwhile to face the challenges inherent to this paradigm. In order to ensure quality in service compositions, some research efforts propose the adoption of verification techniques to identify and correct errors. In this context, exception handling is a powerful mechanism to increase SOA quality. Several research works are concerned with mechanisms for exception propagation on web services, implemented in many languages and frameworks. However, to the extent of our knowledge, no works found evaluates these mechanisms in SOA with regard to the .NET framework. The main contribution of this paper is to evaluate and to propose exception propagation mechanisms in SOA to applications developed within the .NET framework. In this direction, this work: (i)extends a previous study, showing the need to propose a solution to the exception propagation in SOA to applications developed in .NET, and (ii) show a solution, based in model obtained from the results found in (i) and that will be applied in real cases through of faults injections and AOP techniques.

Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2017-02-20T21:14:31Z No. of bitstreams: 1 FranciscoDiogoOliveiraDeQueiroz_DISSERT.pdf: 2384075 bytes, checksum: 6637cd90d60ea8666ced83de9d255a5f (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2017-02-23T00:25:27Z (GMT) No. of bitstreams: 1 FranciscoDiogoOliveiraDeQueiroz_DISSERT.pdf: 2384075 bytes, checksum: 6637cd90d60ea8666ced83de9d255a5f (MD5) / Made available in DSpace on 2017-02-23T00:25:27Z (GMT). No. of bitstreams: 1 FranciscoDiogoOliveiraDeQueiroz_DISSERT.pdf: 2384075 bytes, checksum: 6637cd90d60ea8666ced83de9d255a5f (MD5) Previous issue date: 2016-08-17 / Com a ascens?o da tecnologia m?vel nos ?ltimos anos, dispositivos como smartphones e tablets t?m se tornado parte integral da vida das pessoas. Como telefones tradicionais, os smartphones podem ser utilizados para realizar chamadas e mandar mensagens de texto, mas ? a possibilidade de fornecer variados tipos de aplica??es que os tornam t?o atrativos para seus usu?rios. Neste contexto, aplica??es Android tem se tornado cada vez mais populares; e no mesmo ritmo em que cresce o n?mero de aplica??es dispon?veis, tamb?m cresce o n?mero de usu?rios afetados pelos crashes de tais aplica??es. Para poder lidar com tais condi??es excepcionais, o c?digo para lan?amento e captura de exce??es n?o ? uma parte opcional mas uma parte fundamental de tais aplica??es. Por?m, o que se tem observado ? que o c?digo projetado para tratar estas condi??es excepcionais pode muitas vezes ser a causa de crashes (e.g., exce??es n?o capturadas). At? o momento nenhum estudo investigou as principais caracter?sticas do c?digo de tratamento de exce??es (TE) de aplica??es Android. Este trabalho apresenta um conjunto de estudos complementares para melhor entender as caracter?sticas do c?digo de TE de aplica??es Android assim como identificar a vis?o dos desenvolvedores a respeito destas caracter?sticas. Neste trabalho foram realizados tr?s estudos: (i) um estudo explorat?rio onde foram inspecionados o c?digo de TE de 15 aplica??es Android populares (o que no total correspondeu a 3490 blocos try-catch-finally); e (ii) dois estudos qualitativos baseados em t?cnicas de Teoria Fundamentada em Dados - nestes foram aplicados surveys a 28 desenvolvedores Android e 47 especialistas Android para levantar a opini?o dos mesmos sobre boas e m?s praticas no desenvolvimento do tratamento de exce??es no ambiente Android. Durante estes estudos observamos um grande n?mero de exce??es sendo silenciadas no c?digo de apps. Tamb?m observamos que poucas aplica??es enviavam informa??es as informa??es sobre as exce??es uncaught para servidores de crash report. / Along the recent years, we have witnessed an astonishing increase in the number mobile applications being developed and some of them becoming largely used. Such applications extend phones capabilities far beyond of the basic calls. In the same rate the number of a users increase, also increases the number of users affected by application faults and crashes. In this contexto, Android apps are becoming more and more popular. The number of such apps is astonishingly increasing in a daily rate, as well as the number of users affected by their crashes. Android apps as other Java apps may crash due to faults on the exception handling (EH) code (e.g. uncaught exceptions). Techniques for exception detection and handling are not an optional add-on but a fundamental part of such apps. Yet, no study has investigated the main characteristics of the EH code of mobile apps nor the developers perspective about the good and bad practices of EH in such context. In this work we conducted three complementary studies: (i) one that inspected the EH code of 15 popular Android apps (which overall comprises of 3490 try-catch-finally blocks); and two qualitative studies based an Grounded Theory techniques, on which two surveys were applied to 28 Adndroid developers and 47 Android experts respectively, to get their opinion about the good and bad practices of EH development in Android environment. Some outcomes of the studies show a high occurrence of exception swallowing and only few apps sending exception information to a remote server ? both considered by Android experts as bad practices that negatively impact the app robustness.