The IWPSE-EVOL workshop is the merger of the International Workshop on Principles of Software Evolution (IWPSE) and the annual ERCIM Workshop on Software Evolution (EVOL). The objectives of this joint event are to provide a forum to discuss a wide range of topics in software evolution, to foster the better understanding of the nature of software evolution, and to accelerate research activities on the subject.
The 2010 edition of the IWPSE-EVOL focuses on the special theme of automation in the context of software evolution. This theme has been chosen to pay tribute to the host conference, the 25th IEEE/ACM International Conference on Automated Software Engineering (ASE'2010).
IWPSE-EVOL'2010 attracted 31 submissions. All submissions were reviewed by at least three members of the program committee and selected after an online discussion process. The program committee selected 13 submissions for presentation and publication. The accepted submissions include 5 full research papers, 6 position papers, 1 industrial paper and 1 tool demonstration paper. The acceptance rate for full research papers was 29.4%. The IWPSE-EVOL program committee awarded the "IWPSE-EVOL 2010 best paper award" to "Replaying Past Changes on Multi-developer Projects" by Lile Hattori, Mircea Lungu and Michele Lanza.
Proceeding Downloads
Software is data too: how should we deal with it?
Software systems are designed and engineered to process data. However, software is data too. The size and variety of today's software artifacts and the multitude of stakeholder activities result in so much data that individuals can no longer reason ...
Empirical studies on software evolution: should we (try to) claim causation?
In recent and past years, there have been hundreds of studies aimed at characterizing the evolution of a software system. Many of these studies analyze the behavior of a variable over a given period of observation. How does the size of a software system ...
Do metrics help to identify refactoring?
Many iterative software development methodologies, such as for example eXtreme Programming, state that refactoring is one of the key activities to be undertaken in order to keep the code-base of a project well-structured and consistent. In such a ...
Recording finer-grained software evolution with IDE: an annotation-based approach
This paper proposes a formalized technique for generating finer-grained source code deltas according to a developer's editing intentions. Using the technique, the developer classifies edit operations of source code by annotating the time series of the ...
Replaying past changes in multi-developer projects
What was I working on before the weekend? and What were the members of my team working on during the last week? are common questions that are frequently asked by a developer. They can be answered if one keeps track of who changes what in the source ...
Identifying cross-cutting concerns using software repository mining
Cross-cutting concerns are pieces of functionality that have not been captured into a separate module, thereby hindering program comprehension and maintainability. Solving these problems requires first identifying these cross-cutting concerns in pieces ...
Redocumentation of a legacy banking system: an experience report
Successful software systems need to be maintained. In order to do that, deep knowledge about their architecture and implementation details is required. This knowledge is often kept implicit (inside the heads of the experts) and sometimes made explicit ...
A framework for analysing and visualising open source software ecosystems
Nowadays, most empirical studies in open source software evolution are based on the analysis of program code alone. In order to get a better understanding of how software evolves over time, many more entities that are part of the software ecosystem need ...
An exercise in iterative domain-specific language design
We describe our experiences with the process of designing a domain-specific language (DSL) and corresponding model transformations. The simultaneous development of the language and the transformations has lead to an iterative evolution of the DSL. We ...
An automated hint generation approach for supporting the evolution of requirements specifications
Updating the requirements specification during software evolution is a manual and expensive task. Therefore, software engineers usually choose to apply modifications directly to the code and leave the requirements unchanged. This leads to the loss of ...
An empirical study of the evolution of Eclipse third-party plug-ins
Since the inception of Lehman's software evolution laws in the early 1970s, they have attracted significant attention from the research community. However, to our knowledge, no study of applicability of these laws on the software systems that exhibit ...
Is duplicate code more frequently modified than non-duplicate code in software evolution?: an empirical study on open source software
Various kinds of research efforts have been performed on the basis that the presence of duplicate code has a negative impact on software evolution. A typical example is that, if we modify a code fragment that has been duplicated to other code fragments, ...
Evolutional analysis of licenses in FOSS
FOSS (Free and Open Source Software) is repeatedly modified and reused by other FOSS or proprietary software systems. They are released to others under specific licenses whose terms and conditions are usually written on the source-code files as program ...
Multi-tenant SaaS applications: maintenance dream or nightmare?
Multi-tenancy is a relatively new software architecture principle in the realm of the Software as a Service (SaaS) business model. It allows to make full use of the economy of scale, as multiple customers - "tenants" - share the same application and ...
Feature oriented evolutions for context-aware adaptive systems
Context-aware adaptive systems are a promising approach to deal with the uncertainty shown by the environment. Their ability is to perform run-time adaptations driven by the context thus promoting software evolution to the norm rather than considering ...
- Proceedings of the Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE)