Abstract is missing.
- From off-Line to continuous on-line maintenanceMauro Pezzè. 2-3 [doi]
- Leveraging natural language analysis of software: Achievements, challenges, and opportunitiesLori L. Pollock. 4 [doi]
- An industrial case study of Coman's automated task detection algorithm: What Worked, What Didn't, and WhyLijie Zou, Michael W. Godfrey. 6-14 [doi]
- Vasco: A visual approach to explore object churn in framework-intensive applicationsFleur Duseau, Bruno Dufour, Houari A. Sahraoui. 15-24 [doi]
- What makes a good code example?: A study of programming Q&A in StackOverflowSeyed Mehdi Nasehi, Jonathan Sillito, Frank Maurer, Chris Burns. 25-34 [doi]
- Testing C++ generic librariesAndrew Sutton, Marcin Zalewski. 36-45 [doi]
- Code coverage-based regression test selection and prioritization in WebKitÁrpád Beszédes, Tamás Gergely, Lajos Schrettner, Judit Jász, Laszlo Lango, Tibor Gyimóthy. 46-55 [doi]
- An empirical analysis of the distribution of unit test smells and their impact on software maintenanceGabriele Bavota, Abdallah Qusef, Rocco Oliveto, Andrea De Lucia, David Binkley. 56-65 [doi]
- Interactive fault localization leveraging simple user feedbackLiang Gong, David Lo, Lingxiao Jiang, Hongyu Zhang. 67-76 [doi]
- Finding errors from reverse-engineered equality models using a constraint solverChandan Raj Rupakheti, Daqing Hou. 77-86 [doi]
- The Order of Things: How developers sort fields and methodsBenjamin Biegel, Fabian Beck, Willi Hornig, Stephan Diehl. 88-97 [doi]
- Rejuvenating C++ programs through demacroficationAditya Kumar, Andrew Sutton, Bjarne Stroustrup. 98-107 [doi]
- A change impact analysis to characterize evolving program behaviorsNeha Rungta, Suzette Person, Joshua Branchaud. 109-118 [doi]
- Fine-grained change impact analysis for component-based product familiesAmir Reza Yazdanshenas, Leon Moonen. 119-128 [doi]
- Configuration selection using code change impact analysis for regression testingXiao Qu, Mithun Acharya, Brian Robinson. 129-138 [doi]
- Build system issues in multilanguage softwareAndrew Neitsch, Kenny Wong, Michael W. Godfrey. 140-149 [doi]
- Detecting semantic changes in Makefile build codeJafar M. Al-Kofahi, Hung Viet Nguyen, Anh Tuan Nguyen, Tung Thanh Nguyen, Tien N. Nguyen. 150-159 [doi]
- An empirical study of build system migrations in practice: Case studies on KDE and the Linux kernelRoman Suvorov, Meiyappan Nagappan, Ahmed E. Hassan, Ying Zou, Bram Adams. 160-169 [doi]
- Assessing the effect of requirements traceability for software maintenancePatrick Mäder, Alexander Egyed. 171-180 [doi]
- Do data dependencies in source code complement call dependencies for understanding requirements traceability?Hongyu Kuang, Patrick Mäder, Hao Hu, Achraf Ghabi, LiGuo Huang, Jian Lv, Alexander Egyed. 181-190 [doi]
- An empirical study on requirements traceability using eye-trackingNasir Ali, Zohreh Sharafi, Yann-Gaël Guéhéneuc, Giuliano Antoniol. 191-200 [doi]
- Recovering commit dependencies for selective code integration in software product linesTejinder Dhaliwal, Foutse Khomh, Ying Zou, Ahmed E. Hassan. 202-211 [doi]
- Search-based detection of high-level model changesAmeni ben Fadhel, Marouane Kessentini, Philip Langer, Manuel Wimmer. 212-221 [doi]
- How often do unintended inconsistencies happen? Deriving modification patterns and detecting overlooked code fragmentsYoshiki Higo, Shinji Kusumoto. 222-231 [doi]
- LINSEN: An efficient approach to split identifiers and expand abbreviationsAnna Corazza, Sergio Di Martino, Valerio Maggio. 233-242 [doi]
- Relating requirements to implementation via topic analysis: Do topics extracted from requirements make sense to managers and developers?Abram Hindle, Christian Bird, Thomas Zimmermann, Nachiappan Nagappan. 243-252 [doi]
- Making automatic repair for large-scale programs more efficient using weak recompilationYuhua Qi, Xiaoguang Mao, Yan Lei. 254-263 [doi]
- The impact of bug management patterns on bug fixing: A case study of Eclipse projectsMasao Ohira, Ahmed E. Hassan, Naoya Osawa, Ken-ichi Matsumoto. 264-273 [doi]
- Things structural clones tell that simple clones don'tHamid Abdul Basit, Usman Ali, Sidra Haque, Stan Jarzabek. 275-284 [doi]
- Cloning practices: Why developers clone and what can be changedGang Zhang, Xin Peng, Zhenchang Xing, Wenyun Zhao. 285-294 [doi]
- Models are code too: Near-miss clone detection for Simulink modelsManar H. Alalfi, James R. Cordy, Thomas R. Dean, Matthew Stephan, Andrew Stevenson. 295-304 [doi]
- Do code smells reflect important maintainability aspects?Aiko Fallas Yamashita, Leon Moonen. 306-315 [doi]
- A cost model based on software maintainabilityTibor Bakota, Péter Hegedus, Gergely Ladányi, Peter Kortvelyesi, Rudolf Ferenc, Tibor Gyimóthy. 316-325 [doi]
- A systematic mapping study on dynamic metrics and software qualityAmjed Tahir, Stephen G. MacDonell. 326-335 [doi]
- Refactoring in the presence of annotationsCarlos Noguera, Andy Kellens, Coen De Roover, Viviane Jonckers. 337-346 [doi]
- Search-based refactoring: Towards semantics preservationAli Ouni, Marouane Kessentini, Houari A. Sahraoui, Mohamed Salah Hamdi. 347-356 [doi]
- An empirical investigation into the impact of refactoring on regression testingNapol Rachatasumrit, Miryung Kim. 357-366 [doi]
- Survival of Eclipse third-party plug-insJohn Businge, Alexander Serebrenik, Mark van den Brand. 368-377 [doi]
- Measuring software library stability through historical version analysisSteven Raemaekers, Arie van Deursen, Joost Visser. 378-387 [doi]
- Inferring the data access from the clients of generic APIsHui Song, Gang Huang 0001, Yingfei Xiong, Yanchun Sun. 388-397 [doi]
- Refactoring meets spreadsheet formulasSandro Badame, Danny Dig. 399-409 [doi]
- Detecting code smells in spreadsheet formulasFelienne Hermans, Martin Pinzger, Arie van Deursen. 409-418 [doi]
- When would this bug get reported?Ferdian Thung, David Lo, Lingxiao Jiang, Lucia, Foyzur Rahman, Premkumar T. Devanbu. 420-429 [doi]
- Modelling the 'Hurried' bug report reading process to summarize bug reportsRafael Lotufo, Zeeshan Malik, Krzysztof Czarnecki. 430-439 [doi]
- Domain specific warnings: Are they any better?Andre Hora, Nicolas Anquetil, Stéphane Ducasse, Simon Allier. 441-450 [doi]
- Triaging incoming change requests: Bug or commit history, or code authorship?Mario Linares Vásquez, Kamal Hossen, Hoang Dang, Huzefa H. Kagdi, Malcom Gethers, Denys Poshyvanyk. 451-460 [doi]
- Feature-gathering dependency-based software clustering using Dedication and ModularityKenichi Kobayashi, Manabu Kamimura, Koki Kato, Keisuke Yano, Akihiko Matsuo. 462-471 [doi]
- Supervised software modularisationMathew Hall, Neil Walkinshaw, Phil McMinn. 472-481 [doi]
- A structured approach to assess third-party library usageVeronika Bauer, Lars Heinemann, Florian Deissenboeck. 483-492 [doi]
- Reengineering embedded automotive softwareAndreas Thums, Jochen Quante. 493-502 [doi]
- Incremental reengineering and migration of a 40 year old airport operations systemMario Bernhart, Andreas Mauczka, Michael Fiedler, Stefan Strobl, Thomas Grechenig. 503-510 [doi]
- Dead code elimination for web systems written in PHP: Lessons learned from an industry caseHidde Boomsma, B. V. Hostnet, Hans-Gerhard Gross. 511-515 [doi]
- Sustainability guidelines for long-living software systemsZoya Durdik, Benjamin Klatt, Heiko Koziolek, Klaus Krogmann, Johannes Stammel, Roland Weiss. 517-526 [doi]
- Facilitating enterprise software developer communication with CARESAnja Guzzi, Andrew Begel, Jessica K. Miller, Krishna Nareddy. 527-536 [doi]
- A framework for incremental quality analysis of large software systemsVeronika Bauer, Lars Heinemann, Benjamin Hummel, Elmar Jürgens, Michael Conradt. 537-546 [doi]
- Locating performance improvement opportunities in an industrial software-as-a-service applicationCor-Paul Bezemer, Andy Zaidman, Ad van der Hoeven, Andre van de Graaf, Maarten Wiertz, Remko Weijers. 547-556 [doi]
- Automated architectural reviews with SemmleKris De Schutter. 557-565 [doi]
- Time-leverage point detection for time sensitive software maintenanceEnyi Tang, Linzhang Wang, Jianhua Zhao, Xuandong Li. 567-570 [doi]
- Inferring weak references for fixing Java memory leaksJu Qian, Xiaoyu Zhou. 571-574 [doi]
- Move code refactoring with dynamic analysisShuhei Kimura, Yoshiki Higo, Hiroshi Igaki, Shinji Kusumoto. 575-578 [doi]
- Dependence communities in source codeJames Hamilton, Sebastian Danicic. 579-582 [doi]
- A study on repetitiveness of code completion operationsTakayuki Omori, Hiroaki Kuwabara, Katsuhisa Maruyama. 584-587 [doi]
- Vocabulary normalization improves IR-based concept locationDave Binkley, Dawn Lawrie, Christopher Uehlinger. 588-591 [doi]
- Who's who in Gnome: Using LSA to merge software repository identitiesErik Kouters, Bogdan Vasilescu, Alexander Serebrenik, Mark G. J. van den Brand. 592-595 [doi]
- Automatic classification of software related microblogsPhilips Kokoh Prasetyo, David Lo, Palakorn Achananuparp, Yuan Tian, Ee-Peng Lim. 596-599 [doi]
- Detecting similar applications with collaborative taggingFerdian Thung, David Lo, Lingxiao Jiang. 600-603 [doi]
- Inferring semantically related software terms and their taxonomy by leveraging collaborative taggingShaowei Wang, David Lo, Lingxiao Jiang. 604-607 [doi]
- Version history based source code plagiarism detection in proprietary systemsGirish Maskeri Rama, Deepthi Karnam, Sree Aurovindh Viswanathan, Srinivas Padmanabhuni. 609-612 [doi]
- Applying technical stock market indicators to analyze and predict the evolvability of open source projectsAseel Hmood, Mostafa Erfani, Iman Keivanloo, Juergen Rilling. 613-616 [doi]
- Refactoring edit history of source codeShinpei Hayashi, Takayuki Omori, Teruyoshi Zenmyo, Katsuhisa Maruyama, Motoshi Saeki. 617-620 [doi]
- Retrieving software maintenance history with topic modelsShusi Yu. 621-624 [doi]
- A software change impact analysis taxonomyJerod W. Wilkerson. 625-628 [doi]
- Adapting Linux for mobile platforms: An empirical study of AndroidFoutse Khomh, Hao Yuan, Ying Zou. 629-632 [doi]
- SEANets: Software evolution analysis with networksTheodoros Chaikalis, George Melas, Alexander Chatzigeorgiou. 634-637 [doi]
- Understanding model evolution through semantically lifting model differences with SiLiftTimo Kehrer, Udo Kelter, Manuel Ohrndorf, Tim Sollbach. 638-641 [doi]
- TraceME: Traceability Management in EclipseGabriele Bavota, Luigi Colangelo, Andrea De Lucia, Sabato Fusco, Rocco Oliveto, Annibale Panichella. 642-645 [doi]
- Bacterio: Java mutation testing tool: A framework to evaluate quality of tests casesPedro Reales Mateo, Macario Polo Usaola. 646-649 [doi]
- A toolset for GUI testing of Android applicationsDomenico Amalfitano, Anna Rita Fasolino, Porfirio Tramontana, Salvatore De Carmine, Gennaro Imparato. 650-653 [doi]
- MOTCP: A tool for the prioritization of test cases based on a sorting genetic algorithm and Latent Semantic IndexingMd. Mahfuzul Islam, Alessandro Marchetto, Angelo Susi, Fondazione Bruno Kessler, Giuseppe Scanniello. 654-657 [doi]
- The demacrofierAditya Kumar, Andrew Sutton, Bjarne Stroustrup. 658-661 [doi]
- Supporting the identification of architecturally-relevant code anomaliesIsela Macia Bertran, Roberta Arcoverde, Elder Cirilo, Alessandro Garcia, Arndt von Staa. 662-665 [doi]
- reBPMN: Recovering and reducing business processesAlex Tomasi, Alessandro Marchetto, Chiara Di Francescomarino, Angelo Susi. 666-669 [doi]
- MARBLE: Modernization approach for recovering business processes from legacy information systemsRicardo Pérez-Castillo. 671-676 [doi]
- Understanding deployment costs of enterprise systems: Towards architecture support in deployment decisionsBalthasar Weitzel. 677-680 [doi]