Table of Contents

• Is continuous adoption in software engineering achievable and desirable?Gail C. Murphy. 8 [doi]
• CloudBuild: Microsoft's distributed and caching build serviceHamed Esfahani, Jonas Fietz, Qi Ke, Alexei Kolomiets, Erica Lan, Erik Mavrinac, Wolfram Schulte, Newton Sanches, Srikanth Kandula. 11-20 [doi]
• Continuous deployment at Facebook and OANDATony Savor, Mitchell Douglas, Michael Gentili, Laurie Williams, Kent Beck, Michael Stumm. 21-30 [doi]
• An empirically developed method to aid decisions on architectural technical debt refactoring: AnaConDebtAntonio Martini, Jan Bosch. 31-40 [doi]
• Trustworthiness in enterprise crowdsourcing: a taxonomy & evidence from dataAnurag Dwarakanath, N. C. Shrikanth, Kumar Abhinav, Alex Kass. 41-50 [doi]
• Practical programming, validation and verification with finite-state machines: a library and its industrial applicationPaulo Salem. 51-60 [doi]
• Battles with false positives in static analysis of JavaScript web applications in the wildJoonyoung Park, Inho Lim, Sukyoung Ryu. 61-70 [doi]
• Detecting problems in the database access code of large scale systems: an industrial experience reportTse-Hsun Chen, Weiyi Shang, Ahmed E. Hassan, Mohamed N. Nasser, Parminder Flora. 71-80 [doi]
• Engineering the servo web browser engine using RustBrian Anderson, Lars Bergstrom, Manish Goregaokar, Josh Matthews, Keegan McAllister, Jack Moffitt, Simon Sapin. 81-89 [doi]
• Chaos engineering panelLorin Hochstein, Casey Rosenthal. 90-91 [doi]
• The bones of the system: a case study of logging and telemetry at MicrosoftTitus Barik, Robert DeLine, Steven M. Drucker, Danyel Fisher. 92-101 [doi]
• Log clustering based problem identification for online service systemsQingwei Lin, Hongyu Zhang, Jian-Guang Lou, Yu Zhang, Xuewei Chen. 102-111 [doi]
• Use runtime verification to improve the quality of medical care practiceYu Jiang, Han Liu, Hui Kong, Rui Wang, Mohammad Hosseini, Jia-Guang Sun, Lui Sha. 112-121 [doi]
• Assessing the usefulness of a requirements monitoring tool: a study involving industrial software engineersRick Rabiser, Michael Vierhauser, Paul Grünbacher. 122-131 [doi]
• Lessons learned in aligning data and model evolution in collaborative information systemsThomas Reschenhofer, Manoj Bhat, Adrian Hernandez-Mendez, Florian Matthes. 132-141 [doi]
• Mentoring trajectories in an evolving agile workplaceShreya Kumar, Charles Wallace, Michael Young. 142-151 [doi]
• Visualizing the effects of requirements evolutionShinobu Saito, Yukako Iimura, Hirokazu Tashiro, Aaron K. Massey, Annie I. Antón. 152-161 [doi]
• VEnron: a versioned spreadsheet corpus and related evolution analysisWensheng Dou, Liang Xu, Shing-Chi Cheung, Chushu Gao, Jun Wei, Tao Huang. 162-171 [doi]
• System testing of repository-style software: an experience reportPaolo Salvaneschi. 172-181 [doi]
• Enhancing test case prioritization in an industrial setting with resource awareness and multi-objective searchShuai Wang, Shaukat Ali, Tao Yue, Øyvind Bakkeli, Marius Liaaen. 182-191 [doi]
• Integrating automatic backward error recovery in asynchronous rich clientsManuel Quintela-Pumares, Bruno Cabral, Daniel Fernández Lanvin, Alberto Manuel Fernández Álvarez. 192-201 [doi]
• Opaque service virtualisation: a practical tool for emulating endpoint systemsSteven Versteeg, Miao Du, Jean-Guy Schneider, John Grundy, Jun Han, Menka Goyal. 202-211 [doi]
• A study of the quality-impacting practices of modern code review at Sony mobileJunji Shimagaki, Yasutaka Kamei, Shane McIntosh, Ahmed E. Hassan, Naoyasu Ubayashi. 212-221 [doi]
• CoRReCT: code reviewer recommendation in GitHub based on cross-project and technology experienceMohammad Masudur Rahman, Chanchal K. Roy, Jason A. Collins. 222-231 [doi]
• How do free/open source developers pick their tools?: a Delphi study of the Debian projectMartin F. Krafft, Klaas-Jan Stol, Brian Fitzgerald. 232-241 [doi]
• Observations on knowledge transfer of professional software developers during pair programmingFranz Zieris, Lutz Prechelt. 242-250 [doi]
• Assessing the process of an Eastern European software SME using systemic analysis, GQM, and reliability growth models: a case studyVladimir Ivanov, Manuel Mazzara, Witold Pedrycz, Alberto Sillitti, Giancarlo Succi. 251-259 [doi]
• Model driven development of business applications: a practitioner's perspectiveVinay Kulkarni. 260-269 [doi]
• Industry application of continuous integration modeling: a multiple-case studyDaniel Ståhl, Jan Bosch. 270-279 [doi]
• What went right and what went wrong: an analysis of 155 postmortems from game developmentMichael Washburn Jr., Pavithra Sathiyanarayanan, Meiyappan Nagappan, Thomas Zimmermann 0001, Christian Bird. 280-289 [doi]
• Learning Agile software development in high school: an investigationMarcello Missiroli, Daniel Russo, Paolo Ciancarini. 293-302 [doi]
• Teaching Agile: addressing the conflict between project delivery and application of Agile methodsJan-Philipp Steghöfer, Eric Knauss, Emil Alégroth, Imed Hammouda, Håkan Burden, Morgan Ericsson. 303-312 [doi]
• How surveys, tutors, and software help to assess Scrum adoption in a classroom software engineering projectChristoph Matthies, Thomas Kowark, Keven Richly, Matthias Uflacker, Hasso Plattner. 313-322 [doi]
• Metrics in Agile project coursesLukas Alperowitz, Dora Dzvonyar, Bernd Bruegge. 323-326 [doi]
• Smart decisions: an architectural design gameHumberto Cervantes, Serge Haziyev, Olha Hrytsay, Rick Kazman. 327-335 [doi]
• Reflections on applying constructive alignment with formative feedback for teaching introductory programming and software architectureAndrew Cain, Muhammad Ali Babar. 336-345 [doi]
• Software security education at scaleChristopher Theisen, Laurie Williams, Kevin Oliver, Emerson R. Murphy-Hill. 346-355 [doi]
• What makes teaching software architecture difficult?Matthias Galster, Samuil Angelov. 356-359 [doi]
• Collaborative software engineering education between college seniors and blind high school studentsCollin McMillan, Amanda Rodda-Tyler. 360-363 [doi]
• Can software engineering students program defect-free?: an educational approachGuoping Rong, He Zhang, Qi Shan, Dong Shao. 364-373 [doi]
• Impact of CS programs on the quality of test cases generation: an empirical studyOmar S. Gómez, Sira Vegas, Natalia Juristo. 374-383 [doi]
• Teaching code review management using branch based workflowsStephan Krusche, Mjellma Berisha, Bernd Bruegge. 384-393 [doi]
• Let's verify Linux: accelerated learning of analytical reasoning through automation and collaborationSuresh Kothari, Ahmed Tamrawi, Jeremias Sauceda, Jon Mathews. 394-403 [doi]
• Enriching traditional software engineering curricula with software project management knowledgeAna María Moreno, Maria Isabel Sánchez Segura, Fuensanta Medina-Domínguez, Lawrence Peters, Jonathan Araujo. 404-411 [doi]
• When teams go crazy: an environment to experience group dynamics in software project management coursesMarco Kuhrmann, Jürgen Münch. 412-421 [doi]
• Student experiences using GitHub in software engineering courses: a case studyJoseph Feliciano, Margaret-Anne D. Storey, Alexey Zagalsky. 422-431 [doi]
• What communication tools students use in software projects and how do different tools suit different parts of project work?Otto Seppälä, Tapio Auvinen, Ville Karavirta, Arto Vihavainen, Petri Ihantola. 432-435 [doi]
• HoliCoW: automatically breaking team-based software projects to motivate student testingPeng Zhang, Jules White, Douglas C. Schmidt. 436-439 [doi]
• Teaching a global software development course: student experiences using onsite exercise simulationJouni Lappalainen, Nirnaya Tripathi, Jouni Similä. 440-450 [doi]
• VisAr3D: an innovative 3D visualization of UML modelsClaudia Susie C. Rodrigues, Cláudia Maria Lima Werner, Luiz Landau. 451-460 [doi]
• Facing the challenges of teaching requirements engineeringRoxana Lisette Quintanilla Portugal, Priscila Engiel, Joanna Pivatelli, Julio Cesar Sampaio do Prado Leite. 461-470 [doi]
• Teaching university students Kanban with a collaborative board gameVille T. Heikkilä, Maria Paasivaara, Casper Lassenius. 471-480 [doi]
• SolMiner: mining distinct solutions in programsLannan Luo, Qiang Zeng. 481-490 [doi]
• STAGE: a software tool for automatic grading of testing exercises: case study paperSebastian Pape, Julian Flake, Andreas Beckmann, Jan Jürjens. 491-500 [doi]
• Measuring code behavioral similarity for programming and software engineering educationSihan Li, Xusheng Xiao, Blake Bassett, Tao Xie, Nikolai Tillmann. 501-510 [doi]
• Engaging software estimation education using LEGOs: a case studyLinda Laird, Ye Yang. 511-517 [doi]
• Software engineering and policyAnthony Finkelstein. 521-522 [doi]
• Software energy profiling: comparing releases of a software productErik A. Jagroep, Jan Martijn van der Werf, Sjaak Brinkkemper, Giuseppe Procaccianti, Patricia Lago, Leen Blom, Rob van Vliet. 523-532 [doi]
• Sustainability design in requirements engineering: state of practiceRuzanna Chitchyan, Christoph Becker, Stefanie Betz, Leticia Duboc, Birgit Penzenstadler, Norbert Seyff, Colin C. Venters. 533-542 [doi]
• Sustainability debt: a portfolio-based approach for evaluating sustainability requirements in architecturesBendra Ojameruaye, Rami Bahsoon, Leticia Duboc. 543-552 [doi]
• Values-first SE: research principles in practiceMaria Angela Ferrario, William Simm, Stephen Forshaw, Adrian Gradinar, Marcia Tavares Smith, Ian Smith. 553-562 [doi]
• A guided tour of the legal implications of software cloningPaolo Ciancarini, Daniel Russo, Alberto Sillitti, Giancarlo Succi. 563-572 [doi]
• Engineering software assemblies for participatory democracy: the participatory budgeting use caseJames Holston, Valérie Issarny, Cristhian Parra. 573-582 [doi]
• SimCoTest: a test suite generation tool for simulink/stateflow controllersReza Matinnejad, Shiva Nejati, Lionel C. Briand, Thomas Bruckmann. 585-588 [doi]
• SMACK software verification toolchainMontgomery Carter, Shaobo He, Jonathan Whitaker, Zvonimir Rakamaric, Michael Emmi. 589-592 [doi]
• FOREPOST: a tool for detecting performance problems with feedback-driven learning software testingQi Luo, Denys Poshyvanyk, Aswathy Nair, Mark Grechanik. 593-596 [doi]
• SourcererCC and SourcererCC-I: tools to detect clones in batch mode and during software developmentVaibhav Saini, Hitesh Sajnani, JaeWoo Kim, Cristina V. Lopes. 597-600 [doi]
• Visually reasoning about system and resource behaviorTony Ohmann, Ryan Stanley, Ivan Beschastnikh, Yuriy Brun. 601-604 [doi]
• Toward arbitrary mapping for debugging visualizationsYung-Pin Cheng, Chiu-Yu Ku, Wei-Chen Pan, Chuan Yang, Ting-Shu Lin. 605-608 [doi]
• FUSION: a tool for facilitating and augmenting android bug reportingKevin Moran, Mario Linares Vásquez, Carlos Bernal-Cárdenas, Denys Poshyvanyk. 609-612 [doi]
• JDeodorant: clone refactoringDavood Mazinanian, Nikolaos Tsantalis, Raphael Stein, Zackary Valenta. 613-616 [doi]
• AD-ROOM: a tool for automatic detection of refactorings in object-oriented modelsDjamel Eddine Khelladi, Reda Bendraou, Marie-Pierre Gervais. 617-620 [doi]
• srcSlice: a tool for efficient static forward slicingChristian D. Newman, Tessandra Sage, Michael L. Collard, Hakam W. Alomari, Jonathan I. Maletic. 621-624 [doi]
• SPYSE: a semantic search engine for python packages and modulesShiva Krishna Imminni, Mir Anamul Hasan, Michael Duckett, Puneet Sachdeva, Sudipta Karmakar, Piyush Kumar, Sonia Haiduc. 625-628 [doi]
• FeatureIDE: taming the preprocessor wildernessJens Meinicke, Thomas Thüm, Reimar Schröter, Sebastian Krieter, Fabian Benduhn, Gunter Saake, Thomas Leich. 629-632 [doi]
• JooMDD: a model-driven development environment for web content management system extensionsDennis Priefer, Peter Kneisel, Gabriele Taentzer. 633-636 [doi]
• Microsoft touch develop and the BBC micro: bitThomas Ball, Jonathan Protzenko, Judith Bishop, Michal Moskal, Jonathan de Halleux, Michael Braun, Steve Hodges, Clare Riley. 637-640 [doi]
• DECA: development emails content analyzerAndrea Di Sorbo, Sebastiano Panichella, Corrado Aaron Visaggio, Massimiliano Di Penta, Gerardo Canfora, Harald C. Gall. 641-644 [doi]
• CodeTube: extracting relevant fragments from software development video tutorialsLuca Ponzanelli, Gabriele Bavota, Andrea Mocci, Massimiliano Di Penta, Rocco Oliveto, Barbara Russo, Sonia Haiduc, Michele Lanza. 645-648 [doi]
• TASSAL: autofolding for source code summarizationJaroslav M. Fowkes, Pankajan Chanthirasegaran, Razvan Ranca, Miltiadis Allamanis, Mirella Lapata, Charles A. Sutton. 649-652 [doi]
• LibRadar: fast and accurate detection of third-party libraries in Android appsZiang Ma, Haoyu Wang, Yao Guo, Xiangqun Chen. 653-656 [doi]
• Causal impact for app store analysisWilliam Martin. 659-661 [doi]
• Identifying successful strategies for resolving static analysis notificationsJustin Smith. 662-664 [doi]
• Do biases related to geographical location influence work-related decisions in GitHub?Ayushi Rastogi. 665-667 [doi]
• Safely evolving preprocessor-based configurable systemsFlávio Medeiros. 668-670 [doi]
• Discovering important source code termsPaige Rodeghero, Collin McMillan. 671-673 [doi]
• Scaling testing of refactoring enginesMelina Mongiovi. 674-676 [doi]
• RDIT: race detection from incomplete tracesArun K. Rajagopalan. 677-679 [doi]
• Towards better program obfuscation: optimization via language modelsHan Liu. 680-682 [doi]
• An empirical study of blindness and program comprehensionAmeer Armaly, Collin McMillan. 683-685 [doi]
• Maximally stateless model checking for concurrent bugs under relaxed memory modelsAlan Huang. 686-688 [doi]
• FSMdroid: guided GUI testing of android appsTing Su. 689-691 [doi]
• Instantaneous performance bug detection in IDEShanshan Li. 692-694 [doi]
• Code parallelization through sequential code searchBowen Cai. 695-697 [doi]
• Extracting conceptual interoperability constraints from API documentation using machine learningHadil Abukwaik, Mohammed Abujayyab, Shah Rukh Humayoun, H. Dieter Rombach. 701-703 [doi]
• Technical debt prioritization using predictive analyticsZadia Codabux, Byron J. Williams. 704-706 [doi]
• Recommending developers with supplementary information for issue request resolutionHui Yang, Xiaobing Sun, Bin Li, Jiajun Hu. 707-709 [doi]
• A new homogeneous pure birth process based software reliability modelNéstor Ruben Barraza. 710-712 [doi]
• On the effectiveness of labeled latent dirichlet allocation in automatic bug-report categorizationMinhaz F. Zibran. 713-715 [doi]
• On the reduction of verbose queries in text retrieval based software maintenanceOscar Chaparro, Andrian Marcus. 716-718 [doi]
• Security expert recommender in software engineeringShahab Bayati. 719-721 [doi]
• Towards promoting design and UML modeling practices in the open source communityAbdullah Aldaeej, Omar Badreddin. 722-724 [doi]
• Applying scrum to the army: a case studyLuigi Benedicenti, Franco Raffaele Cotugno, Paolo Ciancarini, Angelo Messina, Witold Pedrycz, Alberto Sillitti, Giancarlo Succi. 725-727 [doi]
• Debugging reactive programming with reactive inspectorGuido Salvaneschi, Mira Mezini. 728-730 [doi]
• Making a difference: an overview of humanitarian free open source systemsEsteban Parra, Sonia Haiduc, Rebecca James. 731-733 [doi]
• A new thread-aware birthmark for plagiarism detection of multithreaded programsZhenzhou Tian, Ting Liu, Qinghua Zheng, Feifei Tong, Ming Fan, Zijiang Yang. 734-736 [doi]
• When to release in open source project?Zeheng Li, LiGuo Huang. 737-739 [doi]
• Topsy-Turvy: a smarter and faster parallelization of mutation analysisRahul Gopinath, Carlos Jensen, Alex Groce. 740-743 [doi]
• Mobile malware detection in the real worldFrancesco Mercaldo, Corrado Aaron Visaggio, Gerardo Canfora, Aniello Cimitile. 744-746 [doi]
• Continuous assessment of software traceabilityPatrick Rempel, Patrick Mäder. 747-748 [doi]
• Characterizing API elements in software documentation with vector representationThanh Van Nguyen, Anh Tuan Nguyen, Tien N. Nguyen. 749-751 [doi]
• Guiding the crowds for Android testingXin Zhang, Zhenyu Chen, Chunrong Fang, Zicong Liu. 752-753 [doi]
• Assessing iterative practical software engineering courses with play moneyKai Mindermann, Jan-Peter Ostberg, Stefan Wagner 0001. 754-755 [doi]
• Mapping API elements for code migration with vector representationsTrong Duc Nguyen, Anh Tuan Nguyen, Tien N. Nguyen. 756-758 [doi]
• Candoia: a platform and ecosystem for mining software repositories toolsNitin M. Tiwari, Ganesha Upadhyaya, Hridesh Rajan. 759-764 [doi]
• Analysing the program analyserCristian Cadar, Alastair F. Donaldson. 765-768 [doi]
• Continuous validation for data analytics systemsMark Staples, Liming Zhu, John C. Grundy. 769-772 [doi]
• COPE: vision for a change-oriented programming environmentDanny Dig, Ralph E. Johnson, Darko Marinov, Brian P. Bailey, Don S. Batory. 773-776 [doi]
• Exploring process improvement decisions to support a rapidly evolving developer baseErika S. Mesh, David M. Tolar, J. Scott Hawker. 777-780 [doi]
• Prodirect manipulation: bidirectional programming for the massesRavi Chugh. 781-784 [doi]
• Code dronesMithun P. Acharya, Chris Parnin, Nicholas A. Kraft, Aldo Dagnino, Xiao Qu. 785-788 [doi]
• Testing the untestable: model testing of complex software-intensive systemsLionel C. Briand, Shiva Nejati, Mehrdad Sabetzadeh, Domenico Bianculli. 789-792 [doi]
• Theories of everythingPamela Zave. 793-796 [doi]
• Wide-field ethnography: studying software engineering in 2025 and beyondDavid Socha, Robin Adams, Kelly Franznick, Wolff-Michael Roth, Kevin Sullivan, Josh Tenenberg, Skip Walter. 797-802 [doi]
• A variability aware configuration management and revision control platformLukas Linsbauer, Alexander Egyed, Roberto Erick Lopez-Herrejon. 803-806 [doi]
• Architectural-based speculative analysis to predict bugs in a software systemDuc Minh Le, Nenad Medvidovic. 807-810 [doi]
• Assisting developers with license complianceChristopher Vendome, Denys Poshyvanyk. 811-814 [doi]
• Automatized derivation of comprehensive specifications for black-box servicesSimon Schwichtenberg, Gregor Engels. 815-818 [doi]
• Boosting static analysis of Android apps through code instrumentationLi Li. 819-822 [doi]
• Cognitive biases in software quality and testingIflaah Salman. 823-826 [doi]
• Context-sensitive identification of refactoring opportunitiesDiego Cedrim. 827-830 [doi]
• Fixing bug reporting for mobile and GUI-based applicationsKevin Moran, Denys Poshyvanyk. 831-834 [doi]
• Implications of requirements engineering on software design: a cognitive insightRahul Mohanani. 835-838 [doi]
• Mining software process linesFabian Rojas Blum. 839-842 [doi]
• Ontology learning and its application in software-intensive projectsJin Guo, Jane Cleland-Huang. 843-846 [doi]
• Realistic bug triagingAli Sajedi Badashian. 847-850 [doi]
• Recognizing relevant code elements during change task navigationKatja Kevic. 851-854 [doi]
• Reducing the test effort of variability-rich systems by using feature interaction knowledge and variability-aware source code analysisStefan Fischer. 855-858 [doi]
• Reusing stack traces: automated attack surface approximationChristopher Theisen. 859-862 [doi]
• Spotting design problems with smell agglomerationsLeonardo da Silva Sousa. 863-866 [doi]
• Towards a better understanding of the impact of experimental components on defect prediction modellingChakkrit Tantithamthavorn. 867-870 [doi]
• Trace link evolution across multiple software versions in safety-critical systemsMona Rahimi. 871-874 [doi]
• Using data provenance to improve software process enactment, monitoring and analysisGabriella Castro Barbosa Costa. 875-878 [doi]
• When more heads are better than one?: understanding and improving collaborative identification of code smellsRoberto Oliveira. 879-882 [doi]
• Rethinking verification: accuracy, efficiency and scalability through human-machine collaborationSuresh Kothari, Ahmed Tamrawi, Jon Mathews. 885-886 [doi]
• How not to do it: anti-patterns for data science in software engineeringTim Menzies. 887 [doi]
• Software engineering for molecular programmingRobyn R. Lutz, Jack H. Lutz. 888-889 [doi]
• Improving and balancing software qualitiesBarry W. Boehm. 890-891 [doi]
• Logic-based learning in software engineeringDalal Alrajeh, Alessandra Russo, Sebastián Uchitel, Jeff Kramer. 892-893 [doi]
• Software release planningXavier Franch, Guenther Ruhe. 894-895 [doi]
• Risk assessment in open source systemsXavier Franch, Angelo Susi. 896-897 [doi]
• The use of text retrieval and natural language processing in software engineeringSonia Haiduc, Venera Arnaoudova, Andrian Marcus, Giuliano Antoniol. 898-899 [doi]
• Analyzing software engineering experiments: everything you always wanted to know but were afraid to askNatalia Juristo, Sira Vegas. 900-901 [doi]
• Software analytics: challenges and opportunitiesLatifa Guerrouj, Olga Baysal, David Lo, Foutse Khomh. 902-903 [doi]
• Advances in unit testing: theory and practiceTao Xie, Nikolai Tillmann, Pratap Lakshman. 904-905 [doi]
• Using docker containers to improve reproducibility in software engineering researchJürgen Cito, Harald C. Gall. 906-907 [doi]
• Control theory for software engineering: technical briefingAntonio Filieri, Martina Maggio. 908-910 [doi]