Table of Contents

• Half-century of unix: history, preservation, and lessons learnedDiomidis Spinellis. 1 [doi]
• An empirical study on Android-related vulnerabilitiesMario Linares Vásquez, Gabriele Bavota, Camilo Escobar-Velasquez. 2-13 [doi]
• Understanding the origins of mobile app vulnerabilities: a large-scale measurement study of free and paid appsTakuya Watanabe, Mitsuaki Akiyama, Fumihiro Kanei, Eitaro Shioji, Yuta Takata, Bo Sun, Yuta Ishii, Toshiki Shibahara, Takeshi Yagi, Tatsuya Mori. 14-24 [doi]
• Developer mistakes in writing Android manifests: an empirical study of configuration errorsAjay Kumar Jha, Sunghee Lee, Woo Jin Lee. 25-36 [doi]
• How do apps evolve in their permission requests?: a preliminary studyPaolo Calciati, Alessandra Gorla. 37-41 [doi]
• A study on the energy consumption of Android app development approachesWellington Oliveira, Renato Oliveira, Fernando Castor. 42-52 [doi]
• Candoia: a platform for building and sharing mining software repositories tools as appsNitin M. Tiwari, Ganesha Upadhyaya, Hoan Anh Nguyen, Hridesh Rajan. 53-63 [doi]
• Analyzing program dependencies in Java EE applicationsAnas Shatnawi, Hafedh Mili, Ghizlane El-Boussaidi, Anis Boubaker, Yann-Gaël Guéhéneuc, Naouel Moha, Jean Privat, Manel Abdellatif. 64-74 [doi]
• Mining social web service repositories for social relationships to aid service discoveryAlejandro Corbellini, Daniela Godoy, Cristian Mateos, Alejandro Zunino, Ignacio Lizarralde. 75-79 [doi]
• Who you gonna call?: analyzing web requests in Android applicationsMarianna Rapoport, Philippe Suter, Erik Wittern, Ondrej Lhoták, Julian Dolby. 80-90 [doi]
• Extracting code segments and their descriptions from research articlesPreetha Chatterjee, Benjamin Gause, Hunter Hedinger, Lori L. Pollock. 91-101 [doi]
• Structure and evolution of package dependency networksRiivo Kikas, Georgios Gousios, Marlon Dumas, Dietmar Pfahl. 102-112 [doi]
• Spencer: interactive heap analysis for the massesStephan Brandauer, Tobias Wrigstad. 113-123 [doi]
• Predicting likelihood of requirement implementation within the planned iteration: an empirical study at IBMAli Dehghan, Adam Neal, Kelly Blincoe, Johan Linåker, Daniela E. Damian. 124-134 [doi]
• The impact of using regression models to build defect classifiersGopi Krishnan Rajbahadur, Shaowei Wang, Yasutaka Kamei, Ahmed E. Hassan. 135-145 [doi]
• A large-scale study of the impact of feature selection techniques on defect classification modelsBaljinder Ghotra, Shane McIntosh, Ahmed E. Hassan. 146-157 [doi]
• SpreadCluster: recovering versioned spreadsheets through similarity-based clusteringLiang Xu, Wensheng Dou, Chushu Gao, Jie Wang, Jun Wei, Hua Zhong, Tao Huang. 158-169 [doi]
• Who will leave the company?: a large-scale industry study of developer turnover by mining monthly work reportLingfeng Bao, Zhenchang Xing, Xin Xia, David Lo, Shanping Li. 170-181 [doi]
• Concept-based classification of software defect reportsSangameshwar Patil. 182-186 [doi]
• Choosing an NLP library for analyzing software documentation: a systematic literature review and a series of experimentsFouad Nasser A. Al Omran, Christoph Treude. 187-197 [doi]
• Bootstrapping a lexicon for emotional arousal in software engineeringMika V. Mäntylä, Nicole Novielli, Filippo Lanubile, Maëlick Claes, Miikka Kuutila. 198-202 [doi]
• Leveraging automated sentiment analysis in software engineeringMd Rakibul Islam, Minhaz F. Zibran. 203-214 [doi]
• Predicting usefulness of code review comments using textual features and developer experienceMohammad Masudur Rahman 0001, Chanchal K. Roy, Raula G. Kula. 215-226 [doi]
• Classifying code comments in Java open-source software systemsLuca Pascarella, Alberto Bacchelli. 227-237 [doi]
• Using Q&A websites as a method for assessing systematic reviewsBruno Cartaxo, Gustavo Pinto, Danilo Monteiro Ribeiro, Fernando Kamei, Ronnie E. S. Santos, Fabio Q. B. da Silva, Sérgio Soares. 238-242 [doi]
• Abnormal working hours: effect of rapid releases and implications to work contentMaëlick Claes, Mika Mäntylä, Miikka Kuutila, Bram Adams. 243-247 [doi]
• Mining change histories for unknown systematic editsTim Molderez, Reinout Stevens, Coen De Roover. 248-256 [doi]
• Source file set search for clone-and-own reuse analysisTakashi Ishio, Yusuke Sakaguchi, Kaoru Ito, Katsuro Inoue. 257-268 [doi]
• RefDiff: detecting refactorings in version historiesDanilo Silva, Marco Tulio Valente. 269-279 [doi]
• Stack overflow in github: any snippets there?Di Yang, Pedro Martins, Vaibhav Saini, Cristina V. Lopes. 280-290 [doi]
• Some from here, some from there: cross-project code reuse in GitHubMohammad Gharehyazie, Baishakhi Ray, Vladimir Filkov. 291-301 [doi]
• Exception evolution in long-lived Java systemsHaidar Osman, Andrei Chis, Claudio Corrodi, Mohammad Ghafari, Oscar Nierstrasz. 302-311 [doi]
• Do not trust build results at face value: an empirical study of 30 million CPAN buildsMahdis Zolfagharinia, Bram Adams, Yann-Gaël Guéhéneuc. 312-322 [doi]
• An empirical analysis of the docker container ecosystem on GitHubJürgen Cito, Gerald Schermann, John Erik Wittern, Philipp Leitner, Sali Zumberi, Harald C. Gall. 323-333 [doi]
• How open source projects use static code analysis tools in continuous integration pipelinesFiorella Zampetti, Simone Scalabrino, Rocco Oliveto, Gerardo Canfora, Massimiliano Di Penta. 334-344 [doi]
• An empirical analysis of build failures in the continuous integration workflows of Java-based open-source softwareThomas Rausch, Waldemar Hummer, Philipp Leitner, Stefan Schulte 0002. 345-355 [doi]
• Oops, my tests broke the build: an explorative analysis of Travis CI with GitHubMoritz Beller, Georgios Gousios, Andy Zaidman. 356-367 [doi]
• Extracting build changes with BuildDiffChristian Macho, Shane McIntosh, Martin Pinzger. 368-378 [doi]
• An exploratory study on assessing the impact of environment variations on the results of load testsRuoyu Gao, Zhen Ming (Jack) Jiang. 379-390 [doi]
• A large-scale study on the usage of testing patterns that address maintainability attributes: patterns for ease of modification, diagnoses, and comprehensionDanielle Gonzalez, Joanna C. S. Santos, Andrew Popovich, Mehdi Mirakhorli, Meiyappan Nagappan. 391-401 [doi]
• To mock or not to mock?: an empirical study on mocking practicesDavide Spadini, Maurício Aniche, Magiel Bruntink, Alberto Bacchelli. 402-412 [doi]
• Bug characteristics in blockchain systems: a large-scale empirical studyZhi-Yuan Wan, David Lo, Xin Xia, Liang Cai. 413-424 [doi]
• Euphony: harmonious unification of cacophonous anti-virus vendor labels for Android malwareMédéric Hurier, Guillermo Suarez-Tangil, Santanu Kumar Dash, Tegawendé F. Bissyandé, Yves Le Traon, Jacques Klein, Lorenzo Cavallaro. 425-435 [doi]
• Rationale in development chat messages: an exploratory studyRana Alkadhi, Teodora Lata, Emitza Guzman, Bernd Bruegge. 436-446 [doi]
• TravisTorrent: synthesizing Travis CI and GitHub for full-stack research on continuous integrationMoritz Beller, Georgios Gousios, Andy Zaidman. 447-450 [doi]
• On the differences between unit and integration testing in the travistorrent datasetGerardo Orellana, Gulsher Laghari, Alessandro Murgia, Serge Demeyer. 451-454 [doi]
• Cost-effective build outcome prediction using cascaded classifiersAnsong Ni, Ming Li. 455-458 [doi]
• Sentiment analysis of Travis CI buildsRodrigo Souza, Bruno Silva. 459-462 [doi]
• A time series analysis of TravisTorrent builds: to everything there is a seasonAbigail Atchison, Christina Berardi, Natalie Best, Elizabeth Stevens, Erik Linstead. 463-466 [doi]
• Insights into continuous integration build failuresMd Rakibul Islam, Minhaz F. Zibran. 467-470 [doi]
• An empirical study of the personnel overhead of continuous integrationMarco Manglaviti, Eduardo Coronado-Montoya, Keheliya Gallaba, Shane McIntosh. 471-474 [doi]
• How does contributors' involvement influence the build status of an open-source software project?Marcel Rebouças, Renato O. Santos, Gustavo Pinto, Fernando Castor. 475-478 [doi]
• On the interplay between non-functional requirements and builds on continuous integrationKlérisson V. R. Paixão, Crícia Z. Felício, Fernanda Madeiral Delfim, Marcelo de Almeida Maia. 479-482 [doi]
• Analyzing the impact of social attributes on commit integration successMauricio Soto, Zack Coker, Claire Le Goues. 483-486 [doi]
• Built to last or built too fast?: evaluating prediction models for build timesEkaba Bisong, Eric Tran, Olga Baysal. 487-490 [doi]
• The impact of the adoption of continuous integration on developer attraction and retentionYash Gupta, Yusaira Khan, Keheliya Gallaba, Shane McIntosh. 491-494 [doi]
• An empirical study of activity, popularity, size, testing, and stability in continuous integrationAakash Gautam, Saket Vishwasrao, Francisco Servant. 495-498 [doi]
• Impact of continuous integration on code reviewsMohammad Masudur Rahman 0001, Chanchal K. Roy. 499-502 [doi]
• Prevalence of botched code integrationsWard Muylaert, Coen De Roover. 503-506 [doi]
• Software evolution and quality data from controlled, multiple, industrial case studiesAiko Yamashita, S. Amirhossein Abtahizadeh, Foutse Khomh, Yann-Gaël Guéhéneuc. 507-510 [doi]
• A dataset of scratch programs: scraped, shaped and scoredEfthimia Aivaloglou, Felienne Hermans, Jesús Moreno-León, Gregorio Robles. 511-514 [doi]
• Continuous defect prediction: the idea and a related datasetLech Madeyski, Marcin Kawalerowicz. 515-518 [doi]
• An extensive dataset of UML models in GitHubGregorio Robles, Truong Ho-Quang, Regina Hebig, Michel R. V. Chaudron, Miguel Angel Fernández. 519-522 [doi]
• A dataset for dynamic discovery of semantic changes in version controlled software historiesChenguang Zhu, Yi Li, Julia Rubin, Marsha Chechik. 523-526 [doi]
• Rediscovery datasets: connecting duplicate reportsMefta Sadat, Ayse Basar Bener, Andriy V. Miranskyy. 527-530 [doi]
• A data set of OCL expressions on GitHubJeroen Noten, Josh Mengerink, Alexander Serebrenik. 531-534 [doi]