All

What are you looking for?

All
Projects
Results
Organizations

Quick search

  • Projects supported by TA ČR
  • Excellent projects
  • Projects with the highest public support
  • Current projects

Smart search

  • That is how I find a specific +word
  • That is how I leave the -word out of the results
  • “That is how I can find the whole phrase”

How Java APIs break - An empirical study

The result's identifiers

  • Result code in 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>

  • Result on the web

    <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>

Alternative languages

  • Result language

    angličtina

  • Original language name

    How Java APIs break - An empirical study

  • Original language description

    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

  • Czech name

  • Czech description

Classification

  • Type

    J<sub>x</sub> - Unclassified - Peer-reviewed scientific article (Jimp, Jsc and Jost)

  • CEP classification

    IN - Informatics

  • OECD FORD branch

Result continuities

  • Project

    <a href="/en/project/ED1.1.00%2F02.0090" target="_blank" >ED1.1.00/02.0090: NTIS - New Technologies for Information Society</a><br>

  • Continuities

    P - Projekt vyzkumu a vyvoje financovany z verejnych zdroju (s odkazem do CEP)

Others

  • Publication year

    2015

  • Confidentiality

    S - Úplné a pravdivé údaje o projektu nepodléhají ochraně podle zvláštních právních předpisů

Data specific for result type

  • Name of the periodical

    Information and Software Technology

  • ISSN

    0950-5849

  • e-ISSN

  • Volume of the periodical

    65

  • Issue of the periodical within the volume

    2

  • Country of publishing house

    GB - UNITED KINGDOM

  • Number of pages

    18

  • Pages from-to

    129-146

  • UT code for WoS article

    000356110100009

  • EID of the result in the Scopus database