Relevant bibliographies by topics / Documentation des API

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Documentation des API'

Author: Grafiati
Published: 4 June 2021
Last updated: 2 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Documentation des API.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Documentation des API"

1

Zhong, Hao, and Zhendong Su. "Detecting API documentation errors." ACM SIGPLAN Notices 48, no. 10 (November 12, 2013): 803–16. http://dx.doi.org/10.1145/2544173.2509523.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Uddin, Gias, and Martin P. Robillard. "How API Documentation Fails." IEEE Software 32, no. 4 (July 2015): 68–75. http://dx.doi.org/10.1109/ms.2014.80.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Robillard, Martin P., and Yam B. Chhetri. "Recommending reference API documentation." Empirical Software Engineering 20, no. 6 (July 15, 2014): 1558–86. http://dx.doi.org/10.1007/s10664-014-9323-y.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Hoffman, Daniel, and Paul Strooper. "API documentation with executable examples." Journal of Systems and Software 66, no. 2 (May 2003): 143–56. http://dx.doi.org/10.1016/s0164-1212(02)00055-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Meng, Michael, Stephanie Steinhardt, and Andreas Schubert. "How developers use API documentation." Communication Design Quarterly 7, no. 2 (August 26, 2019): 40–49. http://dx.doi.org/10.1145/3358931.3358937.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Pandita, Rahul, Raoul Jetley, Sithu Sudarsan, Timothy Menzies, and Laurie Williams. "TMAP: Discovering relevant API methods through text mining of API documentation." Journal of Software: Evolution and Process 29, no. 12 (February 20, 2017): e1845. http://dx.doi.org/10.1002/smr.1845.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Uddin, Gias, Foutse Khomh, and Chanchal K. Roy. "Automatic API Usage Scenario Documentation from Technical Q&A Sites." ACM Transactions on Software Engineering and Methodology 30, no. 3 (May 2021): 1–45. http://dx.doi.org/10.1145/3439769.

Full text
Abstract:
The online technical Q&A site Stack Overflow (SO) is popular among developers to support their coding and diverse development needs. To address shortcomings in API official documentation resources, several research works have thus focused on augmenting official API documentation with insights (e.g., code examples) from SO. The techniques propose to add code examples/insights about APIs into its official documentation. Recently, surveys of software developers find that developers in SO consider the combination of code examples and reviews about APIs as a form of API documentation, and that they consider such a combination to be more useful than official API documentation when the official resources can be incomplete, ambiguous, incorrect, and outdated. Reviews are opinionated sentences with positive/negative sentiments. However, we are aware of no previous research that attempts to automatically produce API documentation from SO by considering both API code examples and reviews. In this article, we present two novel algorithms that can be used to automatically produce API documentation from SO by combining code examples and reviews towards those examples. The first algorithm is called statistical documentation, which shows the distribution of positivity and negativity around the code examples of an API using different metrics (e.g., star ratings). The second algorithm is called concept-based documentation, which clusters similar and conceptually relevant usage scenarios. An API usage scenario contains a code example, a textual description of the underlying task addressed by the code example, and the reviews (i.e., opinions with positive and negative sentiments) from other developers towards the code example. We deployed the algorithms in Opiner, a web-based platform to aggregate information about APIs from online forums. We evaluated the algorithms by mining all Java JSON-based posts in SO and by conducting three user studies based on produced documentation from the posts. The first study is a survey, where we asked the participants to compare our proposed algorithms against a Javadoc-syle documentation format (called as Type-based documentation in Opiner). The participants were asked to compare along four development scenarios (e.g., selection, documentation). The participants preferred our proposed two algorithms over type-based documentation. In our second user study, we asked the participants to complete four coding tasks using Opiner and the API official and informal documentation resources. The participants were more effective and accurate while using Opiner. In a subsequent survey, more than 80% of participants asked the Opiner documentation platform to be integrated into the formal API documentation to complement and improve the API official documentation.
APA, Harvard, Vancouver, ISO, and other styles
8

Meng, Michael, Stephanie Steinhardt, and Andreas Schubert. "Application Programming Interface Documentation: What Do Software Developers Want?" Journal of Technical Writing and Communication 48, no. 3 (July 26, 2017): 295–330. http://dx.doi.org/10.1177/0047281617721853.

Full text
Abstract:
The success of an application programming interface (API) crucially depends on how well its documentation meets the information needs of software developers. Previous research suggests that these information needs have not been sufficiently understood. This article presents the results of a series of semistructured interviews and a follow-up questionnaire conducted to explore the learning goals and learning strategies of software developers, the information resources they turn to and the quality criteria they apply to API documentation. Our results show that developers initially try to form a global understanding regarding the overall purpose and main features of an API, but then adopt either a concepts-oriented or a code-oriented learning strategy that API documentation both needs to address. Our results also show that general quality criteria such as completeness and clarity are relevant to API documentation as well. Developing and maintaining API documentation therefore need to involve the expertise of communication professionals.
APA, Harvard, Vancouver, ISO, and other styles
9

Maalej, Walid, and Martin P. Robillard. "Patterns of Knowledge in API Reference Documentation." IEEE Transactions on Software Engineering 39, no. 9 (September 2013): 1264–82. http://dx.doi.org/10.1109/tse.2013.12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Rantanen, Petri. "REST API example generation using Javadoc." Computer Science and Information Systems 14, no. 2 (2017): 447–66. http://dx.doi.org/10.2298/csis161022009r.

Full text
Abstract:
Formatting and editing documentation can be a tedious process regardless of how well your documentation templates are made. Especially, keeping the code examples up-to-date can be time-consuming and error-prone. The research presented in this article describes a Javadoc extension that can be used to produce example data in combination with automatically generated API method call examples, and explains how the APIs in our implementation are organized to further ease the automatic documentation process. The primary goal is to make generating method call examples for (RESTful) web services easier. The method has been used in the implementation of a media content analysis service, and the experiences, advantages of using the described approach are discussed in this article. The method allows easier validation and maintenance for the documentation of method usage examples with a downside of an increased workload in the implementation of software components required for the automatic documentation process.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Documentation des API"

1

Chhetri, Yam. "Classifying and recommending knowledge in reference documentation to improve API usability." Thesis, McGill University, 2013. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=114542.

Full text
Abstract:
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%.
APA, Harvard, Vancouver, ISO, and other styles
2

Oumaziz, Mohamed Ameziane. "Cloning beyond source code : a study of the practices in API documentation and infrastructure as code." Thesis, Bordeaux, 2020. http://www.theses.fr/2020BORD0007.

Full text
Abstract:
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
APA, Harvard, Vancouver, ISO, and other styles
3

SGOBBI, ALEXANDRE A. "Caracterização mecanica e microestrutural de juntas tubulares soldadas em aço API 5L grau B com base na norma Petrobras N-2301." reponame:Repositório Institucional do IPEN, 2015. http://repositorio.ipen.br:8080/xmlui/handle/123456789/23823.

Full text
Abstract:
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
APA, Harvard, Vancouver, ISO, and other styles
4

Matějka, Martin. "Implementace nástroje pro analýzu dat o pohybu osob." Master's thesis, Vysoká škola ekonomická v Praze, 2014. http://www.nusl.cz/ntk/nusl-192369.

Full text
Abstract:
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``.
APA, Harvard, Vancouver, ISO, and other styles
5

De, Cuyper Sheila. "Applying a participatory action research approach to the production of visual documentation a case study at the Leuwigadjah dumpsite, Bandung, Indonesia /." Toronto : University Consortium on the Environment, 1992. http://catalog.hathitrust.org/api/volumes/oclc/35875752.html.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Sgobbi, Alexandre Amaral. "Caracterização mecânica e microestrutural de juntas tubulares soldadas em aço API 5L Grau B com base na norma Petrobrás N-2301." Universidade de São Paulo, 2015. http://www.teses.usp.br/teses/disponiveis/85/85134/tde-21072015-104725/.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
7

Prymus, Jiří. "Propojení knihovny pro zpracování obrazu s jazykem Lua." Master's thesis, Vysoké učení technické v Brně. Fakulta elektrotechniky a komunikačních technologií, 2012. http://www.nusl.cz/ntk/nusl-219670.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
8

Kulpreet. "Quantitative documentation of construction industry best practices." 1995. http://catalog.hathitrust.org/api/volumes/oclc/33156208.html.

Full text
Abstract:
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).
APA, Harvard, Vancouver, ISO, and other styles
9

Lau, Lun. "Digital pictorial documentation and construction productivity measurement." 2000. http://catalog.hathitrust.org/api/volumes/oclc/45549232.html.

Full text
Abstract:
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).
APA, Harvard, Vancouver, ISO, and other styles
10

McLain, Rebecca J. "Land documentation and farmer investments in Central Honduras." 1986. http://catalog.hathitrust.org/api/volumes/oclc/15610624.html.

Full text
Abstract:
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).
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Documentation des API"

1

Pringle, Michael. APA documentation and style. New Jersey: Longman, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Gail, Raikes, and MacMillan Vicki, eds. Cites & sources: An APA documentation guide. 3rd ed. Toronto: Nelson Education, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Pringle, Michael. The APA style of documentation: A pocket guide. New Jersey: Longman, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

John, Gonzales, and American Psychological Association, eds. The APA style of documentation: A pocket guide. New Jersey: Longman, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Pringle, Michael. The APA style of documentation: A pocket guide. New Jersey: Longman, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Pringle, Michael. The APA style of documentation: A pocket guide. New Jersey: Longman, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pringle, Michael. The APA style of documentation: A pocket guide. New Jersey: Longman, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Trimmer, Joseph F. A guide to MLA documentation: With an appendix on APA style. 3rd ed. Boston: Houghton Mifflin, 1994.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

A guide to MLA documentation: With an appendix on APA style. 5th ed. Boston: Houghton Mifflin, 1999.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Trimmer, Joseph F. A guide to MLA documentation: With an appendix on APA style. 4th ed. Boston: Houghton Mifflin, 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Documentation des API"

1

Inzunza, Sergio, Reyes Juárez-Ramírez, and Samantha Jiménez. "API Documentation." In Advances in Intelligent Systems and Computing, 229–39. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-77712-2_22.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

De, Brajesh. "API Documentation." In API Management, 59–80. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-1305-6_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Ugurlu, Tugberk, Alexander Zeitler, and Ali Kheyrollahi. "Tracing, Logging, and API Documentation." In Pro ASP.NET Web API, 545–76. Berkeley, CA: Apress, 2013. http://dx.doi.org/10.1007/978-1-4302-4726-5_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Rodríguez, Rolando, Roberto Espinosa, Devis Bianchini, Irene Garrigós, Jose-Norberto Mazón, and Jose Jacobo Zubcoff. "Extracting Models from Web API Documentation." In Current Trends in Web Engineering, 134–45. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-35623-0_14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Shi, Lin, Hao Zhong, Tao Xie, and Mingshu Li. "An Empirical Study on Evolution of API Documentation." In Fundamental Approaches to Software Engineering, 416–31. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19811-3_29.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tran, Dinh Huy, Hua Phung Nguyen, and Duy Hanh Le. "EasySearch: Finding Relevant Functions Based on API Documentation." In Advances in Intelligent Systems and Computing, 143–54. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-11680-8_12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Cao, Hanyang, Jean-Rémy Falleri, and Xavier Blanc. "Automated Generation of REST API Specification from Plain HTML Documentation." In Service-Oriented Computing, 453–61. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-69035-3_32.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Koren, István, and Ralf Klamma. "Generation of Web Frontends from API Documentation with Direwolf Interaction Flow Designer." In Lecture Notes in Computer Science, 492–95. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-91662-0_42.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Abukwaik, Hadil, Mohammed Abujayyab, and Dieter Rombach. "Towards Seamless Analysis of Software Interoperability: Automatic Identification of Conceptual Constraints in API Documentation." In Software Architecture, 67–83. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-48992-6_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Lin, Chenghua, Yulan He, Carlos Pedrinaci, and John Domingue. "Feature LDA: A Supervised Topic Model for Automatic Detection of Web API Documentations from the Web." In The Semantic Web – ISWC 2012, 328–43. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-35176-1_21.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Documentation des API"

1

Subramanian, Siddharth, Laura Inozemtseva, and Reid Holmes. "Live API documentation." In ICSE '14: 36th International Conference on Software Engineering. New York, NY, USA: ACM, 2014. http://dx.doi.org/10.1145/2568225.2568313.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Meng, Michael, Stephanie M. Steinhardt, and Andreas Schubert. "Optimizing API Documentation." In SIGDOC '20: The 38th ACM International Conference on Design of Communication. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3380851.3416759.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Zhong, Hao, and Zhendong Su. "Detecting API documentation errors." In SPLASH '13: Conference on Systems, Programming, and Applications: Software for Humanity. New York, NY, USA: ACM, 2013. http://dx.doi.org/10.1145/2509136.2509523.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Stylos, Jeffrey, Andrew Faulring, Zizhuang Yang, and Brad A. Myers. "Improving API documentation using API usage information." In 2009 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC). IEEE, 2009. http://dx.doi.org/10.1109/vlhcc.2009.5295283.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Uddin, Gias, Foutse Khomh, and Chanchal K. Roy. "Towards Crowd-Sourced API Documentation." In 2019 IEEE/ACM 41st International Conference on Software Engineering: Companion Proceedings (ICSE-Companion). IEEE, 2019. http://dx.doi.org/10.1109/icse-companion.2019.00129.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Parnin, Chris, and Christoph Treude. "Measuring API documentation on the web." In Proceeding of the 2nd international workshop. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/1984701.1984706.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Kramer, Douglas. "API documentation from source code comments." In the 17th annual international conference. New York, New York, USA: ACM Press, 1999. http://dx.doi.org/10.1145/318372.318577.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Watson, Robert, Mark Mark Stamnes, Jacob Jeannot-Schroeder, and Jan H. Spyridakis. "API documentation and software community values." In the 31st ACM international conference. New York, New York, USA: ACM Press, 2013. http://dx.doi.org/10.1145/2507065.2507076.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Treude, Christoph, and Maurício Aniche. "Where does Google find API documentation?" In ICSE '18: 40th International Conference on Software Engineering. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3194793.3194796.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Arimatsu, Yuu, Yoshiya Ishida, Kunihiro Noda, and Takashi Kobayashi. "Enriching API Documentation by Relevant API Methods Recommendation Based on Version History." In 2018 IEEE Third International Workshop on Dynamic Software Documentation (DySDoc3). IEEE, 2018. http://dx.doi.org/10.1109/dysdoc3.2018.00014.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Documentation des API"

1

Badia, R., J. Ejarque, S. Böhm, C. Soriano, and R. Rossi. D4.4 API and runtime (complete with documentation and basic unit testing) for IO employing fast local storage. Scipedia, 2021. http://dx.doi.org/10.23967/exaqute.2021.9.001.

Full text
Abstract:
This deliverable presents the activities performed on the ExaQUte project task 4.5 Development of interface to fast local storage. The activities have been focused in two aspects: reduction of the storage space used by applications and design and implementation of an interface that optimizes the use of fast local storage by MPI simulations involved in the project applications. In the rst case, for one of the environments involved in the project (PyCOMPSs) the default behavior is to keep all intermediate les until the end of the execution, in case these les are reused later by any additional task. In the case of the other environment (HyperLoom), all les are deleted by default. To unify these two behaviours, the calls \delete object" and \detele le"have been added to the API and a ag \keep" that can be set to true to keep the les and objects that maybe needed later on. We are reporting results on the optimization of the storage needed by a small case of the project application that reduces the storage needed from 25GB to 350MB. The second focus has been on the de nition of an interface that enables the optimization of the use of local storage disk. This optimization focuses on MPI simulations that may be executed across multiple nodes. The added annotation enables to de ne access patters of the processes in the MPI simulations, with the objective of giving hints to the runtime of where to allocate the di erent MPI processes and reduce the data transfers, as well as the storage usage.
APA, Harvard, Vancouver, ISO, and other styles
2

Rossi, R., I. López, and C. Soriano. D1.1 Solvers "stub" implementation of the capabilities to be delivered. Scipedia, 2021. http://dx.doi.org/10.23967/exaqute.2021.2.008.

Full text
Abstract:
The current deliverable describes the initial API available for the solvers. The API is intended to be based on the Kratos Multiphysics fraemework and will evolve during the project. The current deliverable describes the essential features of the interface and provides an initial working implementation to be used as a basis for the future developements. The initial implementation described here is currently operative on the master branch of Kratos. As of the end of July 2018 (moment of handing in of current deliverable) the interface is operative and is being used “in production”. Nevertheless, it still does not fully support the model serialization capabilities that are needed for pyCompSS and HyperLoom. The interface is documented in the project wiki page [wiki]. The same documentation is also presented in the current deliverable.
APA, Harvard, Vancouver, ISO, and other styles
3

Rasmussen, A. L., and A. A. sanders. Documentation of the NBS APD and pin calibration systems for measuring peak power and energy of low-level 1.064 �mlaser pulses. Gaithersburg, MD: National Bureau of Standards, 1985. http://dx.doi.org/10.6028/nbs.ir.85-3032.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Documentation des API' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography