12,000

We have over 12,000 students, from over 100 countries, within one of the safest campuses in the UK

93%

93% of Lancaster students go into work or further study within six months of graduating

Home > Research > Publications & Outputs > An exploratory study of fault-proneness in evol...
View graph of relations

« Back

An exploratory study of fault-proneness in evolving aspect-oriented programs

Research output: Contribution in Book/Report/ProceedingsPaper

Published

  • Fabiano Ferrari
  • Rachel Burrows
  • Otávio Lemos
  • Alessandro Garcia
  • Eduardo Figueiredo
  • Nelio Cacho
  • Frederico Lopes
  • Nathalia Temudo
  • Liana Silva
  • Sérgio Soares
  • Awais Rashid
  • Paulo Masiero
  • Thais Batista
  • José Maldonado
Publication date2010
Host publicationICSE '10 Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Place of publicationNew York
PublisherACM
Pages65-74
Number of pages10
ISBN (Print)978-1-60558-719-6
Original languageEnglish

Conference

ConferenceInternational Conference on Software Engineering (ICSE 2010)
CityCapetown, South Africa
Period2/05/108/05/10

Conference

ConferenceInternational Conference on Software Engineering (ICSE 2010)
CityCapetown, South Africa
Period2/05/108/05/10

Abstract

This paper presents the results of an exploratory study on the fault- proneness of aspect-oriented programs. We analysed the faults collected from three evolving aspect-oriented systems, all from different application domains. The analysis develops from two different angles. Firstly, we measured the impact of the obliviousness property on the fault-proneness of the evaluated systems. The results show that 40% of reported faults were due to the lack of awareness among base code and aspects. The second analysis regarded the fault-proneness of the main aspect-oriented programming (AOP) mechanisms, namely pointcuts, advices and intertype declarations. The results indicate that these mechanisms present similar fault-proneness when we consider both the overall system and concern- specific implementations. Our findings are reinforced by means of statistical tests. In general, this result contradicts the common intuition stating that the use of pointcut languages is the main source of faults in AOP.