128,331 Hits in 7.3 sec

Characterizing the differences between pre- and post- release versions of software

Paul Luo Li, Ryan Kivett, Zhiyuan Zhan, Sung-eok Jeon, Nachiappan Nagappan, Brendan Murphy, Andrew J. Ko
2011 Proceeding of the 33rd international conference on Software engineering - ICSE '11  
We found each of these usage characteristics to differ between beta and post-release, and by adjusting for the differences, accuracy of field quality predictions for Windows improved by ~59%.  ...  However, little is known about how usage characteristics relate to field quality and how usage characteristics differ between beta and post-release.  ...  For Windows 7, the proportion of machines with these important usage characteristics differed significantly between the two pre-release versions and the post-release version.  ... 
doi:10.1145/1985793.1985894 dblp:conf/icse/LiKZJNMK11 fatcat:r5l4om5kzbbyjg7aaasshinuo4

Who? Where? What? Examining distributed development in two large open source projects

Christian Bird, N. Nagappan
2012 2012 9th IEEE Working Conference on Mining Software Repositories (MSR)  
We examine the distribution in each project's constituent subsystems and report the relationship of pre-and post-release defects with distribution levels.  ...  Both FIREFOX and ECLIPSE have been the subject of many studies and are ubiquitous in the areas of software development and internet usage respectively.  ...  We use this information along with the release dates of each version of ECLIPSE to categorize bugs into pre-release and post-release for each of the versions of 1 ECLIPSE released  ... 
doi:10.1109/msr.2012.6224286 dblp:conf/msr/BirdN12 fatcat:fwzjfe6zqjal7js3qzw5vigch4

Mining metrics to predict component failures

Nachiappan Nagappan, Thomas Ball, Andreas Zeller
2006 Proceeding of the 28th international conference on Software engineering - ICSE '06  
In an empirical study of the post-release defect history of five Microsoft software systems, we found that failure-prone software entities are statistically correlated with code complexity measures.  ...  Using principal component analysis on the code metrics, we built regression models that accurately predict the likelihood of post-release defects for new entities.  ...  We thank Melih Demir, Tom Zimmermann and many others for their helpful comments on earlier revisions of this paper.  ... 
doi:10.1145/1134285.1134349 dblp:conf/icse/NagappanBZ06 fatcat:5z7xsgy2tjhrtpdly6mpohbdwm

Which code construct metrics are symptoms of post release failures

Meiyappan Nagappan, Brendan Murphy, Mladen Vouk
2011 Proceeding of the 2nd international workshop on Emerging trends in software metrics - WETSoM '11  
with post release failures in these versions of Eclipse.  ...  In our comparison we identify which code construct metric, more often than the others, differs the most between these two classes of files.  ...  The first 2 of those metrics were how many pre-release and post release failures were there for each file.  ... 
doi:10.1145/1985374.1985389 dblp:conf/icse/NagappanMV11 fatcat:qckx4dkijbetvouneujk7nfsze

Product Strategies and Startups' Survival in Turbulent Industries: Evidence from the Security Software Industry

Andrea Fosfuri, Marco S. Giarratana
2004 Social Science Research Network  
Specifically, the paper aims to underscore the role played by post-entry product strategies, along with their interaction, beyond that of pre-entry conditions.  ...  Based on a sample of 270 startups that entered the Security Software Industry from 1989 till 1998, we find evidence that surviving entities are those that more aggressively adopt versioning and product  ...  In short, the recipe for startups' survival is a fine mix of pre-entry technological capabilities and stable post-entry product strategies.  ... 
doi:10.2139/ssrn.609801 fatcat:yrky4bh42zcn7bni3fsr3t4gdy

Exploring fault types, detection activities, and failure severity in an evolving safety-critical software system

Maggie Hamill, Katerina Goseva-Popstojanova
2014 Software quality journal  
Analysis and testing activities detected the majority of failures caused by each fault type. (2) The distributions of fault types differed for pre-release and post-release failures. (3) The percentage  ...  Furthermore, it explores the associations among these attributes and the trends within releases (i.e., pre-release and post-release) and across releases.  ...  Acknowledgements Any opinions, findings, and conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of the NASA personnel and the funding  ... 
doi:10.1007/s11219-014-9235-5 fatcat:jjjweqnc3vcb3dgcwwkdwyqv3a

The Secret Life of Patches: A Firefox Case Study

Olga Baysal, Oleksii Kononenko, Reid Holmes, Michael W. Godfrey
2012 2012 19th Working Conference on Reverse Engineering  
We contrast the lifecycle of a patch in preand post-rapid release development.  ...  The goal of the code review process is to assess the quality of source code modifications (submitted as patches) before they are committed to a project's version control repository.  ...  ACKNOWLEDGEMENT We wish to thank Martin Best and David Mandelin from Mozilla for their feedback on the paper.  ... 
doi:10.1109/wcre.2012.54 dblp:conf/wcre/BaysalKHG12 fatcat:fuxfcteozzgvjfabub6udxpnje

Challenges with applying vulnerability prediction models

Patrick Morrison, Kim Herzig, Brendan Murphy, Laurie Williams
2015 Proceedings of the 2015 Symposium and Bootcamp on the Science of Security - HotSoS '15  
Seeking to understand this discrepancy, we replicated a VPM for two releases of the Windows Operating System, varying model granularity and statistical learners.  ...  However, binaries often exceed 1 million lines of code, too large to practically inspect, and engineers expressed preference for source file level predictions.  ...  The Tools for Software Engineers team provided significant support, especially Jacek Czerwonka, Michaela Greiler, and John Smyth.  ... 
doi:10.1145/2746194.2746198 dblp:conf/hotsos/MorrisonHMW15 fatcat:5l2rkrknyjg4bc2ctjeinhv36e

An empirical study of software change: origin, acceptance rate, and functionality vs. quality attributes

P. Mohagheghi, R. Conradi
2004 Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04.  
We did not identify any significant difference between the change-proneness of reused and non-reused components.  ...  The results show that earlier releases of the system are no longer evolved. Perfective changes to functionality and quality attributes are most common.  ...  Note that CRs may be issued pre-or post-delivery.  ... 
doi:10.1109/isese.2004.1334889 fatcat:vyjygr3z3zathnlrenerq4gjym

Skeletal myocytes are a source of interleukin-6 mRNA expression and protein release during contraction: evidence of fiber type specificity

2004 The FASEB Journal  
POST) and glycogen-dependent fluorescence (LOW vs. HIGH) of IL-6 protein were quantitated using Metamorph software. Total IL-6 protein was elevated from PRE to POST exercise (P<0.05).  ...  Muscle biopsy samples were collected from seven males before (PRE) and after (POST) completing 120 min of continuous bicycle ergometry.  ...  Simon Potocnik from the Microvascular Research Group, RMIT University, for expert advice and assistance in the detection and quantitation of the IL-6 protein.  ... 
doi:10.1096/fj.03-1259fje pmid:15059966 fatcat:wlwqqjvrqvczbi26xlqhgq2dvm

A Second Replicated Quantitative Analysis of Fault Distributions in Complex Software Systems

Tihana Galinac Grbac, Per Runeson, Darko Huljenic
2013 IEEE Transactions on Software Engineering  
We conducted a literal replication, collecting defect data from five consecutive releases of a large software system in the telecommunications domain, and conducted the same analysis as in the original  ...  Size measures are not useful as predictors of fault proneness, while fault densities are of the same order of magnitude across releases and contexts. Conclusions.  ...  Conclusion We report a second replication study of Fenton and Ohlsson's study from the late 1990's [10] .  ... 
doi:10.1109/tse.2012.46 fatcat:udnuysmibvazhjgzmfhgiu5v7q

Predicting risk of pre-release code changes with Checkinmentor

Alexander Tarvo, Nachiappan Nagappan, Thomas Zimmermann
2013 2013 IEEE 24th International Symposium on Software Reliability Engineering (ISSRE)  
Such post-release failures are costly to fix and have negative impact on the reputation of the released software. In this paper we propose a methodology for early detection of faulty code changes.  ...  Code defects introduced during the development of the software system can result in failures after its release.  ...  INTRODUCTION Faulty changes, made during the development of the software system, must be detected and fixed before the system is released. Otherwise they can cause post-release failures.  ... 
doi:10.1109/issre.2013.6698912 dblp:conf/issre/TarvoNZ13 fatcat:gf4ew3tvkzgk7mlqv6266h72tq

A deeper look into bug fixes

Mauricio Soto, Ferdian Thung, Chu-Pan Wong, Claire Le Goues, David Lo
2016 Proceedings of the 13th International Workshop on Mining Software Repositories - MSR '16  
However, Java and C are very different languages, and Java should be studied to inform the construction of repair approaches to target it.  ...  We make observations that can be leveraged to guide high quality automatic software repair to target Java specifically, including common and uncommon statement modifications in human patches and the applicability  ...  We discard signatures that appear both in pre-and post-fix versions, and then identify methods with the same name and number of parameters, but different signatures between versions.  ... 
doi:10.1145/2901739.2903495 dblp:conf/msr/SotoTWGL16 fatcat:am5rqup6kzc4xoo27woh7fxe2y

Distributed software development in an offshore outsourcing project: A case study of source code evolution and quality

Ronald Jabangwe, Darja Šmite, Emil Hessbo
2016 Information and Software Technology  
Only post-release defects are used as a proxy for external quality due to unreliable defect data found pre-release such as those reported during integration.  ...  Results: The results suggest that practices that can be grouped into product, people, and process categories can help ensure post-release quality.  ...  This will give a better reflection of the quality of the software pre-and post-release.  ... 
doi:10.1016/j.infsof.2015.12.005 fatcat:ihjyuixljffifbvetjfe7skaku

Assessing climate model software quality: a defect density analysis of three models

J. Pipitone, S. Easterbrook
2012 Geoscientific Model Development Discussions  
We performed an analysis of defect reports and defect fixes in several versions of leading global climate models by collecting defect data from bug tracking systems and version control repository comments  ...  A climate model is an executable theory of the climate; the model encapsulates climatological theories in software so that they can be simulated and their implications investigated.  ...  We also thank Tom Clune and Luis Kornblueh for their comments on an earlier version of this paper. Funding was provided by NSERC. Edited by: R. Redler  ... 
doi:10.5194/gmdd-5-347-2012 fatcat:bob3gnpw2fclllajeekegww4gq
« Previous Showing results 1 — 15 out of 128,331 results