Boutons « J’aime », tweets ancrés… Toutes ces formes sont générées par des interfaces de programmation ou API, outils d’écriture informatique qui ont integré la chaîne de production des textes de réseau contemporains. Cette thèse interroge la fonction éditoriale des API, soit leur rôle dans la production, la standardisation et la circulation des « petites formes » des textes de réseau. Avec comme corpus les API de Facebook et de Twitter ainsi que les petites formes qu’elles permettent de produire, notre analyse techno-sémiotique s’articule en cinq chapitres. Le premier est une généalogie des API du point de vue de l’écriture combinatoire. Nous montrons que cette conception de l’écriture est un trait saillant de la programmation et de l’informatique. Le second chapitre interroge les imaginaires de l’écriture informatique, entre chiffre, combinatoire et méthode scientifique universelle. Le troisième chapitre est une analyse des conséquences sémiotiques de cet universalisme combinatoire, où nous montrons que les API proposent une conception du texte comme ensemble abstrait de blocs combinables. Abstraction du texte qui sert une « économie des passages », objet de notre quatrième chapitre, dans laquelle les API sont des lieux d’industrialisation d’une « pratique lettrée » : elles établissent des critères de lisibilité et de reproductibilité du texte. Parmi ces critères, nous notons une invisibilisation du rôle pourtant fondamental du calcul informatique. Nous proposons donc, dans un cinquième chapitre, des pistes pour développer une sémiotique qui prenne en compte le calcul comme mode d’expression propre aux médias numériques. / « Like » buttons, embedded tweets… All of these visual forms are produced by Application Programming Interfaces (APIs). APIs are digital writing tools which have become part of the publishing process of contemporary web pages. This thesis aims at understanding the « publishing function » of APIs : their role in the production, standardization and circulation of the « little forms » of online texts. Focused on Facebook’s and Twitter’s APIs, our work is divided into five chapters. The first one is a genealogy of the APIs, starting from their combinatorial aspect, a conception of writing which trace back to early programming and the invention of computer science. The second chapter is an inquiry about the imaginaries of calculus as a kind of writing, torn between the imaginary of numbers, of combinatorics and the search for a universal scientific method. The third chapter is a study of the semiotic consequences of this combinatorial universalism. We show how APIs are based on an idea of text as an abstract, modular object. This abstraction of the text is beneficial to an « economy of passages ». In this economy where circulation produce value, APIs are a place of « literate practices » (chapter four). They establish visual standards for the readability, production and circulation of online texts. Among these standards, there’s a systematic invizibilisation of the action of machines, although calculus is a necessary part of the production of digital texts. Therefore, in the fifth chapter, we give some epistemological elements towards non-anthropocentric semiotics, meaning : semiotics which would take into account computational machines as a part of the utterance of digital texts.

Submitted by Fernando de Assis Rodrigues (fernando@elleth.org) on 2017-03-08T18:31:59Z No. of bitstreams: 79 final.pdf: 41703816 bytes, checksum: f59b8e221e9bc15e9bc0f2579244c6c6 (MD5) 1.png: 295336 bytes, checksum: 459beda12600ba335b293bc6ab407543 (MD5) 2.png: 4275028 bytes, checksum: 61d7e2aeba17cbb6bc721cd955357559 (MD5) 3.png: 4278867 bytes, checksum: 78190c57f8aa4cae32be9ff4e3c2b8b9 (MD5) 4.png: 3413913 bytes, checksum: d98179cd8a1720ec3a2ffe941f2617e0 (MD5) 5.png: 2572352 bytes, checksum: 094e37b003e0099dd78a1ec54ed78cdd (MD5) 6.png: 36209 bytes, checksum: 9e5d19706c8131e6c8d169b779114605 (MD5) 7.png: 13916308 bytes, checksum: 23c1db3f0340ac1e79a86f73bf8b64d9 (MD5) 8.png: 10016221 bytes, checksum: eae1e977ef51ebdf0f46990ee85f830a (MD5) 10.png: 4823750 bytes, checksum: fddce1fe56bc6e50d5aefc7d88a5599b (MD5) 11.png: 15076 bytes, checksum: 8f025ab18b9c12128f26be839fb7e7c6 (MD5) 12.png: 2034468 bytes, checksum: 73296cbf213f9e58b0e812bb82d65854 (MD5) 13.png: 2124812 bytes, checksum: 84a03f6e7edfd66fa4bdd6ede8f8d5e9 (MD5) 14.png: 2198512 bytes, checksum: dfec659b294b885f1d853c6a475a8fee (MD5) 15.png: 2053157 bytes, checksum: 0feab30e0c892b45939f17644d3000cf (MD5) 16.png: 70960 bytes, checksum: a675706ca5e284a01544b772aa354c35 (MD5) 17.png: 501763 bytes, checksum: 9f41bb83cac460cc7aeb618a3b81c623 (MD5) 18.png: 30898 bytes, checksum: 4cad6424be9272a63ad826682ac2cedc (MD5) 19.png: 227247 bytes, checksum: 1df7ea50df51d979d740bd21a78f7192 (MD5) 20.png: 176546 bytes, checksum: 29eca9e49b3ec71fa6438ffa2a90665f (MD5) 21.png: 171097 bytes, checksum: 20e944c37814c57bdb330bcca624142f (MD5) 22.png: 64778 bytes, checksum: eb66e18acd5f0942a332e7ad57b3a475 (MD5) 23.png: 911367 bytes, checksum: f733bd8baeffd584a71cc153e87f3fc0 (MD5) 24.png: 443014 bytes, checksum: dad199a0357cf118c1e834e32f29a656 (MD5) 25.png: 133262 bytes, checksum: d9a29c70f3e1bfaa17682dc06d7a94a8 (MD5) 26.png: 97345 bytes, checksum: 7c4f87d60bfddef584a1e31929b125e3 (MD5) 27.png: 121518 bytes, checksum: b648bdf82f061549b8615a276c35e86b (MD5) 28.png: 3907801 bytes, checksum: bce8b22ee075dd30de8903a89a482a44 (MD5) 29.png: 110594 bytes, checksum: 98d4617ddfc62e5186b2ea50750e145f (MD5) 30.png: 65675 bytes, checksum: d6d0ec7e29b63b3d8f3bbf93b33fe392 (MD5) 31.png: 77259 bytes, checksum: 7c650862e389ee010ebf227394b78ae5 (MD5) 32.png: 224392 bytes, checksum: 0f153cc54827e1e125950ba15a93a064 (MD5) 33.compressao.png: 2342753 bytes, checksum: 243f5209f09cf7b998f6a5e579e4b289 (MD5) 34.png: 13209736 bytes, checksum: a3fca0c436e0167e5292cb47683263c6 (MD5) 35.png: 331900 bytes, checksum: 230d44f9fbbd1d1f1b8e16ef4a90bef4 (MD5) 36.png: 7795486 bytes, checksum: ff219f75dea53645c3c8c506aee4f92c (MD5) 37.png: 53430944 bytes, checksum: 497a9784729f29b143815938b3d4d6dd (MD5) 38.png: 5733799 bytes, checksum: 665d395bae6b16fe105fde18c13bfad8 (MD5) 39.png: 219532 bytes, checksum: 5827b2cc4fdf0f8a4bf716aec8a1c5fa (MD5) 40.png: 127177 bytes, checksum: e152cddfffc9c805a89e5e50b8a1817c (MD5) 41.png: 1124665 bytes, checksum: 29d9fd8d9ee671f2b00643f986ed4ee6 (MD5) 42.png: 2383771 bytes, checksum: 3bf368dce4ef03e41b1b9b321ebf5d6b (MD5) 43.png: 2048283 bytes, checksum: d8c1afc1ff4926f26f87d6da2c340189 (MD5) 44.compressao.png: 4545708 bytes, checksum: 1a244e7d2a77739f25582a39ee0dca43 (MD5) 1.png: 91444 bytes, checksum: 97a9b0c6327395ecf131b7f08f852afe (MD5) 2.png: 93204 bytes, checksum: c4f43e7beace7624decc69d5c0bbd763 (MD5) 3.png: 136229 bytes, checksum: decbc71a5c674b502a19bb7ec3a4af39 (MD5) 4.png: 51275 bytes, checksum: 3fd73b126e99f2b7dd130af0bb44bdf2 (MD5) 5.png: 55362 bytes, checksum: 25c62c2e04a6487ff397321ace683cfe (MD5) 6.png: 30359 bytes, checksum: e5a89fc989ad68634201c273405d87cd (MD5) 1.ods: 14748 bytes, checksum: 5c53786fb4f59d40cfc67e265b3ccdbb (MD5) 2.ods: 12277 bytes, checksum: 85d3262eda8d0d19f2b9e68ca6a2ff60 (MD5) 3.ods: 29902 bytes, checksum: 21dce0898e77df8191be437bcf168491 (MD5) 4.ods: 26020 bytes, checksum: 75044d4b95e66473d1c38e29e2c1ddd9 (MD5) 5.ods: 25161 bytes, checksum: 64743c83195cdf34938b5e3142210535 (MD5) 6.ods: 23147 bytes, checksum: 67873780574e4a0c15048d1c18e8092c (MD5) 7.ods: 24872 bytes, checksum: 58b0b7758825e8bc80ec319f90cb30ed (MD5) 8.ods: 23642 bytes, checksum: 7e718def249e8b5c1ba5298d3e6101ae (MD5) 9.ods: 14540 bytes, checksum: b0af9d51d96c085aca53e416c8dc06e6 (MD5) 10.ods: 21679 bytes, checksum: eb531d5e51df06f11e0ae669a881e85f (MD5) 11.ods: 19560 bytes, checksum: 71de1352ca73f10c2cf6d738cd1cec4d (MD5) 12.ods: 14605 bytes, checksum: 31b8d0e606a2af909074980cd9a4a9c1 (MD5) 13.ods: 14233 bytes, checksum: a92806c87118d17b424acccb1f049816 (MD5) 14.ods: 17135 bytes, checksum: ba4d33d3045b7031dad15157a31d90be (MD5) 15.ods: 14245 bytes, checksum: 0a1b4b52bad09fc2dcf67639b1b6ba5b (MD5) 16.ods: 15790 bytes, checksum: 8cf6f938d822bb16cc84be8a422fc1c2 (MD5) 17.ods: 16843 bytes, checksum: c497070bd4d369d226a70c9e5d74c77e (MD5) 18.ods: 25388 bytes, checksum: b1871bedff625da6193de7545d19c4e7 (MD5) 19.ods: 67252 bytes, checksum: 8ebaf944dcae9d220b845680ca31188f (MD5) 20.ods: 27473 bytes, checksum: 923c1755f09c370ccb30729f2710f714 (MD5) 21.ods: 31513 bytes, checksum: 7d25175b6369b25e8b1dab068e610ba7 (MD5) 22.ods: 27301 bytes, checksum: 1064d84b82091b5f6d43cfc17b1d4636 (MD5) 23.ods: 38229 bytes, checksum: 290c7fe1ccbd28e18b5722899702bfed (MD5) 24.ods: 48098 bytes, checksum: 620ed74459343bc06f7eb6ed0d7679ec (MD5) 25.ods: 24148 bytes, checksum: 3cd42fc255ecea838588e3aae8dc19c4 (MD5) 26.ods: 26550 bytes, checksum: 4b6997336ee92c6def97e4909e858b7c (MD5) 27.ods: 27015 bytes, checksum: a20630e9c67be416d0e99f8fcbfe2384 (MD5) 28.ods: 20340 bytes, checksum: ce513515d2d38bb74a6234d7b748ab26 (MD5) 29.ods: 25812 bytes, checksum: 8f94b034213b8a281a25c1bc26e1e543 (MD5) / Rejected by LUIZA DE MENEZES ROMANETTO (luizamenezes@reitoria.unesp.br), reason: Solicitamos que realize uma nova submissão seguindo as orientações abaixo: Foram submetidos 79 arquivos, apenas 1 arquivo deve ser submetido em formato PDF. O arquivo PDF não deve estar protegido e a dissertação/tese deve estar em um único arquivo, inclusive os apêndices e anexos, se houver. Corrija estas informações e realize uma nova submissão contendo o arquivo correto. Agradecemos a compreensão. on 2017-03-13T17:21:20Z (GMT) / Submitted by Fernando de Assis Rodrigues (fernando@elleth.org) on 2017-03-14T01:09:45Z No. of bitstreams: 1 final.pdf: 41703816 bytes, checksum: f59b8e221e9bc15e9bc0f2579244c6c6 (MD5) / Approved for entry into archive by LUIZA DE MENEZES ROMANETTO (luizamenezes@reitoria.unesp.br) on 2017-03-17T19:30:40Z (GMT) No. of bitstreams: 1 rodrigues_fa_dr_mar.pdf: 41703816 bytes, checksum: f59b8e221e9bc15e9bc0f2579244c6c6 (MD5) / Made available in DSpace on 2017-03-17T19:30:40Z (GMT). No. of bitstreams: 1 rodrigues_fa_dr_mar.pdf: 41703816 bytes, checksum: f59b8e221e9bc15e9bc0f2579244c6c6 (MD5) Previous issue date: 2017-03-03 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES) / O desenvolvimento das redes sociais é tema de estudos de várias áreas do conhecimento, e com o aumento do uso da Internet em atividades profissionais e de entretenimento, surgiram as redes sociais online: serviços com o intuito de proporcionar uma interface de relacionamento entre indivíduos. Algumas destas redes possuem milhões de usuários, que consentiram acordo aos Termos de Uso. Os Termos de Uso destes serviços contém a delimitação dos processos de coleta de dados por agentes externos, criando um efeito em cascata de identificação do usuário, e pode potencializar atividades prejudiciais à privacidade. O estudo procura verificar se processos sistematizados de coleta de dados sobre documentos que contém características das interfaces de coleta das Application Programming Interfaces (APIs), e os Termos de Uso podem auxiliar a identificação de atividades potencialmente prejudiciais à privacidade dos usuários (referenciados) e revelar pré-requisitos de conhecimentos sobre as tecnologias envolvidas neste processo, conceitos prévios à identificação das características, e áreas profissionais envolvidas no entendimento das informações sobre tecnologias voltadas às APIs e condições dos Termos de Uso. O objetivo é propor um modelo de dados orientado a análise sobre questões de privacidade de dados pessoais, a partir da identificação das características da coleta de dados de referenciados via API, para auxiliar na identificação de potenciais ações e atividades prejudiciais à privacidade, realizadas na coleta de dados. O universo de pesquisa está delimitado aos serviços disponíveis na Internet que utilizam APIs como interfaces de interoperabilidade de seus conteúdos, e a amostra foi definida em três APIs: do Facebook, do Twitter e do LinkedIn. A metodologia adotada é a análise exploratória, de caráter qualitativo, com métodos combinados a partir da exploração das características técnicas das APIs e da leitura dos documentos disponíveis, sendo segmentada pelas perspectivas: Áreas Profissionais envolvidas, Tecnologias de Coleta e Pré-requisitos de Conhecimento. Para realização, propõe-se três ciclos: o primeiro, com a identificação das características das estruturas de coletas de dados e das funcionalidades apresentadas pelas APIs; o segundo ciclo propõe uma modelagem de dados, a partir da coleta das características das estruturas existentes (Modelagem Direta), e; o terceiro ciclo, uma Modelagem de Segunda Ordem, com informações específicas sobre a privacidade de dados de referenciados para a análise de aspectos de privacidade de dados compartilhados a terceiros. Ao final, apresenta uma lista de critérios para o acompanhamento e a avaliação das informações dos documentos de referência e Termos de Uso das redes sociais, como forma de identificar possíveis relações entre a ausência de dados. Nas considerações, sustentamos que este ambiente é complexo e ofuscado aos referenciados, porém o modelo de dados e os instrumentos elaborados podem auxiliar a minimizar a complexidade dos documentos de referência sobre a interoperabilidade de conjuntos de dados a agentes externos e no entendimento dos Termos de Uso. / The development of social networks is a topic of study for several areas, and with the increased use of the Internet in professional and leisure activities, online social networks have emerged: services with the goal of providing an interface between individuals. Some of these networks have millions of users, who agree and give their consente to the Terms of Use. The Terms of Use of these services contain the delimitation of the processes of data collection by external agents, creating a cascading effect of user identification and can enhance activities which are detrimental to user privacy. This study looks to verify if the systematic data collection processes for documents which contain characteristics of the Application Programming Interfaces (APIs) data collection and the Terms of Use can help in identifying activities potentially harmful to user privacy (referenced) and reveal prerequisites of knowledge about the technology involved in this process, concepts prior to identifying characteristics and professional areas involved in understanding the technology of the API and the Terms of Use. The objective is to propose an analysis based data model on personal privacy data issues, from the identification of the characteristics of the collection of data from the referenced API to assisting in identifying potential actions and activities which are detrimental to privacy obtained through the data collection process. The research universe is limited to the services available on the Internet that use APIs as interoperability interfaces of their content and the sample was defined in three APIs: from Facebook, Twitter and LinkedIn. The methodology adopted was exploratory analysis, in qualitative form, with combined methods based on the exploitation of the technical characteristics of APIs and the reading of available documents, being segmented by the perspectives: professional areas involved, collection technology and knowledge prerequisites. To conduct this study, three cycles are proposed: first, with the identification of the characteristics of the structure of data collection and the functionalities presented by the APIs; second, propose a model of the data from the collection of the characteristics of existing structures (Direct Model); and third, a model of Second Order, with specific information about referenced data privacy for the analysis of data privacy aspects to share with third parties. In the end, present a list of criteria for the monitoring and evaluation of the information of referenced documents and the Terms of Use of social networks, as a way of identifying possible relationships between the absence of data. In the considerations, we maintain the idea that this environment is complex and obfuscated to those referenced, but the data model and the instruments developed can help to minimize the complexity of referenced documents about the interoperability of datasets to external agents and understanding the Terms of Use. / El desarrollo de las redes sociales es tema de estudio de varias áreas del conocimiento, y con el aumento del uso de la Internet en actividades profesionales y de entretenimiento, surgieron las redes sociales en línea: servicios con el fin de proporcionar una interface de relacionamiento entre individuos. Algunas de estas redes poseen millones de usuarios, los cuales dieron su consentimiento al acuerdo de los Términos de Uso. Los Términos de estos servicios engloban la delimitación de los procesos de colecta de datos por agentes externos, creando un efecto en cascada de identificación del usuario, y puede potencializar actividades perjudiciales para la privacidad. El estudio pretende verificar si procesos sistematizados de colecta de datos sobre documentos que contienen características de las interfaces de colecta de las Application Programming Interfaces (APIs), y los Términos de Uso, pueden auxiliar en la identificación de actividades potencialmente perjudiciales para la privacidad de los usuarios (referenciados) y revelar prerrequisitos de conocimientos sobre las tecnologías involucradas en este proceso, conceptos previos a la identificación de las características, y áreas profesionales que participan en el entendimiento de las informaciones sobre tecnologías direccionadas a las APIs y condiciones de los Términos e Uso. El objetivo es proponer un modelo de datos orientado al análisis sobre cuestiones de privacidad de datos personales, a partir de la identificación de las características de la colecta de datos referenciados vía API, para auxiliar en la identificación de potenciales acciones y actividades perjudiciales para la privacidad, realizadas en la colecta de datos. El universo de pesquisa está delimitado a los servicios disponibles en la Internet que utilizan APIs como interfaces de interoperabilidad de sus contenidos, y la muestra fue definida en tres APIs: de Facebook, de Twitter y de LinkedIn. La metodología adoptada es un análisis exploratorio, de carácter cualitativo, con métodos combinados a partir de la exploración de las características técnicas de las APIs y de la lectura de los documentos disponibles, siendo segmentada por las perspectivas: Áreas Profesionales involucradas, Tecnologías de Colecta y Prerrequisitos de Conocimiento. Para la realización, se proponen tres ciclos: i. con la identificación de las características de las estructuras de colectas de datos y de las funcionalidades presentadas por las APIs; ii. ciclo, propone un modelaje de datos, a partir de la colecta de las características de las estructuras existentes (Modelaje Directo), y; iii. ciclo, un Modelaje de Segundo Orden, con informaciones específicas sobre la privacidad de los datos de referenciados para el análisis de aspectos de privacidad de datos compartidos con terceros. Finalmente, presenta una lista de criterios para el acompañamiento y la evaluación de las informaciones de los documentos de referencia y Términos de Uso de las redes sociales, como forma de identificar posibles relaciones entre la ausencia de datos. En las consideraciones, sustentamos que este ambiente es complejo y confuso para los referenciados, no obstante el modelo de datos y los instrumentos elaborados pueden contribuir a minimizar la complejidad de los documentos de referencia sobre la interoperabilidad de conjuntos de datos a agentes externos y en el entendimiento de los Términos de Uso.

<p>Providing carrier grade characteristics for Internet Protocol (IP) communication applications is a significant problem for IP application providers in order to offer integrated services that span IP&nbsp / and telecommunication networks. This thesis addresses the provision of life-cycle management, which is only one carrier grade characteristic, for a SoftBridge application, which is an example of IP communication applications. A SoftBridge provides semi-synchronous multi-modal IP-based communication. The work related to IP-Telecommunication integrated services and the SoftBridge is analyzed with respect to life-cycle management in a literature review. It is suggested to use an Application Server in a Next Generation Network (NGN) to provide life-cyclemanagement functionality for IP-Telecommunication applications. In this thesis, the Application Server is represented by a JAIN Service Logic Execution Environment(JSLEE), in which&nbsp / a SoftBridge application can be deployed, activated, deactivated, uninstalled and upgraded online.Two methodologies are applied in this research: exploratory prototyping, which evolves the development of a SoftBridge application, and empirical comparison, which is concerned with the empirical evaluation of a SoftBridge application in terms of carriergrade capabilities. A SoftBridge application called SIMBA&nbsp / provides a Deaf Telephony service similar to aprevious Deaf Telephony SoftBridge, However, SIMBA&rsquo / s SoftBridge design and implementation are unique to this thesis. In order to test the life-cycle&nbsp / management ability of SIMBA, an empirical evaluation is carried out including the experiments oflife-cycle management and call-processing performance. The final experimental results of the evaluation show that a JSLEE is able to provide life-cycle management for SIMBA without causing a significant decrease in performance. In conclusion, the life-cycle management can be provided&nbsp / or a SoftBridge application by using an Application Server such as a JSLEE. Futhermore, the results indicate that&nbsp / approach of using Application Server (JSLEE) integration should be&nbsp / sufficiently general to provide life cycle management, and indeed other carrier grade capabilities, for other IP communication applications. This allows IP communication applications to be&nbsp / &nbsp / &nbsp / integrated into an NGN.</p>

<p>Providing carrier grade characteristics for Internet Protocol (IP) communication applications is a significant problem for IP application providers in order to offer integrated services that span IP&nbsp / and telecommunication networks. This thesis addresses the provision of life-cycle management, which is only one carrier grade characteristic, for a SoftBridge application, which is an example of IP communication applications. A SoftBridge provides semi-synchronous multi-modal IP-based communication. The work related to IP-Telecommunication integrated services and the SoftBridge is analyzed with respect to life-cycle management in a literature review. It is suggested to use an Application Server in a Next Generation Network (NGN) to provide life-cyclemanagement functionality for IP-Telecommunication applications. In this thesis, the Application Server is represented by a JAIN Service Logic Execution Environment(JSLEE), in which&nbsp / a SoftBridge application can be deployed, activated, deactivated, uninstalled and upgraded online.Two methodologies are applied in this research: exploratory prototyping, which evolves the development of a SoftBridge application, and empirical comparison, which is concerned with the empirical evaluation of a SoftBridge application in terms of carriergrade capabilities. A SoftBridge application called SIMBA&nbsp / provides a Deaf Telephony service similar to aprevious Deaf Telephony SoftBridge, However, SIMBA&rsquo / s SoftBridge design and implementation are unique to this thesis. In order to test the life-cycle&nbsp / management ability of SIMBA, an empirical evaluation is carried out including the experiments oflife-cycle management and call-processing performance. The final experimental results of the evaluation show that a JSLEE is able to provide life-cycle management for SIMBA without causing a significant decrease in performance. In conclusion, the life-cycle management can be provided&nbsp / or a SoftBridge application by using an Application Server such as a JSLEE. Futhermore, the results indicate that&nbsp / approach of using Application Server (JSLEE) integration should be&nbsp / sufficiently general to provide life cycle management, and indeed other carrier grade capabilities, for other IP communication applications. This allows IP communication applications to be&nbsp / &nbsp / &nbsp / integrated into an NGN.</p>

Software components expose Application Programming Interfaces (APIs) as a means to access their functionality, and facilitate reuse. Developers use APIs supplied by programming languages to access the core data structures and algorithms that are part of the language framework. They use the APIs of third-party libraries for specialized tasks. Thus, APIs play a central role in mediating a developer's interaction with software, and the interaction between different software components. However, APIs are often large, complex and hard to navigate. They may have hundreds of classes and methods, with incomplete or obsolete documentation. They may encapsulate concurrency behaviour that the developer is unaware of. Finding the right functionality in a large API, using APIs correctly, and maintaining software that uses a constantly evolving API are challenges that every developer runs into. In this thesis, we design automated techniques to address two problems pertaining to APIs (1) Concurrency analysis of APIs, and (2) API mining. Speci cally, we consider the concurrency analysis of asynchronous APIs, and mining of math APIs to infer the functional behaviour of API methods. The problem of concurrency bugs such as race conditions and deadlocks has been well studied for multi-threaded programs. However, developers have been eschewing a pure multi-threaded programming model in favour of asynchronous programming models supported by asynchronous APIs. Asynchronous programs and multi-threaded programs have different semantics, due to which existing techniques to analyze the latter cannot detect bugs present in programs that use asynchronous APIs. This thesis addresses the problem of concurrency analysis of programs that use asynchronous APIs in an end-to-end fashion. We give operational semantics for important classes of asynchronous and event-driven systems. The semantics are designed by carefully studying real software and serve to clarify subtleties in scheduling. We use the semantics to inform the design of novel algorithms to find races and deadlocks. We implement the algorithms in tools, and show their effectiveness by finding serious bugs in popular open-source software. To begin with, we consider APIs for asynchronous event-driven systems supporting pro-grammatic event loops. Here, event handlers can spin event loops programmatically in addition to the runtime's default event loop. This concurrency idiom is supported by important classes of APIs including GUI, web browser, and OS APIs. Programs that use these APIs are prone to interference between a handler that is spinning an event loop and another handler that runs inside the loop. We present the first happens-before based race detection technique for such programs. Next, we consider the asynchronous programming model of modern languages like C]. In spite of providing primitives for the disciplined use of asynchrony, C] programs can deadlock because of incorrect use of blocking APIs along with non-blocking (asynchronous) APIs. We present the rst deadlock detection technique for asynchronous C] programs. We formulate necessary conditions for deadlock using a novel program representation that represents procedures and continuations, control ow between them and the threads on which they may be scheduled. We design a static analysis to construct the pro-gram representation and use it to identify deadlocks. Our ideas have resulted in research tools with practical impact. Sparse Racer, our tool to detect races, found 13 previously unknown use-after-free bugs in KDE Linux applications. Dead Wait, our deadlock detector, found 43 previously unknown deadlocks in asynchronous C] libraries. Developers have fixed 43 of these races and deadlocks, indicating that our techniques are useful in practice to detect bugs that developers consider worth fixing. Using large APIs effectively entails finding the right functionality and calling the methods that implement it correctly, possibly composing many API elements. Automatically infer-ring the information required to do this is a challenge that has attracted the attention of the research community. In response, the community has introduced many techniques to mine APIs and produce information ranging from usage examples and patterns, to protocols governing the API method calling sequences. We show how to mine unit tests to match API methods to their functional behaviour, for the specific but important class of math APIs. Math APIs are at the heart of many application domains ranging from machine learning to scientific computations, and are supplied by many competing libraries. In contrast to obtaining usage examples or identifying correct call sequences, the challenge in this domain is to infer API methods required to perform a particular mathematical computation, and to compose them correctly. We let developers specify mathematical computations naturally, as a math expression in the notation of interpreted languages (such as Matlab). Our unit test mining technique maps subexpressions to math API methods such that the method's functional behaviour matches the subexpression's executable semantics, as defined by the interpreter. We apply our technique, called MathFinder, to math API discovery and migration, and validate it in a user study. Developers who used MathFinder nished their programming tasks twice as fast as their counterparts who used the usual techniques like web and code search, and IDE code completion. We also demonstrate the use of MathFinder to assist in the migration of Weka, a popular machine learning library, to a different linear algebra library.

Magister Scientiae - MSc / Providing carrier grade characteristics for Internet Protocol (IP) communication applications is a significant problem for IP application providers in order to offer integrated services that span IP and telecommunication networks. This thesis addresses the provision of life-cycle management, which is only one carrier grade characteristic, for a SoftBridge application, which is an example of IP communication applications. A SoftBridge provides semi-synchronous multi-modal IP-based communication. The work related to IP-Telecommunication integrated services and the SoftBridge is analyzed with respect to life-cycle management in a literature review. It is suggested to use an Application Server in a Next Generation Network (NGN) to provide life-cyclemanagement functionality for IP-Telecommunication applications. In this thesis, the Application Server is represented by a JAIN Service Logic Execution Environment(JSLEE), in which a SoftBridge application can be deployed, activated, deactivated, uninstalled and upgraded online.Two methodologies are applied in this research: exploratory prototyping, which evolves the development of a SoftBridge application, and empirical comparison, which is concerned with the empirical evaluation of a SoftBridge application in terms of carriergrade capabilities. A SoftBridge application called SIMBA provides a Deaf Telephony service similar to aprevious Deaf Telephony SoftBridge, However, SIMBA’s SoftBridge design and implementation are unique to this thesis. In order to test the life-cycle management ability of SIMBA, an empirical evaluation is carried out including the experiments oflife-cycle management and call-processing performance. The final experimental results of the evaluation show that a JSLEE is able to provide life-cycle management for SIMBA without causing a significant decrease in performance. In conclusion, the life-cycle management can be provided or a SoftBridge application by using an Application Server such as a JSLEE. Futhermore, the results indicate that approach of using Application Server (JSLEE) integration should be sufficiently general to provide life cycle management, and indeed other carrier grade capabilities, for other IP communication applications. This allows IP communication applications to be integrated into an NGN.Providing carrier grade characteristics for Internet Protocol (IP) communication applications is a significant problem for IP application providers in order to offer integrated services that span IP and telecommunication networks. This thesis addresses the provision of life-cycle management, which is only one carrier grade characteristic, for a SoftBridge application, which is an example of IP communication applications. A SoftBridge provides semi-synchronous multi-modal IP-based communication. The work related to IP-Telecommunication integrated services and the SoftBridge is analyzed with respect to life-cycle management in a literature review. It is suggested to use an Application Server in a Next Generation Network (NGN) to provide life-cyclemanagement functionality for IP-Telecommunication applications. In this thesis, the Application Server is represented by a JAIN Service Logic Execution Environment(JSLEE), in which a SoftBridge application can be deployed, activated, deactivated, uninstalled and upgraded online.Two methodologies are applied in this research: exploratory prototyping, which evolves the development of a SoftBridge application, and empirical comparison, which is concerned with the empirical evaluation of a SoftBridge application in terms of carriergrade capabilities. A SoftBridge application called SIMBA provides a Deaf Telephony service similar to aprevious Deaf Telephony SoftBridge, However, SIMBA’s SoftBridge design and implementation are unique to this thesis. In order to test the life-cycle management ability of SIMBA, an empirical evaluation is carried out including the experiments oflife-cycle management and call-processing performance. The final experimental results of the evaluation show that a JSLEE is able to provide life-cycle management for SIMBA without causing a significant decrease in performance. In conclusion, the life-cycle management can be provided or a SoftBridge application by using an Application Server such as a JSLEE. Futhermore, the results indicate that approach of using Application Server (JSLEE) integration should be sufficiently general to provide life cycle management, and indeed other carrier grade capabilities, for other IP communication applications. This allows IP communication applications to be integrated into an NGN. / South Africa

Made available in DSpace on 2015-05-14T12:36:47Z (GMT). No. of bitstreams: 1 arquivototal.pdf: 8775685 bytes, checksum: 7021be54b3d48e2a9247804ad1a980ab (MD5) Previous issue date: 2018-08-08 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior - CAPES / The Interactive Digital TV applications progress does not occur at the same speed we found at Web or Desktop applications. This fact is due to constraints encountered in both hardware and the middleware in which applications run, and also due to the limited way we have to interact with the TV: with the traditional remote control. In the Brazilian scene, the middleware Ginga specification allows the incorporation of new functionalities through the Device Integration API, which is target of this dissertation. The API allows TVDI applications to use mobile devices both as a means of interaction, and to share its multimedia resources. As a result of the API use, TVDI applications are able to employ new possibilities not available in others existing Digital TV middlewares, like the use of multimedia resources and multiuser support. The new API has been implemented and applied to develop TVDI applications aiming to explore the new advanced features available. / avanço das aplicações de TV Digital Interativa não ocorre na mesma velocidade que as aplicações para WEB ou Desktop. Tal fato se deve tanto por limitações encontradas no hardware e no middleware no qual as aplicações são executadas, quanto pela limitação do dispositivo usado na interação dos usuários com a TV. No panorama nacional, a especificação do middleware Ginga permite a incorporação de novas funcionalidades através da API de Integração de Dispositivos, alvo desse trabalho. Esta API que permite que aplicações de TVDI usem dispositivos móveis tanto como meio de interação, como para compartilhamento de seus recursos multimídia. Como resultado do uso da API proposta, as aplicações de TVDI passam a contar com novas possibilidades até então não disponíveis nos middlewares de TV Digital existentes; como a utilização de mais de um dispositivo simultaneamente, o suporte ao desenvolvimento de aplicações multiusuário e o acesso a recursos de captura de mídias contínuas disponíveis em aparelhos como celulares, que podem ser integrados aos aparelhos de TV. A API resultante desse trabalho foi implementada e utilizada no desenvolvimento de aplicações para TVDI voltadas a explorar os novos recursos avançados disponíveis.

Neste trabalho serão discutidas novas ferramentas para a construção de um espectrômetro de Ressonância Magnética (RM) totalmente digital. A motivação parte das dificuldades encontradas pelos pesquisadores no momento de programar um equipamento de RM, incluindo a falta de ferramentas para desenvolvimento de metodologias, as quais não são oferecidas pelos softwares atuais. Em particular tratamos do desenvolvimento de uma biblioteca, a PyMR (Python Magnetic Resonance), de uma API (Application Program Interface) e de um IDE (Integrated Development Environment). Nesta estrutura, a biblioteca PyMR é o front-end para programação e setup dos equipamentos de RM enquanto a API constitui o back-end. O IDE, por sua vez, é uma ferramenta de auxílio especializado para criação e gerenciamento das metodologias e protocolos de RM de forma funcional e amigável. O desenvolvimento baseado no estado-da-arte das tecnologias de Computação e Ressonância Magnética garante a qualidade, robustez, adaptabilidade e ainda assim, a simplicidade para uso dos menos experientes. Para a validação do sistema, além de métricas de software, foi montada uma sequência de pulsos conhecida como CPMG (Carr-Purcell-Meiboom-Gill) executada no espectrômetro local sobre uma amostra de CuSO4 em solução, o qual mostrou valores de T2 compatíveis com os valores esperados. Os resultados do novo sistema mostram sua capacidade de atender as principais exigências dos usuários e desenvolvedores de metodologias de RM, oferecendo um amplo conjunto de ferramentas. Em suma, este projeto provê a estrutura básica e funcional de uma nova forma de se programar e utilizar equipamentos de RM, gerando um poderoso instrumento para a pesquisa na área. / In this study we discuss new tools for the building of a fully digital Magnetic Resonance (MR) spectrometer. The research was motivated by several difficulties experienced by researchers in programming MR machines, which include the lack of tools for the development of methodologies that are not currently offered by companies. In particular, we treat the development of a library, PyMR (Python Magnetic Resonance), an API (Application Program Interface) and an IDE (Integrated Development Environment). In this structure, the PyMR library acts as a front-end for MR equipment programming and setup while the API is a back-end. Finally, the IDE is a user-friendly tool that helps the developer to create and manage methodologies and protocols. The state-of-the-art of Computer Sciences and Magnetic Resonance technologies adopted here has ensured the quality, robustness and adaptability keeping simplicity for non-experienced users. For the validation of the system, besides software metrics, a pulse sequence known as CPMG (Carr-Purcell-Meiboom-Gill) was assembled and performed on an onsite spectrometer, using a solution of CuSO4 as a sample, which exhibited compatible T2 values. The results show that the system can meet the main requirements of both users and developers and offer a large set of tools. This project provides a basic and functional structure of a new way to program and use the MR equipment and a powerful tool for researchers in this area.

This Master’s Thesis in Electrical Engineering concerns the introduction of a Parlay gateway in Skanova’s public circuit switched telephone network, what network integrity problems this brings, and how to preserve the integrity of the network. There is a rising demand from the market on Skanova to be able to offer integrated and useful services via their network. Examples of such services are Web Controlled Call Forwarding and Virtual Call Centres. Until now, these services have been implemented with the Intelligent Network concept which is a technology for concentrating the service logic in the telephone network to centralised service platforms within the network operator’s domain. Developing new services in this environment is expensive and therefore, Skanova wants to open the network for third party service providers. The opening of the network is enabled by the introduction of a gateway implementing the open service interface Parlay. The crucial point when opening the network for third party service providers is to maintain the integrity of the network. Parlay is an object oriented Application Programming Interface that enables a third party service access to core network resources in a controlled manner. The authors’ definition of network integrity is: “the ability of a network to steadily remain in a safe state, while performing according to the expectations and specifications of its owner, i.e. delivering the expected functionality and providing means to charge for utilised network resources”. The thesis describes a few services implemented via the Parlay interface and points out examples of activities in these services that may jeopardise the integrity of the network. The described activities belong to one of the two categories: Call Control Functionality or Lack of Charging Instruments. The thesis also describes two important methods for addressing encountered integrity problems. The methods are: Parlay Service Level Agreement and Policy Management.&lt;/p&gt; Finally, the solutions are compared and the conclusion is that Policy Management is a conformable and flexible method for addressing lots of integrity problems and that these are important qualities, since new integrity problems will arise all the time.

This paper aimed to discover how player satisfaction is affected by context-aware elements based on physical, real-world factors in an action role-playing game. The possibility of utilizing player modelling to counteract the reduction in player empowerment in a game heavily influenced by external factors was also explored. This was accomplished by creating an ARPG heavily integrated with various weather, and daytime, context data obtained from web-based APIs. Followed by conducting qualitative tests with help of eleven participants during a time period of a week. The evaluated results were presented in a manner of relevance for both context-driven applications as a whole, and for further exploration within game developments utilization of state of the art technology.