Dissertations / Theses on the topic 'Documentation des API'

Reference documentation is an important source of information on API usage. Programmers, however, can easily overlook reference information because of its tedious nature, and because the information they seek can be buried among irrelevant or boiler-plate text. We propose to detect and recommend fragments of API documentation relevant and important to a task. We categorize pieces of information in API documentation based on the type of knowledge they contain. From the pieces that contain knowledge worthy of recommendation, we extract the composition and the pattern of words, and use the patterns to automatically find new pieces that contain similar knowledge. In an evaluation study, with a training set of manually-classified reference documentation of about 1 000 API elements, we could issue recommendations with about, on average, 90% precision and 69% recall.
La documentation de référence est une source importante d'information sur l'usage d'une API. Cependant, les programmeurs peuvent négliger cette information que l'information recherchée se trouve enfouie au milieu de texte passe-partout et sans pertinence. Nous proposons de détecter et recommender les fragments de documentation d'API pertinents à une tâche donnée de façon automatique. Nous catégorisons les morceaux d'information dans la documentation d'API en fonction du type de savoir qu'ils renferment. À partir des morceaux de savoir digne de recommendation, nous extrayons des patrons de mots, puis utilisons ces patrons pour trouver automatiquement de nouveaux morceaux qui renferment un savoir similaire. Nous présentons les résultats d'une évaluation expérimentale de notre système effectuée à partir de plus de 1 000 morceaux d'API, où nous trouvons que notre système offre de recommendations adéquates 90% du temps avec un taux de rappel de 69%.

Lors du développement de logiciels, la maintenance et l'évolution constituent une partie importante du cycle de vie du développement représentant 80% du coût et des efforts globaux.Au cours de la maintenance, il arrive que les développeurs aient copier-coller des fragments de code source afin de les réutiliser. Une telle pratique, apparemment inoffensive, est plus fréquente qu'on ne le pense.Communément appelés «clones» dans la littérature, ces doublons de code source sont un sujet bien connu et étudié en génie logiciel.Dans cette thèse, nous visons à mettre en lumière les pratiques du copier-coller sur les artefacts logiciels.En particulier, nous avons choisi de concentrer nos contributions sur deux types d'artefacts logiciels : Documentation d'API et fichiers de compilation (c.-à-d. Dockerfiles). Pour les deux contributions, nous suivons une méthodologie d'étude empirique commune.Tout d'abord, nous montrons que les documentations d'API et les fichiers de construction de logiciels (c.-à-d. Dockerfiles) sont confrontés à des problèmes de doublons et que de tels doublons sont fréquents.Deuxièmement, nous identifions les raisons derrière l'existence de ces doublons.Troisièmement, nous effectuons une enquête auprès de développeurs expérimentés et de constatons qu'ils sont conscients de ces doublons, et qu'ils les rencontrent souvent tout en ayant un avis mitigé sur eux.Enfin, nous montrons que les deux artefacts logiciels manquent de mécanismes de réutilisation pour faire face aux doublons, et que certains développeurs ont même recours à des outils ad-hoc pour les gérer
When developing a software, maintenance and evolution represents an important part of the development's life-cycle, making up to 80% of the overall cost and effort.During the maintenance effort, it happens that developers have to resort to copying and pasting source code fragments in order to reuse them.Such practice, seemingly harmless is more frequent than we expect.Commonly referred to as ``clones'' in the literature, these source code duplicates are a well-known and studied topic in software engineering.In this thesis, we aim at shedding some light on copy-paste practices on software artifacts. In particular, we chose to focus our contributions on two specific types of software artifacts: API documentation and build files (i.e. Dockerfiles).For both contributions, we follow a common empirical study methodology. First, We show that API documentations and software build files (i.e. Dockerfiles) actually face duplicates issues and that such duplicates are frequent.Secondly, we identify the reasons behind the existence of such duplicates.Thirdly, We perform a survey on experimented developers and find that they're aware of such duplicates, frequently face them. But still have a mixed opinion regarding them.Finally, We show that both software artifacts lack reuse mechanisms to cope with duplicates, and that some developers even resort to ad-hoc tools to manage them

Submitted by Claudinei Pracidelli (cpracide@ipen.br) on 2015-07-23T10:56:10Z No. of bitstreams: 0
Made available in DSpace on 2015-07-23T10:56:10Z (GMT). No. of bitstreams: 0
Dissertação (Mestrado em Tecnologia Nuclear)
IPEN/D
Instituto de Pesquisas Energeticas e Nucleares - IPEN-CNEN/SP

The aim of this thesis is to provide an insight into theoretical and practical aspects of an analytical tool developed by Ondřej Funiok, Vilém Kalus, Tomáš Rosenberger and Martin Matějka at the University of Economics in Prague. The goal was to develop a tool which could be used for an analysis of human movement within a given place (e.g. retail store) and which could leverage traditional customers' data like age, gender or profession in order to enrich outcomes of conducted analysis, as well as provide a new segmentation of these customers based on their movement. Given that, one of the possible scenarios is that marketers would be able to finely-target their campaigns and use the space more effectively. The thesis contains a short introduction to Location Intelligence as a category of systems which the developed tool belongs to. Further a research of existing theses, articles etc., as well as already available products is conducted. Since a documentation of web services' application interface has proved to be an important aspect of the development, a research and comparison of supporting tools follows. Fourth and fifth chapters are of rather practical nature -- the first of them is about an overall design and architecture of the developed tool, while the second one describes the used application interface and its documentation in detail together with the most important aspects of a backend component -- so called ,,GA-Server``.

Para a certificação de um procedimento de soldagem, quer seja de alta responsabilidade na soldagem de oleodutos e gasodutos em tubulações de aço carbono ou para um uso rotineiro e diário em fábricas e oficinas, deve ser realizada uma análise profunda dos fenômenos ocorridos no material de base (MB), no metal de adição (MA) e na zona afetada pelo calor (ZAC). Por meio desta análise criteriosa na qualificação de um procedimento de soldagem, o procedimento é liberado para ser utilizado, seja qual for o objetivo final da soldagem. Apenas com a Especificação do Procedimento de Soldagem (EPS) qualificada em mãos é possível iniciar os trabalhos de soldagem, e caso esta seja seguida integralmente, o sucesso do processo está a um passo de se concretizar. Para demonstração desta interação existente entre qualificação, análise dos resultados, aprovação dos ensaios e aprovação da especificação, foi desenvolvido este trabalho utilizando o material de base na forma tubular API 5L Gr. B soldado com os processos eletrodo revestido (SMAW) e arame tubular autoprotegido (FCAW-S). Foi utilizada uma junta tubular como exemplo de estudo e qualificação de um procedimento de soldagem baseado na documentação contida na norma da Petrobrás N-2301 e em outros códigos e normas, que regem a qualificação do processo de soldagem utilizado em refinarias e plantas de produção brasileiras. Foram estudados em conjunto os resultados obtidos por meio de ensaios mecânicos, ensaios não destrutivos e microestruturais. Ambas as Especificações dos Procedimentos de Soldagem preliminares (pEPS), estabelecidas antes do início da soldagem dos dois processos de soldagem, foram aprovadas e qualificadas, satisfazendo as características macro e microscópicas, metalúrgicas e mecânicas da junta soldada.
A comprehensive analysis of the phenomena occurring in the base metal (MB), filler metal (FM) and the heat affected zone (HAZ) should be conducted to provide the qualification of the welding procedure, either in high-demand carbon steel oil & gas pipelines or standard factory & workshop daily, usual operation. By means of this thorough welding procedure qualification, the process will be released, whatever the ultimate goal of welding. Only after the welding procedure specification (WPS) is qualified, is possible to start any welding work, and being the norm fully observed, the process is nearly to start successfully. The present work has been elaborated to demonstrate the interaction of qualification, result analysis, tests and specification approval, by applying the following elements: tubular base metal API 5L grade B welded with Shielded Metal Arc Welding process (SMAW) and self-shielded Flux Cored Arc Welding process (FCAW-S). A tubular joint was used as sample for a welding procedure qualification studies based on technical documentation specified on Petrobras N-2301, a Brazilian standard, and any others codes and standards that rule welding qualification on refineries & production plants of this company. The results obtained through mechanical testing, non-destructive testing and microstructure were studied together. Both preliminary welding procedure specifications (pWPS) established before the welding of these two welding processes, have been approved and qualified. The support given by welding qualification record (WQR) allows the joints to be welded in production, and result in reliable weld bead that satisfy the macro & microscopic, metallurgical and mechanical characteristics.

The thesis deals with OpenCV library and its implementation into scripting language Lua. The first part of the thesis concentrates on description of the course Computer vision MPOV and description of mathematical basics needed for further understandings. The second part describes OpenCV library and its potential usage in the MPOV. Next chapter examines the programming scripting language Lua. The description of the implementation of binding the OpenCV library to Lua language along with its overall functionality is included in the practical part of the thesis. The use of LuaCV is more comfortable thanks to Open Source projects for cross-platform compilation and distribution. Part of the thesis is also generator of Latex documentation for LuaCV binding. The last chapter deals with testing LuaCV in course MPOV and analysis of criticism from students.

Thesis (M.S.)--University of Wisconsin--Madison, 1995.
Typescript. eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references (leaves 89-91).

Thesis (M.S.)--University of Wisconsin--Madison, 2000.
Typescript. eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references (leaves 74-76).

Thesis (M.S.)--University of Wisconsin--Madison, 1986.
Typescript. eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references (leaves 122-130).

Thesis (M.S.)--University of Wisconsin--Madison, 1986.
Typescript. eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references (leaves 72-78).

Les systèmes logiciels dépendent de plus en plus des librairies et des frameworks logiciels. Les programmeurs réutilisent les fonctionnalités offertes par ces librairies à travers une interface de programmation (API). Par conséquent, ils doivent faire face à la complexité des APIs nécessaires pour accomplir leurs tâches, tout en surmontant l’absence de directive sur l’utilisation de ces API dans leur documentation. Dans cette thèse, nous proposons une approche holistique qui cible le problème de réutilisation des librairies, à trois niveaux. En premier lieu, nous nous sommes intéressés à la réutilisation d’une seule méthode d’une API. À ce niveau, nous proposons d’identifier les contraintes d’utilisation liées aux paramètres de la méthode, en analysant uniquement le code source de la librairie. Nous avons appliqué plusieurs analyses de programme pour détecter quatre types de contraintes d’utilisation considérées critiques. Dans un deuxième temps, nous changeons l’échelle pour nous focaliser sur l’inférence des patrons d’utilisation d’une API. Ces patrons sont utiles pour aider les développeurs à apprendre les façons courantes d’utiliser des méthodes complémentaires de l’API. Nous proposons d’abord une technique basée sur l’analyse des programmes clients de l’API. Cette technique permet l’inférence de patrons multi-niveaux. Ces derniers présentent des relations de co-utilisation entre les méthodes de l’API à travers des scénarios d’utilisation entremêlés. Ensuite, nous proposons une technique basée uniquement sur l’analyse du code de la librairie, pour surmonter la contrainte de l’existence des programmes clients de l‘API. Cette technique infère les patrons par analyse des relations structurelles et sémantiques entre les méthodes. Finalement, nous proposons une technique coopérative pour l’inférence des patrons d’utilisation. Cette technique est axée sur la combinaison des heuristiques basées respectivement sur les clients et sur le code de la librairie. Cette combinaison permet de profiter à la fois de la précision des techniques basées sur les clients et de la généralisabilité des techniques basées sur les librairies. Pour la dernière contribution de notre thèse, nous visons un plus haut niveau de réutilisation des librairies. Nous présentons une nouvelle approche, pour identifier automatiquement les patrons d’utilisation de plusieurs librairies, couramment utilisées ensemble, et généralement développées par différentes tierces parties. Ces patrons permettent de découvrir les possibilités de réutilisation de plusieurs librairies pour réaliser diverses fonctionnalités du projets.
Software systems increasingly depend on external library and frameworks. Software developers need to reuse functionalities provided by these libraries through their Application Programming Interfaces (APIs). Hence, software developers have to cope with the complexity of existing APIs needed to accomplish their work, and overcome the lack of usage directive in the API documentation. In this thesis, we propose a holistic approach that deals with the library usability problem at three levels of granularity. In the first step, we focus on the method level. We propose to identify usage constraints related to method parameters, by analyzing only the library source code. We applied program analysis strategies to detect four critical usage constraint types. At the second step, we change the scale to focus on API usage pattern mining in order to help developers to better learn common ways to use the API complementary methods. We first propose a client-based technique for mining multilevel API usage patterns to exhibit the co-usage relationships between API methods across interfering usage scenarios. Then, we proposed a library-based technique to overcome the strong constraint of client programs’ selection. Our technique infers API usage patterns through the analysis of structural and semantic relationships between API methods. Finally, we proposed a cooperative usage pattern mining technique that combines client-based and library-based usage pattern mining. Our technique takes advantage at the same time from the precision of the client-based technique and from the generalizability of the library-based technique. As a last contribution of this thesis, we target a higher level of library usability. We present a novel approach, to automatically identify third-party library usage patterns, of libraries that are commonly used together. This aims to help developers to discover reuse opportunities, and pick complementary libraries that may be relevant for their projects.

Thesis (M.S.)--University of Wisconsin--Madison, 1995.
Typescript. eContent provider-neutral record in process. Description based on print version record. Includes bibliographical references (leaves 185-195).