On the impact of crosscutting concern projection on code measurement

Figueiredo, Eduardo; Garcia, Alessandro; Maia, Marcelo de Almeida; Ferreira, Gonçalo Cordeiro; Nunes, Camila; Whittle, Jon

doi:10.1145/1960275.1960287

Cited by 14 publications

(6 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Each participant were asked to refactor one crosscutting concern of each application using the AspectJ programming language [18]. [12,14] and Lines of Concern Code (LOCC) [12,14] measure the concern size using the same units. All concerns and applications share similar complexity and were carefully chosen to allow subjects to finish the experimental task within 90 minutes.…”

Section: Target Applications and Crosscutting Concernsmentioning

confidence: 99%

“…Investigations of concern identification and code smells: Recent studies [12,25] investigated mistakes in the projection of concerns on code -a key task in concern refactoring. For instance, Figueiredo et al [12] noticed that programmers are conservative when projecting concerns, i.e.…”

Section: Related Workmentioning

confidence: 99%

“…For instance, Figueiredo et al [12] noticed that programmers are conservative when projecting concerns, i.e. they make omissions of concern-to-elements assignments.…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Avoiding Code Pitfalls in Aspect-Oriented Programming

Alves

Figueiredo

Ferrari

2014

Programming Languages

Self Cite

View full text Add to dashboard Cite

Abstract. Aspect-Oriented Programming (AOP) is a maturing technique that requires a good comprehension of which types of mistakes programmers make during the development of applications. Unfortunately, the lack of such knowledge seems to represent one of the reasons for the cautious adoption of AOP in real software development projects. Based on a series of experiments, this paper reports a catalogue of code pitfalls that are likely to lead programmers to make mistakes in AOP. Each experiment required the aspectization (i.e. refactoring) of a crosscutting concern in one object-oriented application. Six rounds of the experiment provided us with the data of 80 aspect-oriented (AO) implementations where three crosscutting concerns were aspectized in three applications. We developed a prototype tool to warn programmers of the code pitfalls during refactoring activities.

show abstract

Section: Target Applications and Crosscutting Concernsmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Avoiding Code Pitfalls in Aspect-Oriented Programming

Alves

Figueiredo

Ferrari

2014

Programming Languages

Self Cite

View full text Add to dashboard Cite

show abstract

“…On the other hand, the seed mappings of the RAWeb family were about 10% for all the assessed features. This occurs because the functional features are often domain-specific and they are realized by a set of specific modules, which are not widely scattered in program families [6,58]. On the basis of this coverage level, our heuristics have achieved good results in terms of precision and recall (Section 6.3).…”

Section: Limitationsmentioning

confidence: 99%

Heuristic expansion of feature mappings in evolving program families

et al. 2013

Self Cite

View full text Add to dashboard Cite

SUMMARYEstablishing explicit mappings between features and their implementation elements in code is one of the critical factors to maintain and evolve software systems successfully. This is especially important when developers have to evolve program families, which have evolved from one single core system to similar but different systems to accommodate various requirements from customers. Many techniques and tools have emerged to assist developers in the feature mapping activity. However, existing techniques and tools for feature mapping are limited as they operate on a single program version individually. Additionally, existing approaches are limited to recover features on demand, that is, developers have to run the tools for each family member version individually. In this paper, we propose a cohesive suite of five mapping heuristics addressing those two limitations. These heuristics explore the evolution history of the family members in order to expand feature mappings in evolving program families. The expansion refers to the action of automatically generating the feature mappings for each family member version by systematically considering its previous change history. The mapping expansion starts from seed mappings and continually tracks the features of the program family, thus eliminating the need of on demand algorithms. Additionally, we present the MapHist tool that provides support to the application of the proposed heuristics. We evaluate the accuracy of our heuristics through two evolving program families from our industrial partners. Copyright © 2013 John Wiley & Sons, Ltd.

show abstract

“…Although their study was carefully conducted, their linking methodology is a serious threat to internal validity, as they point out; independent means of investigating crosscutting concerns are warranted. Figueiredo et al [12] conducted five controlled experiments to ascertain how well people can map code to concerns; they found that developers tend to underreport which concerns are present in a given piece of code, that all concern-based measures also lead to such biases, but that coarse-grained scattering measures are less sensitive to poor mappings from code to concerns. We take this as support that utilizing simple measures of scattering arising directly from Mozilla's repository may help avoid biases.…”

Section: "Do Crosscutting Concerns Cause Defects?"mentioning

confidence: 99%

Do crosscutting concerns cause modularity problems?

Walker

Rawal

Sillito

2012

Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering

View full text Add to dashboard Cite

It has been claimed that crosscutting concerns are pervasive and problematic, leading to difficulties in program comprehension, evolution, and long-term design degradation. To consider whether this theory bears out, we examine the patch history of the Mozilla project over a period of a decade to consider whether crosscutting concerns exist therein and whether we can see evidence of problems arising from them. Mozilla is an interesting case, due to its longevity; size; polylingual nature; and use of a patch review process, which maintains strong connections between issue reports and the patches that are intended to address each. We perform several statistical analyses of the over 200,000 patches submitted to address over 90,000 issues reported in this time period. We find that 90% of patches show little or no evidence of scattering, that the scattering of a patch tends to decrease slightly upon review on average, and that the system shows at worst a slow increase of average scattering over time.

show abstract

On the impact of crosscutting concern projection on code measurement

Cited by 14 publications

References 20 publications

Avoiding Code Pitfalls in Aspect-Oriented Programming

Avoiding Code Pitfalls in Aspect-Oriented Programming

Heuristic expansion of feature mappings in evolving program families

Do crosscutting concerns cause modularity problems?

Contact Info

Product

Resources

About