JPIAspectZ: A Formal Specification Language for Aspect-Oriented JPI Applications

Cristian Vidal Silva, RODOLFO HUMBERTO VILLARROEL ACEVEDO, Cristian Pereira Vasquez

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

2 Scopus citations

Abstract

This article proposes and describes JPIAspectZ, a formal language used to write AspectOriented (AO) software specification to support the use of Join Point Interfaces (JPI) between advised classes and aspects. JPIAspectZ looks for a concept and model consistency for a JPI software development process. The main characteristic of JPI is to define explicit associations between aspects and advised classes by means of join point interfaces, so that classes are no longer oblivious of their possible interaction with aspects and as well aspects, for their action effectiveness, do not depend on signatures of advisable class methods. Only JPIAspectZ supports this JPI principle. An application example of JPIAspectZ is presented to analyze the pros and cons of our proposal.

Original languageEnglish
Title of host publicationProceedings - 2014 33rd International Conference of the Chilean Computer Science Society, SCCC 2014
PublisherIEEE Computer Society
Pages128-131
Number of pages4
ISBN (Electronic)9781509004218
DOIs
StatePublished - 1 Sep 2016
Event33rd International Conference of the Chilean Computer Science Society, SCCC 2014 - Talca, Maule, Chile
Duration: 12 Nov 201414 Nov 2014

Publication series

NameProceedings - International Conference of the Chilean Computer Science Society, SCCC
Volume2016-September
ISSN (Print)1522-4902

Conference

Conference33rd International Conference of the Chilean Computer Science Society, SCCC 2014
Country/TerritoryChile
CityTalca, Maule
Period12/11/1414/11/14

Keywords

  • aspects
  • join point interfaces
  • JPI
  • JPIAspectZ

Fingerprint

Dive into the research topics of 'JPIAspectZ: A Formal Specification Language for Aspect-Oriented JPI Applications'. Together they form a unique fingerprint.

Cite this