Submitted by Automa??o e Estat?stica (sst@bczm.ufrn.br) on 2017-11-01T21:17:50Z No. of bitstreams: 1 JoaoHelisJuniorDeAzevedoBernardo_DISSERT.pdf: 3484130 bytes, checksum: f8c6117ef3a3facccdfb4317e8e41c61 (MD5) / Approved for entry into archive by Arlan Eloi Leite Silva (eloihistoriador@yahoo.com.br) on 2017-11-07T22:16:31Z (GMT) No. of bitstreams: 1 JoaoHelisJuniorDeAzevedoBernardo_DISSERT.pdf: 3484130 bytes, checksum: f8c6117ef3a3facccdfb4317e8e41c61 (MD5) / Made available in DSpace on 2017-11-07T22:16:31Z (GMT). No. of bitstreams: 1 JoaoHelisJuniorDeAzevedoBernardo_DISSERT.pdf: 3484130 bytes, checksum: f8c6117ef3a3facccdfb4317e8e41c61 (MD5) Previous issue date: 2017-07-31 / Conselho Nacional de Desenvolvimento Cient?fico e Tecnol?gico (CNPq) / A Integra??o Cont?nua (IC) ? uma pr?tica de desenvolvimento de software que leva os desenvolvedores a integrarem seu c?digo-fonte mais frequentemente. Projetos de software t?m adotado amplamente a IC com o intuito de melhorar a integra??o de c?digo e lan?ar novas releases mais rapidamente para os seus usu?rios. A ado??o da IC ? usualmente motivada pela atra??o de entregar novas funcionalidades do software de forma mais r?pida e frequente. Todavia, h? poucas evid?ncias emp?ricas para justificar tais alega??es. Ao longo dos ?ltimos anos, muitos projetos de software dispon?veis em ambientes de codifica??o social, como o GitHub, tem adotado a pr?tica da IC usando servi?os que podem ser facilmente integrados nesses ambientes (por exemplo, Travis-CI). Esta disserta??o investiga empiricamente o impacto da ado??o da IC no tempo de entrega de pull requests (PRs), atrav?s da an?lise de 167.037 PRs de 90 projetos do GitHub que s?o implementados em 5 linguagens de programa??o diferentes. Ao analisar a porcentagem de merged PRs por projeto que perderam pelo menos uma release antes de serem entregues aos usu?rios finais, os resultados mostraram que antes da ado??o da IC, em mediana 13.8% dos merged PRs tem sua entrega adiada por pelo menos um release, enquanto que ap?s a ado??o da IC, em mediana 24% dos merged PRs tem sua entrega adiada para futuras releases. Ao contr?rio do que se pode especular, observou-se que PRs tendem a esperar mais tempo para serem entregues ap?s a ado??o da IC na maioria (53%) dos projetos investigados. O grande aumento das submiss?es de PRs ap?s a IC ? uma raz?o fundamental para que projetos demorem mais tempo para entregar PRs depois da ado??o da IC. 77,8% dos projetos aumentam a taxa de submiss?es de PRs ap?s a ado??o da IC. Com o prop?sito de investigar os fatores relacionados ao tempo de entrega de merged PRs, treinou-se modelos de regress?o linear e log?stica, os quais obtiveram R-Quadrado mediano de 0.72-0.74 e bons valores medianos de AUC de 0.85-0.90. An?lises mais profundas de nossos modelos sugerem que, antes e depois da ado??o da IC, a intensidade das contribui??es de c?digo para uma release pode aumentar o tempo de entrega de PRs devido a uma maior carga de integra??o (em termos de commits integrados) da equipe de desenvolvimento. Finalmente, apresentamos heur?sticas capazes de identificar com precis?o os PRs que possuem um tempo de entrega prolongado. Nossos modelos de regress?o obtiveram valores de AUC mediano de 0.92 a 0.97. / Continuous Integration (CI) is a software development practice that leads developers to integrate their work more frequently. Software projects have broadly adopted CI to ship new releases more frequently and to improve code integration. The adoption of CI is usually motivated by the allure of delivering new software content more quickly and frequently. However, there is little empirical evidence to support such claims. Over the last years, many available software projects from social coding environments such as GitHub have adopted the CI practice using CI facilities that are integrated in these environments (e.g., Travis-CI). In this dissertation, we empirically investigate the impact of adopting CI on the time-to-delivery of pull requests (PRs), through the analysis of 167,037 PRs of 90 GitHub projects that are implemented in 5 different programming languages. On analyzing the percentage of merged PRs per project that missed at least one release prior being delivered to the end users, the results show that before adopting CI, a median of 13.8% of merged PRs are postponed by at least one release, while after adopting CI, a median of 24% of merged PRs have their delivery postponed to future releases. Contrary to what one might speculate, we find that PRs tend to wait longer to be delivered after the adoption of CI in the majority (53%) of the studied projects. The large increase of PR submissions after CI is a key reason as to why these projects deliver PRs more slowly after adopting CI. 77.8% of the projects increase the rate of PR submissions after adopting CI. To investigate the factors that are related to the time-to-delivery of merged PRs, we train linear and logistic regression models, which obtain sound median R-squares of 0.72-0.74, and good median AUC values of 0.85-0.90. A deeper analysis of our models suggests that, before and after the adoption of CI, the intensity of code contributions to a release may increase the delivery time due to a higher integration-load (in terms of integrated commits) of the development team. Finally, we are able to accurately identify merged pull requests that have a prolonged delivery time. Our regression models obtained median AUC values of 0.92 to 0.97.

Nous avons observé l’aide dans l’interaction entre enfants et enseignants, avec une perspective moins centrée sur l’apprentissage que sur les enjeux relationnels entre les acteurs. Les manières dont l’aide est apportée par le maître aux élèves montrent comment se construit au coup par coup le rapport de dépendance et d’autonomie qui fonde les relations humaines. Notre recherche s’inscrit dans le cadre de l’Analyse des Discours en Interaction. La visée est descriptive : à partir d’un corpus filmé de quatre classes de grande section de maternelle et de CM2, nous avons analysé les échanges entre enseignant et élèves en tenant compte du contexte de communication spécifique. Dans l’échange d’aide, on peut distinguer trois moments : (1) le déclencheur de l’aide : une action de l’élève (verbale ou non verbale) provoque la réponse aidante de l’enseignant. Le déclencheur peut être explicitement une demande d’aide ou un autre acte (demande de validation, signe d’inactivité ou de découragement) que l’enseignant interprète comme un besoin d’aide ;(2) l’aide proprement dite : action verbale ou non verbale, plus ou moins directive, dont la fonction peut être plus ou moins cognitive ou technique (tenir la main pour écrire ou relire une consigne) ou affective (une parole qui motive et encourage) ;(3) la clôture : les événements qui déclenchent la séparation de l’aidé et de l’aidant ainsi que la manière dont ils se quittent après un échange d’aide. / We have examined the functioning of help in the children - teacher's interaction, focussing on the participants' relations more than on learning issues. The ways in which teachers provide help to pupils show how a balance between dependence and autonomy is reached in their relation in an ad hoc manner.Our research relies on the framework of Analysis of Talk in Interaction, and has a descriptive purpose. On the basis of video-recordings of four classes of kindergarten and CM2, we have analyzed exchanges between teacher and pupils taking into account the specificity of the didactic context.In "help exchange", we can distinguish three stages:(1) The event that triggers help out: a pupil's action (be it verbal or not) triggers out a helping response by the teacher. The source event can be an explicit request for help or another act (like a request for validation, a sign of inactivity or of discouragement) that the teacher interprets as a need of assistance;(2) The help itself: verbal or nonverbal action, which can be more or less directive, and whose function can be more or less cognitive or technical (holding hands to write, or read an instruction) or emotional (a word that motivates, and encourages);(3) Closing: the events that trigger the separation of the "helper" and the "helper" out, and the way in which they leave after an exchange of help.

Made available in DSpace on 2014-06-12T15:53:57Z (GMT). No. of bitstreams: 2 arquivo1938_1.pdf: 2696606 bytes, checksum: c2ff3cbbb3029fd0f89eb8d67c0e4f08 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2009 / Manutenção e evolução de software são atividades caracterizadas pelo seu enorme custo e baixa velocidade de execução. Não obstante, elas são atividades inevitáveis para garantir a qualidade do software quase todo software bem sucedido estimula os usuários a fazer pedidos de mudanças e melhorias. Sommerville é ainda mais enfático e diz que mudanças em projetos de software são um fato. Além disso, diferentes estudos têm afirmado ao longo dos anos que as atividades de manutenção e evolução de software são as mais caras do ciclo de desenvolvimento, sendo responsável por cerca de até 90% dos custos. Todas essas peculiaridades da fase de manutenção e evolução de software leva o mundo acadêmico e industrial a investigar constantemente novas soluções para reduzir os custos dessas atividades. Neste contexto, Gerência de Configuração de Software (GCS) é um conjunto de atividades e normas para a gestão da evolução e manutenção de software; GCS define como são registradas e processadas todas as modificações, o impacto das mesmas em todo o sistema, dentre outros procedimentos. Para todas estas tarefas de GCM existem diferentes ferramentas de auxílio, tais como sistemas de controle de versão e bug trackers. No entanto, alguns problemas podem surgir devido ao uso das mesmas, como por exemplo o problema de atribuição automática de responsável por um bug report e o problema de duplicação de bug reports. Neste sentido, esta dissertação investiga o problema de duplicação de bug reports resultante da utilização de bug trackers em projetos de desenvolvimento de software. Tal problema é caracterizado pela submissão de dois ou mais bug reports que descrevem o mesmo problema referente a um software, tendo como principais conseqüências a sobrecarga de trabalho na busca e análise de bug reports, e o mal aproveitamento do tempo destinado a essa atividade

Orientador: Walter da Cunha Borelli / Dissertação (mestrado) - Universidade Estadual de Campinas, Faculdade de Engenharia Eletrica e de Computação / Made available in DSpace on 2018-07-23T08:02:09Z (GMT). No. of bitstreams: 1 Macario_CarlaGeovanadoNascimento_M.pdf: 8704471 bytes, checksum: bee9de6493b42d0139961cb43f32cb24 (MD5) Previous issue date: 1997 / Resumo: Este trabalho propõe uma metodologia alternativa para o desenvolvimento e evolução do AIOA, um software para o gerenciamento e análise de dados experimentais, em desenvolvimento na Embrapa. Esta nova metodologia consiste no uso combinado da técnica OMT (Object Modeling Technique) com a linguagem de especificação formal SOL (Specification and Oescription Language), e apresenta facilidades que produzem ga¿n ANTPOT. H¿os no processo de desenvolvimento de software, como a possibilidade de validação e de simulação do sistema, e também a geração de código para sua prototipação. A partir do modelo de classes proposto pela OMT, passa-se à especificação do sistema em SOL, levando-se em conta na elaboração de ambos os modelos, conceitos como reuso, herança e evolução de sistemas. A validação, a simulação e a geração de código do sistema tornam-se possíveis com o uso da ferramenta CASE SOT1(SOL Oesign Tool - Telelogic, Suécia). É apresentada a evolução do ambiente AIOA centralizado até uma versão distribuída, considerando uma arquitetura cliente-servidor com mecanismo CORBA, bem como exemplos de simulação e de validação destes sistemas / Abstract: The present work proposes an alternative methodology for the development and evolution of AIOA, a software environment for the management and analysis of experimental data, being developed at Embrapa, Brazil. This new technique consists of the combined use of OMT (Object Modeling Technique) with the formal specification language SDL (Specification and Description Language), in its 1992 version SDL-92, presenting strong facilities on the software development process, allowing the validation, simulation and eventual code generation for software prototyping. From the system object model and after mapping to SOL-92, the formal specification is generated considering concepts such as reuse, inheritance, and system evolution. The validation, the simulation and code generation of the system is allowed through the use of the CASE tool SOT (SOL Oesign Tool - Telelogic, Sweden). The specification of the centralized AIOA to its evolution to distributed version are presented, validated and simulated. This is followed up with a specialization and validation of thedistributed AIOA, considering an arquitecture client-server with CORBA mechanism / Mestrado / Telecomunicações e Telemática / Mestre em Engenharia Elétrica

Most of the people in the industrial world are using several web applications every day. Many of those web applications contain vulnerabilities that can allow attackers to steal sensitive data from the web application's users. One way to detect these vulnerabilities is to have a penetration tester examine the web application. A common way to train penetration testers to find vulnerabilities is to challenge them with realistic web applications that contain vulnerabilities. The penetration tester's assignment is to try to locate and exploit the vulnerabilities in the web application. Training on the same web application twice will not provide any new challenges to the penetration tester, because the penetration tester already knows how to exploit all the vulnerabilities in the web application. Therefore, a vast number of web applications and variants of web applications are needed to train on. This thesis describes a tool designed and developed to automatically generate vulnerable web applications. First a web application is prepared, so that the tool can generate a vulnerable version of the web application. The tool injects Cross Site Scripting (XSS) and Cross Site Request Forgery (CSRF) vulnerabilities in prepared web applications. Different variations of the same vulnerability can also be injected, so that different methods are needed to exploit the vulnerability depending on the variation. A purpose of the tool is that it should generate web applications which shall be used to train penetration testers, and some of the vulnerabilities the tool can inject, cannot be detected by current free web application vulnerability scanners, and would thus need to be detected by a penetration tester. To inject the vulnerabilities, the tool uses abstract syntax trees and taint analysis to detect where vulnerabilities can be injected in the prepared web applications. Tests confirm that web application vulnerability scanners cannot find all the vulnerabilities on the web applications which have been generated by the tool.

The subject of this thesis consists in comparing means of request expression in French and Czech language in pursuit of scaling them by their politeness level, taking into account the socio-pragmatic environment of both languages. Apart from that, a syntactic realisation of request is analysed in both languages as well as morphological, lexical and stylistic instruments that either increase or decrease the degree of politeness and the effect of performed request. Attention is primarily focused on indirect requests in both French and Czech in order to identify an appropriate translation equivalent expressing the same degree of politeness. The fundamental source for the contrastive analysis lies in InterCorp parallel corpus data. This research is further extended with survey that verifies the previous findings.

Diploma thesis is focused on evaluation of communication streams in the process of application support also known under the term IT support. Thesis is divided into three main parts: In the first part outlines the topic of application support. The definition of term, relation between business and IT and defining the position of application support in the process of information system development along with support services methodologies. The second part is focused on description of typical user of application support, from the side of sponsor as well as from the side of supplier. The following are the main communication streams between both sides as well as inside the supplier team. The third, practical part contains an analysis of application support on a specific project. Discussed are communication barriers, their impact including suggestions for improvement.

The topic of this Master Thesis is Incident Management process as well as other processes which are inseparably linked to it, such as Problem Management, Change Management, Knowledge Management, etc. Main focus of this work is taken to the mentioned processes implementation in the real environment of the real company. Those processes are to be supported by selected information system whereas the selection itself is also part of the project. The processess are compared and optimized with use of Information Technology Infrastructure Library (ITIL).

Cílem této práce je vytvořit komunikační sběrnici pro platformu Testos, což umožní nástrojům platformy spolu komunikovat a využívat navzájem svoje služby. V textu jsou prozkoum8na současná řešení a protokoly založené na modelu Publish-Subscribe. Dále také práce specifikuje požadavky na komunikační sběrnici vyhovující potřebám platformy Testos a také navrhuje řešení pro splnění daných požadavků.   V rámci výzkumu byly prozkoumány tři řešení - MQTT, DDS a AMQP. Průzkum každého řešení byl zaměřen na způsob komunikace a hlavní funkční prvky. Jako startovací bod implementace sběrnice byl vybrán protokol MQTT. Tato práce také specifikuje jak tento protokol rozšířit, aby byly splněny požadavky na sběrnici. Mezi stěžejní rozšíření navrhnuté v rámci této práce patří management životního cyklu požadavků rozšiřující způsob doručování zpráv a mechanismus zasílání požadavků standardu MQTT. Protokol byl také rozšířen o možnost shlukování zpráv do BULK paketu za účelem snížení množství potřebných síťových zdrojů. Výsledkem je Testos Bus, který je postavený na upraveném a rozšířeném protokolu MQTT, který zahrunuje implementaci brokeru a klientských knihoven pro Python a C++. Testos Bus naplňuje všechny povinné požadavky platformy, což ověřují automatické testy.

The thesis monitors the distribution logistics of company CommScope at the local and corporate level. The aim of this work is the optimization of the current state and the proposal to use the combined mode of transport for the largest customer in Europe. The theoretical part is focused on the current method of arranging transport and carrier choise. The practical part is a detailed analysis of the road transport from manufacturer to the customer and proposal for using an alternative mode of combined transporport is formulated.