How Java APIs break - An empirical study
Identifikátory výsledku
Kód výsledku v IS VaVaI
<a href="https://www.isvavai.cz/riv?ss=detail&h=RIV%2F49777513%3A23520%2F15%3A43925695" target="_blank" >RIV/49777513:23520/15:43925695 - isvavai.cz</a>
Výsledek na webu
<a href="http://dx.doi.org/10.1016/j.infsof.2015.02.014" target="_blank" >http://dx.doi.org/10.1016/j.infsof.2015.02.014</a>
DOI - Digital Object Identifier
<a href="http://dx.doi.org/10.1016/j.infsof.2015.02.014" target="_blank" >10.1016/j.infsof.2015.02.014</a>
Alternativní jazyky
Jazyk výsledku
angličtina
Název v původním jazyce
How Java APIs break - An empirical study
Popis výsledku v původním jazyce
Context It has become common practice to build programs by using libraries. While the benefits of reuse are well known, an often overlooked risk are system runtime failures due to API changes in libraries that evolve independently. Traditionally, the consistency between a program and the libraries it uses is checked at build time when the entire system is compiled and tested. However, the trend towards partially upgrading systems by redeploying only evolved library versions results in situations where these crucial verification steps are skipped. For Java programs, partial upgrades create additional interesting problems as the compiler and the virtual machine use different rule sets to enforce contracts between the providers and the consumers of APIs.Objective We have studied the extent of the problem in real world programs. We were interested in two aspects: the compatibility of API changes as libraries evolve, and the impact this has on programs using these libraries. Method This st
Název v anglickém jazyce
How Java APIs break - An empirical study
Popis výsledku anglicky
Context It has become common practice to build programs by using libraries. While the benefits of reuse are well known, an often overlooked risk are system runtime failures due to API changes in libraries that evolve independently. Traditionally, the consistency between a program and the libraries it uses is checked at build time when the entire system is compiled and tested. However, the trend towards partially upgrading systems by redeploying only evolved library versions results in situations where these crucial verification steps are skipped. For Java programs, partial upgrades create additional interesting problems as the compiler and the virtual machine use different rule sets to enforce contracts between the providers and the consumers of APIs.Objective We have studied the extent of the problem in real world programs. We were interested in two aspects: the compatibility of API changes as libraries evolve, and the impact this has on programs using these libraries. Method This st
Klasifikace
Druh
J<sub>x</sub> - Nezařazeno - Článek v odborném periodiku (Jimp, Jsc a Jost)
CEP obor
IN - Informatika
OECD FORD obor
—
Návaznosti výsledku
Projekt
<a href="/cs/project/ED1.1.00%2F02.0090" target="_blank" >ED1.1.00/02.0090: NTIS - Nové technologie pro informační společnost</a><br>
Návaznosti
P - Projekt vyzkumu a vyvoje financovany z verejnych zdroju (s odkazem do CEP)
Ostatní
Rok uplatnění
2015
Kód důvěrnosti údajů
S - Úplné a pravdivé údaje o projektu nepodléhají ochraně podle zvláštních právních předpisů
Údaje specifické pro druh výsledku
Název periodika
Information and Software Technology
ISSN
0950-5849
e-ISSN
—
Svazek periodika
65
Číslo periodika v rámci svazku
2
Stát vydavatele periodika
GB - Spojené království Velké Británie a Severního Irska
Počet stran výsledku
18
Strana od-do
129-146
Kód UT WoS článku
000356110100009
EID výsledku v databázi Scopus
—