Powered by
2014 Software Evolution Week --- IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering (CSMR-WCRE),
February 3-6, 2014,
Antwerp, Belgium
Keynotes
Using Biology and Ecology as Inspiration for Software Maintenance? (Keynote Abstract)
Philippe Grosjean
(University of Mons, Belgium)
As a bioengineer and marine ecologist, I probably have a different view on software complexity and evolution than specialists in this field. The literature as well as discussion with colleagues suggests that there may well be "hidden gems" in traditional ecology for software engineers. In this presentation, I will compare a couple of biological and software (mostly Open Source) ecosystems and suggest a few ideas that may be useful for software maintenance research.
Two key aspects appeared to me when I started to work on Open Source software ecosystems: (1) the difference in terminology in biology and software engineering, and (2) the much more collaborative trends in software ecosystems, compared to biological ecosystems.
The first aspect is mostly a technical issue that unfortunately creates a strong barrier between software engineers and biologists. So, it should be worth considering using the same or similar meaning for the same terms, like ecosystem, resource, consumer,... in both disciplines.
The second aspect is much more interesting. So, software ecosystems exhibit much more collaboration and much less competition than biological ecosystems? Since biologists consider competition as one of the major driving forces for biological evolution (recall Darwin and his natural selection mechanism through struggle for existence), it is very clear that the fundamental rules that drive both biological and software ecosystems are completely different.
@InProceedings{CSMR-WCRE14p1,
author = {Philippe Grosjean},
title = {Using Biology and Ecology as Inspiration for Software Maintenance? (Keynote Abstract)},
booktitle = {Proc.\ CSMR-WCRE},
publisher = {IEEE},
pages = {1--1},
doi = {},
year = {2014},
}
Mitigating the Risk of Software Change in Practice: Retrospective on More Than 50 Architecture Evaluations in Industry (Keynote Paper)
Jens Knodel and Matthias Naab
(Fraunhofer IESE, Germany)
Architecture evaluation has become a mature instrument to mitigate the risk of software change. It enables decision-making about software systems being changed or being prepared for change. While scientific literature on architecture evaluation approaches is available, publications on practical experiences are rather limited. In this paper, we share our experiences – after having performed more than 50 architecture evaluations for industrial customers in the last decade. We compiled facts and consolidate our findings about the risk of software change and architecture evaluations as a means to mitigate change. We highlight the role of reverse engineering in these projects. In addition, we share our lessons learned and provide data on common beliefs and provide examples for frequently observed misconceptions on the power of reverse engineering. This industrial and practical perspective allows practitioners to benefit from our experience in their daily architecture work and the scientific community to focus their research work on the generalizability of our findings.
@InProceedings{CSMR-WCRE14p2,
author = {Jens Knodel and Matthias Naab},
title = {Mitigating the Risk of Software Change in Practice: Retrospective on More Than 50 Architecture Evaluations in Industry (Keynote Paper)},
booktitle = {Proc.\ CSMR-WCRE},
publisher = {IEEE},
pages = {2--17},
doi = {},
year = {2014},
}
The Vision of Software Clone Management: Past, Present, and Future (Keynote Paper)
Chanchal K. Roy, Minhaz F. Zibran, and Rainer Koschke
(University of Saskatchewan, Canada; University of Bremen, Germany)
Duplicated code or code clones are a kind of code smell that have both positive and negative impacts on the development and maintenance of software systems. Software clone research in the past mostly focused on the detection and analysis of code clones, while research in recent years extends to the whole spectrum of clone management. In the last decade, three surveys appeared in the literature, which cover the detection, analysis, and evolutionary characteristics of code clones. This paper presents a comprehensive survey on the state of the art in clone management, with in-depth investigation of clone management activities (e.g., tracing, refactoring, cost-benefit analysis) beyond the detection and analysis. This is the first survey on clone management, where we point to the achievements so far, and reveal avenues for further research necessary towards an integrated clone management system. We believe that we have done a good job in surveying the area of clone management and that this work may serve as a roadmap for future research in the area.
@InProceedings{CSMR-WCRE14p18,
author = {Chanchal K. Roy and Minhaz F. Zibran and Rainer Koschke},
title = {The Vision of Software Clone Management: Past, Present, and Future (Keynote Paper)},
booktitle = {Proc.\ CSMR-WCRE},
publisher = {IEEE},
pages = {18--33},
doi = {},
year = {2014},
}
proc time: 0.22