1. SWEBOK, Chap 5 Maintenance
   • Auteurs Alain Abran, James W Moore, Pierre Bourque, Robert Dupuis, Leonard L Tripp
   • Date de publication 2004
   • Guide to the software engineering body of knowledge: 2004 version SWEBOK (chapitre sofware Maintenance)
2. IEEE Std. 14764-2006 (a.k.a. ISO/IEC 14764:2006) Standard for Software Engineering—Software Life Cycle Processes—Maintenance, IEEE, 2006.
3. Herraiz I, Rodriguez D, Robles G, Gonzalez-Barahona JM (2013) The Evolution of the Laws of Software Evolution: A Discussion Based on a Systematic Literature Review. ACM Comput Surv 46:28:1--28:28.
4. Demeyer S, Ducasse S, Nierstrasz O (2002) Object Oriented Reengineering Patterns. Morgan Kaufmann Publishers Inc., San Francisco, CA, USA
5. http://blog.cleancoder.com/ relativement au livre : Clean Code: A Handbook of Agile Software Craftsmanship

by Robert C. Martin

1. Who broke the build?: automatically identifying changes that induce test failures in continuous integration at Google scale
   • Auteurs : Celal Ziftci, Jim Reardon
   • Date de publication : 2017/5/20
   • Conférence Proceedings of the 39th International Conference on Software Engineering: Software Engineering in Practice Track
   • Pages 113-122
   • Description
     • Quickly identifying and fixing code changes that introduce regressions is critical to keep the momentum on software development, especially in very large scale software repositories with rapid development cycles, such as at Google. Identifying and fixing such regressions is one of the most expensive, tedious, and time consuming tasks in the software development life-cycle. Therefore, there is a high demand for automated techniques that can help developers identify such changes while minimizing manual human intervention …
2. The Evolution of Technical Debt in the Apache Ecosystem
   • Authors : Georgios Digkas, Mircea Lungu, Alexander Chatzigeorgiou, Paris Avgeriou
   • Publication date : 2017/9/11
   • Conference European Conference on Software Architecture
   • Pages 51-66
   • Description :
     • Software systems must evolve over time or become increasingly irrelevant says one of Lehman's laws of software evolution. Many studies have been presented in the literature that investigate the evolution of software systems but few have focused on the evolution of technical debt. In this paper we study sixty-six Java open-source software projects from the Apache ecosystem focusing on the evolution of technical debt. We analyze the evolution of these systems over the past five years at the temporal granularity level of weekly …
3. Evaluating an Architecture Conformance Monitoring Solution
   • Authors : Andrea Caracciolo, Mircea Lungu, Oskar Truffer, Kirill Levitin, Oscar Nierstrasz
   • Publication date : 2016/3/13
   • Conference Empirical Software Engineering in Practice (IWESEP), 2016 7th International Workshop on
   • Pages 41-44
   • Description
     • Architectural rules are often defined but rarely tested. Current tools offer limited functionality and often require significant effort to be configured, automated and integrated within existing platforms. We propose a platform that is aimed at reducing the overall cost of setting up and maintaining an architectural conformance monitoring environment by decoupling the conceptual representation of a user-defined rule from its technical specification prescribed by the underlying analysis tools. The user is no longer expected …
4. The Impact of Continuous Integration on Other Software Development Practices: A Large-Scale Empirical Study
   • Authors : Yangyang Zhao, Alexander Serebrenik, Yuming Zhou, Vladimir Filkov, Bogdan Vasilescu
   • Date de publication 2017
   • Conférence ASE
   • Description
     • Continuous Integration (CI) has become a disruptive innovation in software development: with proper tool support and adoption, positive effects have been demonstrated for pull request throughput and scaling up of project sizes. As any other innovation, adopting CI implies adapting existing practices in order to take full advantage of its potential, and“ best practices” to that end have been proposed. Here we study the adaptation and evolution of code writing and submission, issue and pull request closing …
5. Are developers aware of the architectural impact of their changes?
   • Auteurs : Matheus Paixao, Jens Krinke, DongGyun Han, Chaiyong Ragkhitwetsagul, Mark Harman
   • Date de publication 2017/10/30
   • Conférence Proceedings of the 32nd IEEE/ACM International Conference on Automated Software Engineering
   • Pages 95-105
   • Description :
     • Although considered one of the most important decisions in a software development lifecycle, empirical evidence on how developers perform and perceive architectural changes is still scarce. Given the large implications of architectural decisions, we do not know whether developers are aware of their changes' impact on the software's architecture, whether awareness leads to better changes, and whether automatically making developers aware would prevent degradation. Therefore, we use code review data of 4 …
6. Mining Implicit Design Templates for Actionable Code Reuse
   • Auteurs : Yun Lin, Guozhu Meng, Yinxing Xue, Zhenchang Xing, Jun Sun, Xin Peng, Yang Liu, Wenyun Zhao, Jinsong Dong
   • Date de publication : 2017/10
   • Conférence The 32nd IEEE/ACM International Conference on Automated Software Engineering
   • Pages 394–404
   • Description
     • In this paper, we propose an approach to detecting project-specific recurring designs in code base and abstracting them into design templates as reuse opportunities. The mined templates allow programmers to make further customization for generating new code. The generated code involves the code skeleton of recurring design as well as the semi-implemented code bodies annotated with comments to remind programmers of necessary modification. We implemented our approach as an Eclipse plugin called …
7. Test case selection in industry: an analysis of issues related to static approaches
   • Auteurs Vincent Blondeau, Anne Etien, Nicolas Anquetil, Sylvain Cresson, Pascal Croisy, Stéphane Ducasse
   • Date de publication 2016
   • Revue Software Quality Journal
   • Pages 1-35
   • Description :
     • Automatic testing constitutes an important part of everyday development practice. Worldline, a major IT company, is creating more and more tests to ensure the good behavior of its applications and gains in efficiency and quality. But running all these tests may take hours. This is especially true for large systems involving, for example, the deployment of a web server or communication with a database. For this reason, tests are not launched as often as they should be and are mostly run at night. The company wishes to improve its …
8. The Quest for Open Source Projects That Use UML
   • Auteurs: Regina Hebig, Truong Ho Quang, Michel RV Chaudron, Gregorio Robles, Miguel Angel Fernandez
   • Date de publication : 2016/10/2
   • Conférence Proceedings of the ACM/IEEE 19th International Conference on Model Driven Engineering Languages and Systems
   • Pages 173-183
   • Description
     • Context: While industrial use of UML was studied intensely, little is known about UML use in Free/Open Source Software (FOSS) projects. Goal: We aim at systematically mining GitHub projects to answer the question when models, if used, are created and updated throughout the whole project's life-span. Method: We present a semi-automated approach to collect UML stored in images,. xmi, and. uml files and scanned ten percent of all GitHub projects (1.24 million). Our focus was on number and role of contributors that …
   • Et aussi : An extensive dataset of UML models in GitHub
9. Assessing Code Authorship: The Case of the Linux Kernel.
   • Auteurs Guilherme Avelino, Leonardo Passos, Andre Hora, Marco Tulio Valente
   • Date de publication 2017/5/22
   • Conférence IFIP International Conference on Open Source Systems
   • Pages 151-163
   • Description
     • Code authorship is a key information in large-scale open-source systems. Among others, it allows maintainers to assess division of work and identify key collaborators. Interestingly, open-source communities lack guidelines on how to manage authorship. This could be mitigated by setting to build an empirical body of knowledge on how authorship-related measures evolve in successful open-source communities. Towards that direction, we perform a case study on the Linux kernel. Our results show that:(a) only a small portion of …
10. Secure Open Source Collaboration: An Empirical Study of Linus’ Law
    • Auteurs Andrew Meneely, Laurie Williams
    • Date de publication 2009/11/9
    • Conférence Proceedings of the 16th ACM conference on Computer and communications security
    • Pages 453-462
    • Description : Open source software is often considered to be secure. One factor in this confidence in the security of open source software lies in leveraging large developer communities to find vulnerabilities in the code. Eric Raymond declares Linus' Law“ Given enough eyeballs, all bugs are shallow.” Does Linus' Law hold up ad infinitum? Or, can the multitude of developers become“ too many cooks in the kitchen”, causing the system's security to suffer as a result? In this study, we examine the security of an open source …
11. Code Smells in iOS Apps: How do they compare to Android?
    • Auteurs : Sarra Habchi, Geoffrey Hecht, Romain Rouvoy, Naouel Moha
    • Date de publication : 2017/5/20
    • Conférence : Proceedings of the 4th International Conference on Mobile Software Engineering and Systems
    • Pages : 110-121
    • Description
      • With billions of app downloads, the Apple App Store and Google Play Store succeeded to conquer mobile devices. However, this success also challenges app developers to publish high-quality apps to keep attracting and satisfying end-users. In particular, taming the ever-growing complexity of mobile apps to cope with maintenance and evolution tasks under such a pressure may lead to bad development choices. While these bad choices, aka code smells, are widely studied in object-oriented software, their study …
12. (Non disponible en ligne…) Code review analysis of software system using machine learning techniques
    • Auteurs Harsh Lal, Gaurav Pahwa
    • Date de publication 2017/1/5
    • Conférence Intelligent Systems and Control (ISCO), 2017 11th International Conference on
    • Pages 8-13
    • Description
      • Code review is systematic examination of a software system's source code. It is intended to find mistakes overlooked in the initial development phase, improving the overall quality of software and reducing the risk of bugs among other benefits. Reviews are done in various forms such as pair programming, informal walk-through, and formal inspections. Code review has been found to accelerate and streamline the process of software development like very few other practices in software development can. In this paper we …
13. Beaucoup d'articles proviennent de ASE 2017, d'autres peuvent être intéressants en fonction de vos sujets d'études.
14. Hebig, R., Quang, T. H., Chaudron, M. R. V., Robles, G., & Fernandez, M. A. (2016). The quest for open source projects that use UML. In Proceedings of the ACM/IEEE 19th International Conference on Model Driven Engineering Languages and Systems - MODELS ’16. https://doi.org/10.1145/2976767.2976778
15. Inferring Hierarchical Motifs from Execution Traces
16. mobilesoft_2018.pdf

1. The WEKA Data Mining Software: An Update
   • Date 2009
   • Description :
     • More than twelve years have elapsed since the first public release of WEKA. In that time, the software has been rewritten entirely from scratch, evolved substantially and now accompanies a text on data mining [35]. These days, WEKA enjoys widespread acceptance in both academia and business, has an active community, and has been downloaded more than 1.4 million times since being placed on Source-Forge in April 2000. This paper provides an introduction to the WEKA workbench, reviews the history of the project, and …
2. Martinez J, Ziadi T, Bissyandé T, Klein J, Le Traon Y (2015) Automating the Extraction of Model-based Software Product Lines from Model Variants. 30th ACM/IEEE Int. Conf. Autom. Softw. Eng. - ASE. ACM/IEEE, Lincoln, Nebraska, United States
   1. Khatoon S, Li G, Mahmood A (2013) Comparison and Evaluation of Source Code Mining Tools and Techniques: A Qualitative Approach. Intell Data Anal 17:459–484. doi: 10.3233/IDA-130589
3. Ouni A, Kessentini M, Sahraoui H, Inoue K, Hamdi MS (2015) Improving Multi-objective Code-smells Correction Using Development History. J Syst Softw 105:18–39. doi: 10.1016/j.jss.2015.03.040 (63 pages)
4. Kalenkova AA, van der Aalst WMP, Lomazova IA, Rubin VA (2016) Process Mining Using BPMN: Relating Event Logs and Process Models. Proc. ACM/IEEE 19th Int. Conf. Model Driven Eng. Lang. Syst. ACM, New York, NY, USA, p 123
5. Hassan AE (2009) Predicting faults using the complexity of code changes. Proc. - Int. Conf. Softw. Eng. pp 78–88
6. A survey and taxonomy of approaches for mining software repositories in the context of software evolution
7. Nachiappan Nagappan, Thomas Ball, and Andreas Zeller. 2006. Mining metrics to predict component failures. In Proceedings of the 28th international conference on Software engineering (ICSE '06). ACM, New York, NY, USA, 452-461. DOI=http://dx.doi.org/10.1145/1134285.1134349
8. Don't touch my code!: examining the effects of ownership on software quality C Bird, N Nagappan, B Murphy, H Gall, P Devanbu - Proceedings of the 19th ACM SIGSOFT symposium …, 2011
9. Foucault M, Palyart M, Blanc X, Murphy GC, Falleri J-R (2015) Impact of Developer Turnover on Quality in Open-source Software. Proc. 2015 10th Jt. Meet. Found. Softw. Eng. ACM, New York, NY, USA, pp 829–841
10. Hora A, Robbes R, Anquetil N, Etien A, Ducasse S, Valente MT (2015) How do developers react to API evolution? the Pharo ecosystem case. 2015 IEEE 31st Int. Conf. Softw. Maint. Evol. ICSME 2015 - Proc. Institute of Electrical and Electronics Engineers Inc., pp 251–260
11. Silva LL, Valente MT, Maia M, Anquetil N (2015) Developers’ Perception of Co-Change Patterns: An Empirical Study. Proc. 31st IEEE Int. Conf. Softw. Maint.
12. Hecht G, Benomar O, Rouvoy R, Moha N, Duchien L (2016) Tracking the software quality of android applications along their evolution. Proc. - 2015 30th IEEE/ACM Int. Conf. Autom. Softw. Eng. ASE 2015. Institute of Electrical and Electronics Engineers Inc., pp 236–247
13. Karina Sokolova, Marc Lemercier, Ludovic Garcia,Android Passive MVC: a novel architecture model for the Android application development, in The Fifth International Conferences on Pervasive Patterns and Applications (PATTERNS 2013), May 27 - June 1, 2013 - Valencia, Spain, vol. , pp. 7
14. Software evolution in open source projects—a large-scale investigation| (Evaluer les Lois de l'évolution)
15. featuresEmpirical-based recovery and maintenance of input error-correction
16. Benomar O, Sahraoui H, Poulin P (2013) Visualizing software dynamicities with heat maps. Softw. Vis. (VISSOFT), 2013 First IEEE Work. Conf. pp 1–10
17. A Unified Framework for the Comprehension of Software’s Time Dimension
18. Witten IH, Frank E, Hall M a (2011) Data Mining: Practical Machine Learning Tools and Techniques (Google eBook). Complement Lit None. doi: 0120884070, 9780120884070

Autres

1. Unbundling Pokémon Go et la masse de documentations sur le reverse de Pokemon Go… A utiliser avec “responsabilité”