Botched Releases: Do we Need to Roll Back? Empirical Study on a Commercial Web App

TitreBotched Releases: Do we Need to Roll Back? Empirical Study on a Commercial Web App
Publication TypeConference Paper
Year of Publication2016
AuthorsKerzazi, N, Adams, B
Conference Name2016 IEEE 23RD INTERNATIONAL CONFERENCE ON SOFTWARE ANALYSIS, EVOLUTION, AND REENGINEERING (SANER), VOL 1
PublisherIEEE; IEEE Comp Soc; IPA; Reengineering Forum; Informat Proc Soc Japan, Special Interest Grp Software Engn; Japan Soc Software Sci & Technol, Special Interest Grp Fdn Software Engn; Osaka Univ, Grad Sch Informat Sci & Technol; Mitsubishi Elect; Microsoft;
ISBN Number978-1-5090-1855-0
Abstract

Few minutes after a web-based software release, the release team might encounter log traces showing the new system crashing, hanging, or having poor performance. This is the start of the most nerve-wrecking moments of a product's release cycle, i.e., should one run the risk of not doing anything and users losing precious data, or of prematurely engaging the tedious (and costly) roll-back procedure towards the previous release? Thus far, only little attention has been paid by researchers to these so-called ``botched releases{''}, partly because of lack of release log data. This paper studies 345 releases of a large e-commerce web app over a period of 1.5 years, in which we identified 17 recurrent root causes of botched releases, classified into four major categories. We then build explanatory models to understand which root causes are the most important, and to explore the factors leading to botched releases.

DOI10.1109/SANER.2016.114
Revues: 

Partenaires

Localisation


Location map

Suivez-nous sur

  

Contactez-nous

ENSIAS

Avenue Mohammed Ben Abdallah Regragui, Madinat Al Irfane, BP 713, Agdal Rabat, Maroc

Résultat de recherche d'images pour "icone fax" Télécopie : (+212) 5 37 77 72 30

    Compteur de visiteurs:348,109
    Education - This is a contributing Drupal Theme
    Design by WeebPal.