Relevant bibliographies by topics / API (Application Programming Interface)

Contents

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

Academic literature on the topic 'API (Application Programming Interface)'

Author: Grafiati
Published: 4 June 2021
Last updated: 7 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 'API (Application Programming Interface).'

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 "API (Application Programming Interface)"

1

Ofoeda, Joshua, Richard Boateng, and John Effah. "Application Programming Interface (API) Research." International Journal of Enterprise Information Systems 15, no. 3 (July 2019): 76–95. http://dx.doi.org/10.4018/ijeis.2019070105.

Full text
Abstract:
The purpose of this study is to perform a synthesis of API research. The study took stock of literature from academic journals on APIs with their associated themes, frameworks, methodologies, publication outlets and level of analysis. The authors draw on a total of 104 articles from academic journals and conferences published from 2010 to 2018. A systematic literature review was conducted on the selected articles. The findings suggest that API research is primarily atheoretical and largely focuses on the technological dimensions such as design and usage; thus, neglecting most of the social issues such as the business and managerial applications of APIs, which are equally important. Future research directions are provided concerning the gaps identified.
APA, Harvard, Vancouver, ISO, and other styles
2

Muri, M. Fuadi Aziz, Hendrik Setyo Utomo, and Rabini Sayyidati. "Search Engine Get Application Programming Interface." Jurnal Sains dan Informatika 5, no. 2 (December 1, 2019): 88–97. http://dx.doi.org/10.34128/jsi.v5i2.175.

Full text
Abstract:
Application Programming Interface (API) is a function concept that can be called by other programs. The API works as a link that unites various applications of various types of platforms, commonly known as API public names. The public API has been widely spread, while its users, programmers who want to search for public APIs, must browse through various methods such as general search engines, repository documentation or directly in web articles. The user does not yet have a system specifically for collecting public-public APIs, so that users have difficulty in performing API public link searches. The solution to these problems can be solved by building a web framework with a search engine interface that provides specific public-public searches for the API, so that users can search the API public more easily. Web Service is an API that is made to support the interaction between two or more different applications through a network. Representational State Transfer (ReST) is one of the rules.
APA, Harvard, Vancouver, ISO, and other styles
3

Rakhmawati, Nur Aini, Sayekti Harits Suryawan, Muhammad Ariful Furqon, and Deny Hermansyah. "Indonesia’s Public Application Programming Interface (API)." Jurnal Penelitian Pos dan Informatika 9, no. 2 (December 30, 2019): 85. http://dx.doi.org/10.17933/jppi.2019.090201.

Full text
Abstract:
<p class="JGI-AbstractIsi">Indonesia places the fifth position of the most internet users in the world. Consequently, data transaction through HTTP protocol saw an increase. An open API can facilitate Indonesia's users to access data and build application through HTTP protocol. In this paper, 38 open APIs were investigated and classified by using five criteria, namely technology, authentication, scope, source, and approval request. In general, the open APIs in Indonesia employ RESTful as a web service and JSON format as data format. In term of authentication, API key is a common method in most of open APIs.</p>
APA, Harvard, Vancouver, ISO, and other styles
4

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
5

Sahbudin, Murtadha Arif Bin, Chakib Chaouch, Salvatore Serrano, and Marco Scarpa. "Application-Programming Interface (API) for Song Recognition Systems." Advances in Science, Technology and Engineering Systems Journal 6, no. 2 (April 2021): 846–59. http://dx.doi.org/10.25046/aj060298.

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

Jones, Norman L., Robert M. Wallace, Russell Jones, Cary Butler, and Alan Zundel. "Efficient application programming interface for multi-dimensional modeling data." Journal of Hydroinformatics 14, no. 1 (June 7, 2011): 1–12. http://dx.doi.org/10.2166/hydro.2011.013.

Full text
Abstract:
This paper describes an Application Programming Interface (API) for managing multi-dimensional data produced for water resource computational modeling that is being developed by the US Army Engineer Research and Development Center (ERDC), in conjunction with Brigham Young University. This API, along with a corresponding data standard, is being implemented within ERDC computational models to facilitate rapid data access, enhanced data compression and data sharing, and cross-platform independence. The API and data standard are known as the eXtensible Model Data Format (XMDF), and version 1.3 is available for free download. This API is designed to manage geometric data associated with grids, meshes, riverine and coastal cross sections, and both static and transient array-based datasets. The inclusion of coordinate system data makes it possible to share data between models developed in different coordinate systems. XMDF is used to store the data-intensive components of a modeling study in a compressed binary format that is platform-independent. It also provides a standardized file format that enhances modeling linking and data sharing between models.
APA, Harvard, Vancouver, ISO, and other styles
7

Selby, Peter, Rafael Abbeloos, Jan Erik Backlund, Martin Basterrechea Salido, Guillaume Bauchet, Omar E. Benites-Alfaro, Clay Birkett, et al. "BrAPI—an application programming interface for plant breeding applications." Bioinformatics 35, no. 20 (March 23, 2019): 4147–55. http://dx.doi.org/10.1093/bioinformatics/btz190.

Full text
Abstract:
Abstract Motivation Modern genomic breeding methods rely heavily on very large amounts of phenotyping and genotyping data, presenting new challenges in effective data management and integration. Recently, the size and complexity of datasets have increased significantly, with the result that data are often stored on multiple systems. As analyses of interest increasingly require aggregation of datasets from diverse sources, data exchange between disparate systems becomes a challenge. Results To facilitate interoperability among breeding applications, we present the public plant Breeding Application Programming Interface (BrAPI). BrAPI is a standardized web service API specification. The development of BrAPI is a collaborative, community-based initiative involving a growing global community of over a hundred participants representing several dozen institutions and companies. Development of such a standard is recognized as critical to a number of important large breeding system initiatives as a foundational technology. The focus of the first version of the API is on providing services for connecting systems and retrieving basic breeding data including germplasm, study, observation, and marker data. A number of BrAPI-enabled applications, termed BrAPPs, have been written, that take advantage of the emerging support of BrAPI by many databases. Availability and implementation More information on BrAPI, including links to the specification, test suites, BrAPPs, and sample implementations is available at https://brapi.org/. The BrAPI specification and the developer tools are provided as free and open source.
APA, Harvard, Vancouver, ISO, and other styles
8

Gee-Swee Poo and Chye-Guan Chew. "Modeling of the XOM/XMP application programming interface (API)." IEEE Communications Magazine 34, no. 8 (1996): 134–44. http://dx.doi.org/10.1109/35.533932.

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

Roberts, Andrew M., Aaron K. Wong, Ian Fisk, and Olga G. Troyanskaya. "GIANT API: an application programming interface for functional genomics." Nucleic Acids Research 44, W1 (April 20, 2016): W587—W592. http://dx.doi.org/10.1093/nar/gkw289.

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

Rudianto, Rudianto, and Eko Budi Setiawan. "Sistem Pengawasan Aktifitas Penggunaan Smartphone Android." Jurnal ULTIMA InfoSys 9, no. 1 (July 6, 2018): 24–31. http://dx.doi.org/10.31937/si.v9i1.839.

Full text
Abstract:
Availability the Application Programming Interface (API) for third-party applications on Android devices provides an opportunity to monitor Android devices with each other. This is used to create an application that can facilitate parents in child supervision through Android devices owned. In this study, some features added to the classification of image content on Android devices related to negative content. In this case, researchers using Clarifai API. The result of this research is to produce a system which has feature, give a report of image file contained in target smartphone and can do deletion on the image file, receive browser history report and can directly visit in the application, receive a report of child location and can be directly contacted via this application. This application works well on the Android Lollipop (API Level 22). Index Terms— Application Programming Interface(API), Monitoring, Negative Content, Children, Parent.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "API (Application Programming Interface)"

1

Yao, Kuan. "Implementing an Application Programming Interface for Distributed Adaptive Computing Systems." Thesis, Virginia Tech, 2000. http://hdl.handle.net/10919/33329.

Full text
Abstract:
Developing applications for distributed adaptive computing systems (ACS) requires developers to have knowledge of both parallel computing and configurable computing. Furthermore, portability and scalability are required for developers to use innovative ACS research directly in deployed systems. This thesis presents an Application Programming Interface (API) implementation developed in a scalable parallel ACS system. The API gives the developer the ability to easily control both single board and multi-board systems in a network cluster environment. The API implementation is highly portable and scalable, allowing ACS researchers to easily move from a research system to a deployed system. The thesis details the design and implementation of the API, as well as analyzes its performance.
Master of Science
APA, Harvard, Vancouver, ISO, and other styles
2

Chivi, Daniel, and Gran Joakim Östling. "Administration av API-drivna enheter och tjänster för slutanvändare : En fallstudie av API-tjänster." Thesis, KTH, Skolan för kemi, bioteknologi och hälsa (CBH), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-223347.

Full text
Abstract:
I dagsläget tenderar många att använda tjänster som hanteras separat. Arbetet undersöker om det är möjligt att sammankoppla ett fåtal tjänster i en gemensam webbapplikation för att underlätta kommunicering mellan tjänsterna samt att förbättra användarvänligheten. Företaget A Great Thing har i åtanke att skapa en webbapplikation som tillåter användare att med hjälp av deras applikation skapa agenter som sköter händelser från användarens begäran, exempelvis “spela upp en låt vid en viss tid”. Metodiken som tillämpats har dels varit en fallstudie och dels användarbaserade metoder i form av enkätundersökning samt ett användartest. Ytterligare undersöktes hur kommunikationen går mellan tjänsters API, och de nödvändiga parametrar som utbyter data. Slutligen evalueras den framtagna prototypen enligt vissa riktlinjer inom användarvänlighet. Examensarbetets resultat är i form av en webbprototyp med fokus på användarvänlighet, implementering av API:er, användartest på faktiska användare samt statistik på efterfrågan av tjänster. Vidare har även en marknadsundersökning utförts för att belysa ekonomiska vinstmöjligheter genom API-distribution. Slutsatsen dras att det är möjligt att sammankoppla API:er och dess tjänster för att uppnå ett användarvänligt gränssnitt samt hur nödvändiga parametrar disponeras på ett effektivt vis. Vidare är förhoppningen att utomstående läsare skapar en förståelse om hur sammankopplingen går till på ett strukturerat och informativt tillvägagångssätt. Även hur olika tekniska metoder inom användarvänlighet kan tillämpas vid konstruktion av prototyper.
Nowadays people tend to use services and appliances that are managed seperately. This thesis examines the possibility of connecting different services into one main web application to faciliate communication between these services. A Great Thing have embraced the need of connecting applications to a single device and therefore, wants to create a web application integrated with the use of agents. These agents are built to manage the events a user request. For example ”Play a song at a specific time”. The methodology applied has partly been a case study and partly user-based methods in form of a survery and a user test. Further research was conducted on communication between service API:s and the necessary parameters that exchange data. Finally, the developed prototype was evaluated according to some usability guidelines. The thesis’s results are presented in the form of a web prototype focused on usability, implementation of APIs, user test of actual users and statistics of demanded services. In addition, a market research has been conducted to highlight economic benefits through API distribution. The conclusion is drawn that it is possible to link API:s and their services to achieve a user-friendly interface and how to use different parameters in an efficient way. Furthermore, the hope is that external readers will understand how the connection between API:s works in a structured and informative approach. Also how different technical methods for usability can be applied in construction of prototypes.
APA, Harvard, Vancouver, ISO, and other styles
3

Feng, Xuan. "Evaluation of Capuchin Application Programming Interface : Implementing a Mobile TV Client." Thesis, KTH, Kommunikationssystem, CoS, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-91497.

Full text
Abstract:
The purpose of this research was to evaluate the Capuchin API launched by Sony Ericsson at Lund, Sweden in 2008. The Capuchin API bridges Adobe’s Flash graphics and effects with JSR support from Java ME. We evaluated Capuchin API with regard to its suitability for a Mobile TV application. We tested this API in Ericsson’s TV lab where we had access to live TV streams and online multimedia resources by implementing a Mobile TV client. This test application was named “Min TV”, in English: “My TV”. Using Capuchin in the Ericsson TV lab environment has shown that it has some benefits, but also has many drawbacks. The Flash developer can be used to create an animated user interface and Java developers can do complex programming. At this early stage Capuchin technology is not mature enough, nor is it suitable for Mobile TV client development. Only after Sony Ericsson adds features such as soft keys, easier debugging of Flash Lite standalone applications, test emulator support in the software development kit, and more data communication methods than string and number, only then it will be a suitable technology for Mobile TV applications. Ericsson’s current Mobile TV application client was built using a framework called ECAF, which supports a graphics frontend and Java ME as backend. We compared ECAF and Min TV with respect to parameters such as: flexibility, performance, memory footprint, code size, and cost of skinning. (All these parameters are explained in detail in the methodology chapter.) As a possible future technology for Mobile TV, we evaluated a number of different presentation/graphics technologies including HECL, SVG Tiny, MIDP 3.0, .NET Compact Framework, etc. Moreover, we examed if a pure Flash Lite client application is a viable solution for Mobile TV. The comparison of different presentation technologies showed that Java ME is a comprehensive platform for mobile development offering all the necessary support from third party graphical user interface makers. .NET CF also looks like a good option for development with the scaled down capabilities for different programming languages supported using CLR.
Syftet med denna forskning var att utvärdera Capuchin API lanserades av Sony Ericsson i Lund, Sverige 2008. Den Capuchin API broar Adobe Flash grafik och effekter med JSR stöd från Java ME. Vi utvärderade Capuchin API med avseende på dess lämplighet för ett mobil-tv ansökan. Vi testade detta API i Ericssons TV lab där vi hade tillgång till TV-strömmar och online multimediaresurser genom en mobil-TV-klient. Detta test ansökan hette "Min TV", på engelska: "My TV". Använda Capuchin i Ericsson TV lab miljö har visat att det har vissa fördelar, men också många nackdelar. Flash-utvecklare kan användas för att skapa en animerad användargränssnitt och Java utvecklare kan göra komplexa programmering. På detta tidiga stadium Capuchin tekniken inte mogen, det är inte heller lämpliga för mobil-TV-klient utveckling. Först efter Sony Ericsson lägger till detaljer såsom mjuka nycklar, enklare felsökning av Flash Lite fristående program, testa emulator stöd i Software Development Kit, och mer data kommunikationsmetoder än string och antal, först då kommer det att vara en lämplig teknik för mobil-TV-program . Ericssons nuvarande mobil-tv ansökan klient byggdes med hjälp av en ram som kallas ECAF, som stöder en grafiska gränssnittet och Java ME som backend. Vi jämförde ECAF och min TV med avseende på parametrar såsom flexibilitet, prestanda, minne fotavtryck kod storlek och kostnaden för avhudning. (Alla dessa parametrar förklaras i detalj i den metod kapitel.) Som en möjlig framtida teknik för mobil-TV Vi utvärderade ett antal olika presentation / grafik teknik inklusive HECL, SVG Tiny, MIDP 3.0,. NET Compact Framework, etc. Dessutom har vi examed om en ren Flash Lite klientprogrammet är en hållbar lösning för mobil-TV. Jämförelsen mellan olika presentation teknik visade att Java ME är en övergripande plattform för mobila utvecklingen erbjuder allt nödvändigt stöd från tredje part grafiskt användargränssnitt beslutsfattare. . NET CF också ser ut som ett bra alternativ för utvecklingen med ned kapacitet för olika programspråk som stöds med hjälp av CLR.
APA, Harvard, Vancouver, ISO, and other styles
4

Veldsman, Werner Pieter. "SNP based literature and data retrieval." Thesis, University of the Western Cape, 2016. http://hdl.handle.net/11394/5345.

Full text
Abstract:
>Magister Scientiae - MSc
Reference single nucleotide polymorphism (refSNP) identifiers are used to earmark SNPs in the human genome. These identifiers are often found in variant call format (VCF) files. RefSNPs can be useful to include as terms submitted to search engines when sourcing biomedical literature. In this thesis, the development of a bioinformatics software package is motivated, planned and implemented as a web application (http://sniphunter.sanbi.ac.za) with an application programming interface (API). The purpose is to allow scientists searching for relevant literature to query a database using refSNP identifiers and potential keywords assigned to scientific literature by the authors. Multiple queries can be simultaneously launched using either the web interface or the API. In addition, a VCF file parser was developed and packaged with the application to allow users to upload, extract and write information from VCF files to a file format that can be interpreted by the novel search engine created during this project. The parsing feature is seamlessly integrated with the web application's user interface, meaning there is no expectation on the user to learn a scripting language. This multi-faceted software system, called SNiPhunter, envisions saving researchers time during life sciences literature procurement, by suggesting articles based on the amount of times a reference SNP identifier has been mentioned in an article. This will allow the user to make a quantitative estimate as to the relevance of an article. A second novel feature is the inclusion of the email address of a correspondence author in the results returned to the user, which promotes communication between scientists. Moreover, links to external functional information are provided to allow researchers to examine annotations associated with their reference SNP identifier of interest. Standard information such as digital object identifiers and publishing dates, that are typically provided by other search engines, are also included in the results returned to the user.
National Research Foundation (NRF) /The South African Research Chairs Initiative (SARChI)
APA, Harvard, Vancouver, ISO, and other styles
5

Collini, Alex. "Realizzazione di un'applicazione mobile Android basata su interazioni con interfacce API di diversi servizi." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2015. http://amslaurea.unibo.it/9256/.

Full text
Abstract:
La grande crescita e l'enorme distribuzione che hanno avuto negli ultimi tempi i moderni devices mobile (smartphones, tablet, dispositivi wearable, etc...) ha dato l'avvio ad un massiccio sviluppo di applicazioni mobile di qualunque genere, dall'health-care all'AR (Augmented Reality, realtà aumentata), dalle applicazioni social alle applicazioni che offrono servizi all'utente.
APA, Harvard, Vancouver, ISO, and other styles
6

Aguilar, David Pedro. "A framework for evaluating the computational aspects of mobile phones." [Tampa, Fla] : University of South Florida, 2008. http://purl.fcla.edu/usf/dc/et/SFE0002390.

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

Guerra, Eduardo Leal. "InGriDE: um ambiente integrado e extensível de desenvolvimento para computação em grade." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/45/45134/tde-04052010-193112/.

Full text
Abstract:
Recentes avanços proporcionaram às grades computacionais um bom nível de maturidade. Esses sistemas têm sido implantados em ambientes de produção de qualidade na comunidade de pesquisa acadêmica e vêm despertando um grande interesse da indústria. Entretanto, desenvolver aplicações para essas infra-estruturas heterogêneas e distribuídas ainda é uma tarefa complexa e propensa a erros. As iniciativas de facilitar essa tarefa resultaram, na maioria dos casos, em ferramentas não integradas e baseadas em características específicas de cada grade computacional. O presente trabalho tem como objetivo minimizar a dificuldade de desenvolvimento de aplicações para a grade através da construção de um ambiente integrado e extensível de desenvolvimento (IDE) para computação em grade chamado InGriDE. O InGriDE fornece um conjunto único de ferramentas compatíveis com diferentes sistemas de middleware, desenvolvidas baseadas na interface de programação Grid Application Toolkit (GAT). O conjunto de funcionalidades do InGriDE foi desenvolvido com base na plataforma Eclipse que, além de fornecer um arcabouço para construção de IDEs, facilita a extensão do conjunto inicial de funcionalidades. Para validar a nossa solução, utilizamos em nosso estudo de caso o middleware InteGrade, desenvolvido no nosso grupo de pesquisa. Os resultados obtidos nesse trabalho mostraram a viabilidade de fornecer independência de middleware para IDEs através do uso de uma interface genérica de programação como o GAT. Além disso, os benefícios obtidos com o uso do Eclipse como arcabouço para construção de IDEs indicam que os recursos fornecidos por esse tipo de arcabouço atendem de forma eficiente as necessidades inerentes ao processo de desenvolvimento de aplicações para a grade.
Computational grids have evolved considerably over the past few years. These systems have been deployed in production environments in the academic research community and have increased the interest by the industrial community. However, developing applications over heterogeneous and distributed infrastructure is still a complex and error prone process. The initiatives to facilitate this task, in the majority of the cases, resulted in isolated, middleware-specific tools. This work has the objective of minimizing the difficulty of developing grid applications through the construction of an integrated and extensible development environment for grid computing, called InGriDE. InGriDE provides a unique set of tools, compliant with different middleware systems, based on the Grid Application Toolkit (GAT). We developed the InGriDE set of features, based on the Eclipse platform, which provides both a framework for building IDEs and the possibility to extend the initial set of features. To validate our solution we used the InteGrade middleware, developed in our research group, as our case study. The results obtained from our work showed the viability of providing middleware independence to IDEs through the use of a generic application programming interface like GAT. Moreover, the benefits obtained through the use of Eclipse as our framework for building IDEs indicates that this kind of framework satisfies the requirements inherent to the grid application development process in a efficient way.
APA, Harvard, Vancouver, ISO, and other styles
8

Fiume, Claudio. "La tecnologia API come fattore di cambiamento per le aziende e per i clienti." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2019.

Find full text
Abstract:
Un interesse sempre maggiore per lo studio dei Business Process ha apportato all'interno delle aziende implementazioni organizzative e software, conseguendo numerosi vantaggi sul coordinamento delle attività e sulla gestione delle risorse in modo efficace. Infatti, l’approccio ai processi di business nel nuovo millennio mette in evidenza come la componente informatica sia fondamentale per ottenere processi snelli ed efficienti. Questo lavoro di tesi nasce dal periodo di stage in Crif S.p.A. dove ho avuto la possibilità di lavorare sulla tecnologia API (Application Programming Interface) ed apprendere il modo in cui essa viene utilizzata, avendo un duplice risvolto in quanto impatta sia sui processi aziendali che sul cliente stesso. Le API offrono un modello comune per aiutare le persone a collaborare, rendendo dati ed informazioni disponibili tramite applicazioni informatiche. Le API sono un'estensione di buoni rapporti commerciali, infatti consentono una migliore comunicazione e condivisione delle risorse, garantiscono un accesso alle informazioni in tempo reale ed infine, di fondamentale importanza, permettono l'accesso a nuovi mercati. Inoltre, offrono un cambiamento rispetto ai metodi del passato in quanto consentono una maggiore agilità, innovazione tecnologica, integrazione e nuove fonti di monetizzazione. È trattato anche il tema del Project Management che è diventato molto più di un insieme di tecniche e di metodologie, infatti può essere definito come un sistema orientato ad obiettivi prestabiliti. Particolare attenzione è rivolta ai progetti software in quanto la tecnologia API è strettamente legata ad uno sviluppo recente che ha una notevole componente tecnologica. Infine, è effettuata una suddivisone delle API (privata, partner e pubblica) dove ognuna ha i propri vantaggi e benefici. Poi, ad ogni fornitore di API spetta la scelta della strategia migliore per avere una buona commercializzazione e di conseguenza maggiori ricavi.
APA, Harvard, Vancouver, ISO, and other styles
9

MAIA, Mikaela Anuska Oliveira. "Uma abordagem para adaptação de clientes do Java Collections framework baseada em técnicas de migração de APÌs." Universidade Federal de Campina Grande, 2014. http://dspace.sti.ufcg.edu.br:8080/jspui/handle/riufcg/392.

Full text
Abstract:
Submitted by Johnny Rodrigues (johnnyrodrigues@ufcg.edu.br) on 2018-04-16T18:53:29Z No. of bitstreams: 1 MIKAELA ANUSKA OLIVEIRA MAIA - DISSERTAÇÃO PPGCC 2014..pdf: 1160102 bytes, checksum: 5eb99698589be1aeca83623ca4b79e2f (MD5)
Made available in DSpace on 2018-04-16T18:53:29Z (GMT). No. of bitstreams: 1 MIKAELA ANUSKA OLIVEIRA MAIA - DISSERTAÇÃO PPGCC 2014..pdf: 1160102 bytes, checksum: 5eb99698589be1aeca83623ca4b79e2f (MD5) Previous issue date: 2014-08
Apesar da diversidade que a API do Java Collections Framework(JCF) provê, com uma variedade de implementações para várias estruturas de dados, os desenvolvedores podem escolher interfaces ou classes inadequadas, em termos de eficiência ou propósito. Isto pode acontecer devido à documentação da API ser insuficiente ou a falta de análise ponderada pelo desenvolvedor de acordo com exigências do contexto. É possível a substituição manual, em paralelo com uma análise do contexto do programa. No entanto, isso é cansativo e suscetível a erros,desestimulando a modificação. Neste trabalho, nós definimos uma abordagem semi-automática para a seleção de interfaces e implementações dentro do JCF e a modificação de clientes do JCF, com base em técnicas de migração de API. A abordagem ajuda o usuário a escolher a coleção mais apropriada, com base em requisitos coletados por meio de perguntas mais intuitivas para o usuário. A seleção é resolvida com uma árvore de decisão que, a partir das respostas dadas pelo desenvolvedor, decide qual é a interface e implementação mais adequada do JCF. Após esta decisão, a modificação do programa é realizado por meio de adaptadores, minimizando a modificação do código fonte. Nós avaliamos a abordagem, implementada em uma ferramenta de apoio, com um estudo experimental que compreende estudantes de Ciência da Computação distribuídos aleatoriamente em grupos, os quais realizaram mudanças para clientes do JCF por diferentes métodos: manualmente, utilizando-se do EclipseJavaSearch e nossa abordagem. Os resultados foram avaliados na qualidade, esforço e tempo gasto. Descobrimos que a maioria dos usuários teve dificuldades em escolher a interface ou implementação apropriada para os requisitos apresentados. Nossa abordagem evidenciou uma melhora no esforço de selecionar a melhor coleção para a exigência, poupando algum tempo no processo. Sobre a qualidade da coleção selecionada, encontramos o mesmo comportamento usando as duas ferramentas.
Despite the API diversity that the Java Collections Framework (JCF) provides, with diverse implementations for several data structures, developers may choose inappropriate interfaces or classes, in terms of efficiency or purpose. This may happen due to insufficient API documentation or the lack of thoughtful analysis by the developer according to context requirements. A possible solution is manual replacement, in parallel with an analysis of the program context. However, this is tiresome and error-prone, discouraging the modification. In this work, we define a semi-automatic approach for (i) the selection of interfaces and implementation within the JCF and (ii) the modification of JCF clients, based on API migration techniques. The approach helps the user in choosing the most appropriate collection, based on requirements collected by means of simple yes/no questions. The selection is resolved with a decision tree that, from the answers given by the developer, decides which is the most adequate interface (and implementation) from the JCF. After this decision, the actual program modification is performed by means of adapters, minimizing the source code modification We evaluate the approach, as implemented in a supporting tool,with an experimental study comprising computer science students randomly distributed into groups,whose task was performing changes to JCF clients by different methods (manually, using Eclipse’s Java Search and our approach); the results were evaluated on quality, effort and time spent. We found that most students had a hard time choosing the right interface or implementation for the given requirements. Our approach seemed to improve the effort of selecting the best collection for the requirement, saving sometime in the process. Regarding the quality of the collection selected, we found the same behavior using both tools.
APA, Harvard, Vancouver, ISO, and other styles
10

Silva, Lincoln David Nery e. "Uma proposta de API para desenvolvimento de aplicações multiusuário e multidispositivo para TV Digital utilizando o Middleware Ginga." Universidade Federal da Paraí­ba, 2008. http://tede.biblioteca.ufpb.br:8080/handle/tede/6118.

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

Books on the topic "API (Application Programming Interface)"

1

DB2 universal database application programming interface (API) developer's guide. New York: McGraw-Hill, 2000.

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

E, Sanders Roger. DB2 universal database application programming interface (API) developer's guide. New York: McGraw-Hill, 2000.

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

Institute Of Electrical and Electronics Engineers. IEEE standard for information technology: Directory services C language interfaces--binding for application program interface (API). New York: Institute of Electrical and Electronics Engineers, Inc., 1994.

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

Institute Of Electrical and Electronics Engineers. IEEE standard for information technology: POSIX Ada language interfaces -- Part 1: Binding for system application program interface (API). New York, NY: Institute of Electrical and Electronics Engineers, 1992.

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

1971-, Jinmei Tatuya, and Shima Keiichi 1970-, eds. IPv6 socket API extensions: Programmer's guide. Burlington, MA: Morgan Kaufmann Publishers, 2009.

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

Li, Qing. IPv6 socket API extensions: Programmer's guide. Burlington, MA: Morgan Kaufmann Publishers, 2009.

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

Li, Qing. IPv6 socket API extensions: Programmer's guide. Burlington, MA: Morgan Kaufmann Publishers, 2009.

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

Institute Of Electrical and Electronics Engineers. IEEE standard for information technology: POSIX FORTRAN 77 language interfaces -- Part 1: Binding for system application program interface (API). New York, NY, USA: Institute of Electrical and Electronics Engineers, 1992.

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

API design for C++. Burlington, MA: Morgan Kaufmann, 2011.

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

Bidelman, Eric. Using the HTML5 filesystem API. Sebastopol, CA: O'Reilly Media, 2011.

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

Book chapters on the topic "API (Application Programming Interface)"

1

Gadre, Dhananjay V., and Sarthak Gupta. "Application Programming Interface (API)." In Getting Started with Tiva ARM Cortex M4 Microcontrollers, 95–100. New Delhi: Springer India, 2017. http://dx.doi.org/10.1007/978-81-322-3766-2_8.

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

Heshmatisafa, Saeid, and Marko Seppänen. "API Utilization and Monetization in Finnish Industries." In Agile Processes in Software Engineering and Extreme Programming – Workshops, 23–31. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58858-8_3.

Full text
Abstract:
Abstract Many companies have followed the trend toward exposing their business assets through open (i.e., Web) application programming interfaces (APIs). However, these firms appear to have adopted API technology largely to meet their customers’ needs and demands. The pressures on industries to develop, implement, and maintain API products and services can prevent companies from gaining a greater awareness of API development’s benefits. Firms may thus miss out on related monetary or non-monetary exploitation of their business assets. This study explored the status of the API economy and development among Finnish industries. The dataset comprised publicly available information from 226 private and public organizations representing a variety of industries, such as industrial, consumer goods, and services sectors. The current status of API readiness, types, protocols, and monetization models is presented to provide a more comprehensive overview.
APA, Harvard, Vancouver, ISO, and other styles
3

Chun, Doo Man, Hyung Jung Kim, Jae Chul Lee, and Sung Hoon Ahn. "Web-Based Material Database for Material Selection and its Application Programming Interface (API) for CAD." In The Mechanical Behavior of Materials X, 1593–96. Stafa: Trans Tech Publications Ltd., 2007. http://dx.doi.org/10.4028/0-87849-440-5.1593.

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

Stenman, Virpi. "Finnish Forest Data-Based Metsään.fi-services." In Big Data in Bioeconomy, 309–19. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-71069-9_23.

Full text
Abstract:
AbstractThis chapter introduces the Finnish forest data ecosystem and its role in DataBio project pilots. In these DataBio pilots, the main objective is to improve the use of the Finnish forest resource data. The Finnish forest data provides a foundation for the forest big data-based online and e-services. The technical solution elements for the introduced DataBio pilots are based on standardized XML data sets, X-Road data transfer protocols, open forest data application programming interfaces (APIs) and crowdsourcing applications. The Metsään.fi-services including the open forest data APIs and Wuudis-mobile application are the key components for the customer’s user interface. In the end of the chapter, the pilot-specific business benefits and key performance indicators are decribed showing clear positive impacts of the pilots. At the end of this chapter, visions for the future of public online services are discussed.
APA, Harvard, Vancouver, ISO, and other styles
5

Korte, U. "Kryptographisches Application Programming Interface." In Sicherheitsschnittstellen — Konzepte, Anwendungen und Einsatzbeispiele, 157–65. Wiesbaden: Deutscher Universitätsverlag, 1994. http://dx.doi.org/10.1007/978-3-663-06728-3_12.

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

Sorgatz, Andreas. "Application Programming Interface (MAPI)." In Dynamic Modules, 53–111. Berlin, Heidelberg: Springer Berlin Heidelberg, 1999. http://dx.doi.org/10.1007/978-3-642-59995-8_6.

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

Aylward, Pete, Ken Jokol, Jamie Macdonald, Paul Prudence, Glen Rhodes, Robbie Shepherd, and Todd Yard. "Creating Interfaces with the Drawing API." In Flash MX Application & Interface Design, 25–44. Berkeley, CA: Apress, 2002. http://dx.doi.org/10.1007/978-1-4302-5217-7_2.

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

Tang, Bing, Zhigeng Pan, ZuoYan Lin, and Le Zheng. "PHI: Physics Application Programming Interface." In Lecture Notes in Computer Science, 390–93. Berlin, Heidelberg: Springer Berlin Heidelberg, 2006. http://dx.doi.org/10.1007/11872320_57.

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

Maier, K. "TeleTrusT-Security Application Programming Interface." In Sicherheitsschnittstellen — Konzepte, Anwendungen und Einsatzbeispiele, 167–78. Wiesbaden: Deutscher Universitätsverlag, 1994. http://dx.doi.org/10.1007/978-3-663-06728-3_13.

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

Garfinkel, Simson L., and Michael K. Mahoney. "Creating an Application Without Interface Builder." In NeXTSTEP™ PROGRAMMING, 87–119. New York, NY: Springer New York, 1993. http://dx.doi.org/10.1007/978-1-4613-9275-0_4.

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

Conference papers on the topic "API (Application Programming Interface)"

1

Juntunen, Jari, Mauri Kuorilehto, Mikko Kohvakka, Ville Kaseva, Marko Hannikainen, and Timo Hamalainen. "WSN API: Application Programming Interface for Wireless Sensor Networks." In 2006 IEEE 17th International Symposium on Personal, Indoor and Mobile Radio Communications. IEEE, 2006. http://dx.doi.org/10.1109/pimrc.2006.254073.

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

Lai, Chan-Yet, and Nordin Zakaria. "As sketchy as possible: Application Programming Interface (API) for sketch-based user interface." In 2010 International Symposium on Information Technology (ITSim 2010). IEEE, 2010. http://dx.doi.org/10.1109/itsim.2010.5561366.

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

Secil, Sezgin, Cansu Soyleyici, Metin Ozkan, Osman Parlaktuna, Helin Dutagaci, Kaya Turgut, and Mustafa Parlaktuna. "Design of an application programming interface (API) for commercial industrial robots." In 2016 IEEE 14th International Conference on Industrial Informatics (INDIN). IEEE, 2016. http://dx.doi.org/10.1109/indin.2016.7819163.

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

Joo, Sung-Hwan. "Assessment of Three Dimensional CAD Models Using CAD Application Programming Interface." In ASME 2018 International Mechanical Engineering Congress and Exposition. American Society of Mechanical Engineers, 2018. http://dx.doi.org/10.1115/imece2018-87776.

Full text
Abstract:
It has been always a challenge to grade and assess the students’ CAD (Computer-Aided Design) three-dimensional models in the class. The high number of the files and complexity of models make the task time-consuming and tedious many times. For example, even opening and closing each CAD file takes a lot of time. When hundreds of CAD models need to open and verified, it takes more than one hour to finish the task. The work has been done to simplify this task and make it easy using Commercial CAD software’s API (Application Programming Interface), which can be used to automate and customize the CAD software. The API contains hundreds of functions that you can call from Visual Basic for Applications (VBA), VB.NET, Visual C#, Visual C++ 6.0, and Visual C++/CLI. These functions provide direct access to CAD functionality such as opening a file, check the important physical properties of three-dimensional models. Custom API program has been programmed for the task. The custom program executes the internal commends in CAD software and retrieve the data you need from each CAD file automatically. The program opens the multiple CAD files in the folder and check each file’s physical properties and save the information in MS Excel for the review. The program checks the volume (w.r.t the given coordinates) in two standard units (English and S.I. Units), the creator of model (to prevent the plagiarism) and degrees of sketch. In this paper, the following topics will be discussed and presented. 1) The problem with manual grading and assessment, 2) History and background of API functionality in commercial CAD software, 3) Examples of simple source code for API usage, 4) Running example of the API program for the given task, 5) Comparison between manual assessment and automatic assessment using API in terms of spent time. 6) Future improvement with API program. Actual demonstration of the program will be given during the presentation.
APA, Harvard, Vancouver, ISO, and other styles
5

Konstantinos Domdouzis, Luis Rodriguez, Alan Hansen, and K.C Ting. "Development of an Application Programming Interface (API) for Biomass Feedstock Production Engineering." In 2010 Pittsburgh, Pennsylvania, June 20 - June 23, 2010. St. Joseph, MI: American Society of Agricultural and Biological Engineers, 2010. http://dx.doi.org/10.13031/2013.29978.

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

Canestrari, Niccolò, Dimitris Karkoulis, and Manuel Sánchez del Río. "SHADOW3-API: the application programming interface for the ray tracing code SHADOW." In SPIE Optical Engineering + Applications, edited by Manuel Sanchez del Rio and Oleg Chubar. SPIE, 2011. http://dx.doi.org/10.1117/12.893433.

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

Adhoni, Zameer Ahmed, Husam Al Hamad, Abdul Ahad Siddiqi, and Zaheer Ahmed Adhoni. "CBQ-API: A Cloud-Based Programming Interface for Qur'anic Applications." In 2013 International Conference on IT Convergence and Security (ICITCS). IEEE, 2013. http://dx.doi.org/10.1109/icitcs.2013.6717811.

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

Kamarulzaman, Ammar, Satyaraj Muniandy, Raja Zuhaili Aimran Raja Zainal Raffik, Mohd Fadzil Harun, and Asher Alexander. "Reducing Integrated Operation Project Deployment Complexity through Application Programming Interface API Enabled Software." In Abu Dhabi International Petroleum Exhibition & Conference. Society of Petroleum Engineers, 2019. http://dx.doi.org/10.2118/197165-ms.

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

Farchi, Eitan, Itai Segall, João M. Lourenço, and Diogo Sousa. "Using program closures to make an application programming interface (API) implementation thread safe." In the 2012 Workshop. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2338967.2336810.

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

Fang, Fang Clara. "Development of an Application Programming Interface (API) in Simulation to Evaluate Real-Time Signal Control." In Seventh International Conference of Chinese Transportation Professionals Congress (ICCTP). Reston, VA: American Society of Civil Engineers, 2008. http://dx.doi.org/10.1061/40952(317)42.

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

Reports on the topic "API (Application Programming Interface)"

1

Terada, M., and K. Fujimura. Voucher Trading System Application Programming Interface (VTS-API). RFC Editor, September 2005. http://dx.doi.org/10.17487/rfc4154.

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

Lee, C. H., A. Marin-Lafleche, and M. A. Smith. Development of Cross Section Library and Application Programming Interface (API). Office of Scientific and Technical Information (OSTI), April 2014. http://dx.doi.org/10.2172/1127296.

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

Williams, N., L. Johansson, S. Hartman, and S. Josefsson. Generic Security Service Application Programming Interface (GSS-API) Naming Extensions. RFC Editor, August 2012. http://dx.doi.org/10.17487/rfc6680.

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

Marlin, David, and Shane Thomas. Sensor Performance Evaluation for Battlefield Environments (SPEBE) C++ Application Programming Interface (API) Version 1.0. Fort Belvoir, VA: Defense Technical Information Center, January 2008. http://dx.doi.org/10.21236/ada476772.

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

Whelan, Paul. AE9/AP9/SPM Model Application Programming Interface, Version 1.00.000. Fort Belvoir, VA: Defense Technical Information Center, February 2014. http://dx.doi.org/10.21236/ada603361.

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

Komu, M., M. Bagnulo, and K. Slavov. Sockets Application Program Interface (API) for Multihoming Shim. Edited by S. Sugimoto. RFC Editor, July 2011. http://dx.doi.org/10.17487/rfc6316.

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

Stevens, W., M. Thomas, E. Nordmark, and T. Jinmei. Advanced Sockets Application Program Interface (API) for IPv6. RFC Editor, May 2003. http://dx.doi.org/10.17487/rfc3542.

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

Carpenter, B., W. Wang, and X. Gong. GeneRic Autonomic Signaling Protocol Application Program Interface (GRASP API). Edited by B. Liu. RFC Editor, May 2021. http://dx.doi.org/10.17487/rfc8991.

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

Kuehn, Jeffery A., Barbara Chapman, Anthony R. Curtis, Ricardo Mauricio, Swaroop Pophale, Ramachandra Nanjegowda, Amrita Banerjee, Karl Feind, Stephen W. Poole, and Lauren Smith. OpenSHMEM Application Programming Interface, v1.0 Final. Office of Scientific and Technical Information (OSTI), January 2012. http://dx.doi.org/10.2172/1050393.

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

Laros, James H.,, Suzanne M. Kelly, Kevin Pedretti, Ryan Grant, Stephen Lecler Olivier, Michael J. Levenhagen, David DeBonis, and Laros, James H.,. High Performance Computing - Power Application Programming Interface Specification. Office of Scientific and Technical Information (OSTI), March 2016. http://dx.doi.org/10.2172/1494356.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'API (Application Programming Interface)' 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