A Survey of Search-Based Refactoring for Software Maintenance

Abstract This survey reviews published materials related to the specific area of Search-Based Software Engineering that concerns software maintenance and, in particular, refactoring. The survey aims to give a comprehensive review of the use of search-based refactoring to maintain software. Fifty different papers have been selected from online databases to analyze and review the use of search-based refactoring in software engineering. The current state of the research is analyzed and patterns in the studies are investigated in order to assess gaps in the area and suggest opportunities for future research. The papers reviewed are tabulated in order to aid researchers in quickly referencing studies. The literature addresses different methods using search-based refactoring for software maintenance, as well as studies that investigate the optimization process and discuss components of the search. There are studies that analyze different software metrics, experiment with multi-objective techniques and propose refactoring tools for use. Analysis of the literature has indicated some opportunities for future research in the area. More experimentation of the techniques in an industrial environment and feedback from software developers is needed to support the approaches. Also, recent work with multi-objective techniques has shown that there are exciting possibilities for future research using these techniques with refactoring. This survey is beneficial as an introduction for any researchers aiming to work in the area of Search-Based Software Engineering with respect to software maintenance and will allow them to gain an understanding of the current landscape of the research and the insights gathered

The state of software maintenance

A state of software maintenance survey is presented, indicating the incongruity of the simultaneous existence of important and neglect in this field. An overview is given of selected developments and activities covering the following topics: the "Maintenance Problem", models, methods for improving maintenance, metrics, maintenance information management, standards, maintenance of existing code, and surveys. The paper concludes with a prognosis of what is ahead in maintenance: a battle and tradeoff between the forces for maintaining the base of existing software and the forces for the evolution of new systems. An Appendix is provided for the reader who desires information about a software maintenance conference and a special interest group

Rationale Management Challenges in Requirements Engineering

Rationale and rationale management have been playing an increasingly prominent role in software system development mainly due to the knowledge demand during system evaluation, maintenance, and evolution, especially for large and complex systems. The rationale management for requirements engineering, as a commencing and critical phase in software development life cycle, is still under-exploited. In this paper, we first survey briefly the state-of-the-art on rationale employment and applications in requirements engineering. Secondly, we identify the challenges in integrating rationale management in requirements engineering activities in order to promote further investigations and define a research agenda on rationale management in requirements engineering.

Maintenance Logistics Management: A Survey Study in the Moroccan Industrial Context

Global logistics system performance could not be achieved without an available intern logistics system for production systems.  Indeed, availability is the fastest path to performance where maintenance logistics occupies the central role.In this paper we define a systemic framework for maintenance logistics to manage all maintenance resources and their interactions.  In order to define main maintenance logistics management problems we conducted a structured survey study in the Moroccan industrial context. The study presents results based on 152 surveys responses from 281 surveys addressed to different industrial production systems. Results analysed on SPSS statistical software revealed an insufficient involvement level for production operator and insufficient organisation level for maintenance logistics environment. Therefore we propose a new sustainable model conception based on empirical conclusions. Keywords— Maintenance logistics system; management model; Operator involvement; maintenance logistics environment; SPSS software; maintenance improvement

End-user documentation

The first and most basic problem with documentation is that the consumer of software applications does not want to use the documentation included with a software product for one or more reasons. Studies, and papers, have been done on the effect that documentation has on a user's satisfaction with a software application; its ease of use, how quickly a user can learn to use the application, and on how documentation should be standardized. The premise of this thesis is that an improvement to the software maintenance processes can be achieved by limiting maintenance requests to "actual” problems with software, versus "perceived" problems caused by inadequate end-user documentation. After analyzing the literature within the computer science communities on the software maintenance process, and the literature within the educational and psychological communities on learning, retention, and the effect of software documentation on the end-user, a modification to the Foster Model was conceived. This model incorporates the concept of an Interactive Documentation Program (IDP), which allows for the end-user to utilize end-user directed and task-based documentation to improve their skills with the operation of commercially available off-the-shelf "office application" software as well as in-house developed software of a similar nature. To ascertain the viability of this concept, a world-wide survey of end-users is concerning their needs, desires, expectations, and complaints concerning end-user documentation was conducted. Combining the statistical results of the analysis of this survey with the concept of the IDP resulted in a new visuaUy-based and task oriented documentation paradigm called hypervideo

Why Modern Open Source Projects Fail

Open source is experiencing a renaissance period, due to the appearance of modern platforms and workflows for developing and maintaining public code. As a result, developers are creating open source software at speeds never seen before. Consequently, these projects are also facing unprecedented mortality rates. To better understand the reasons for the failure of modern open source projects, this paper describes the results of a survey with the maintainers of 104 popular GitHub systems that have been deprecated. We provide a set of nine reasons for the failure of these open source projects. We also show that some maintenance practices -- specifically the adoption of contributing guidelines and continuous integration -- have an important association with a project failure or success. Finally, we discuss and reveal the principal strategies developers have tried to overcome the failure of the studied projects.Comment: Paper accepted at 25th International Symposium on the Foundations of Software Engineering (FSE), pages 1-11, 201

Relevance, benefits, and problems of software modelling and model driven techniques—A survey in the Italian industry

Context Claimed benefits of software modelling and model driven techniques are improvements in productivity, portability, maintainability and interoperability. However, little effort has been devoted at collecting evidence to evaluate their actual relevance, benefits and usage complications. Goal The main goals of this paper are: (1) assess the diffusion and relevance of software modelling and MD techniques in the Italian industry, (2) understand the expected and achieved benefits, and (3) identify which problems limit/prevent their diffusion. Method We conducted an exploratory personal opinion survey with a sample of 155 Italian software professionals by means of a Web-based questionnaire on-line from February to April 2011. Results Software modelling and MD techniques are very relevant in the Italian industry. The adoption of simple modelling brings common benefits (better design support, documentation improvement, better maintenance, and higher software quality), while MD techniques make it easier to achieve: improved standardization, higher productivity, and platform independence. We identified problems, some hindering adoption (too much effort required and limited usefulness) others preventing it (lack of competencies and supporting tools). Conclusions The relevance represents an important objective motivation for researchers in this area. The relationship between techniques and attainable benefits represents an instrument for practitioners planning the adoption of such techniques. In addition the findings may provide hints for companies and universitie