On the proactive identification of mistakes on concern mapping tasks
Proceedings of the tenth international conference on Aspect-oriented software development companion
Concern-based cohesion as change proneness indicator: an initial empirical study
Proceedings of the 2nd International Workshop on Emerging Trends in Software Metrics
On the relationship of concern metrics and requirements maintainability
Information and Software Technology
Proceedings of the 34th International Conference on Software Engineering
| Hi-index | 0.00 |
Concern mapping is the activity of assigning a stakeholder’s concern to its corresponding elements in the source code. This activity is primordial to guide software maintainers in several tasks, such as understanding and restructuring the implementation of existing concerns. Even though different techniques are emerging to facilitate the concern mapping process, they are still manual and error-prone according to recent studies. Existing work does not provide any guidance to developers to review and correct concern mappings. In this context, this paper presents the characterization and classification of eight concern mapping mistakes commonly made by developers. These mistakes were found to be associated with various properties of concerns and modules in the source code. The mistake categories were derived from actual mappings of 10 concerns in 12 versions of industry systems. In order to further evaluate to what extent these mistakes also occur in wider contexts, we ran two experiments where 26 subjects mapped 10 concerns in two systems. Our experimental results confirmed the mapping mistakes that often occur when developers need to interact with the source code.