Supporting automated software re-engineering using re-aspects

Mohamed Almorsy, John Grundy, Amani S. Ibrahim

Research output: Chapter in Book/Report/Conference proceedingConference PaperResearchpeer-review

4 Citations (Scopus)

Abstract

System maintenance, including omitting an existing system feature e.g. buggy or vulnerable code, or modifying existing features, e.g. replacing them, is still very challenging. To address this problem we introduce the "re-aspect" (re-engineering aspect), inspired from traditional AOP. A re-aspect captures system modification details including signatures of entities to be updated; actions to apply including remove, modify, replace, or inject new code; and code to apply. Re-aspects locate entities to update, entities that will be impacted by the given update, and finally propagate changes on the system source code. We have applied our re-aspects technique to the security re-engineering problem and evaluated it on a set of open source .NET applications to demonstrate its usefulness.

Original languageEnglish
Title of host publication2012 27th IEEE/ACM International Conference on Automated Software Engineering, ASE 2012 - Proceedings
Pages230-233
Number of pages4
DOIs
Publication statusPublished - 2012
Externally publishedYes
EventAutomated Software Engineering Conference 2012 - Atlantic Congress Hotel, Essen, Germany
Duration: 3 Sept 20127 Sept 2012
Conference number: 27th
http://www.ase-conferences.org/ase/past/ase2012/index.html (Conference website)
https://dl.acm.org/doi/proceedings/10.1145/2351676 (Proceedings)

Conference

ConferenceAutomated Software Engineering Conference 2012
Abbreviated titleASE 2012
Country/TerritoryGermany
CityEssen
Period3/09/127/09/12
OtherIEEE/ACM International Conference on Automated Software Engineering, ASE 2012
Internet address

Keywords

  • Change impact analysis
  • Re-aspects
  • Software evolution
  • System reengineering

Cite this