Archface4COP: Architectural interface for context-oriented programming

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Context-awareness plays an important role in developing flexible and evolvable applications such as self-* systems (e.g., self-adaptive, self-healing, and self-management systems). However, it is not easy to design and implement such a context-aware system, because its software architecture is dynamically changed. That is, software components constituting a system and their connection structure can be dynamically changed. As a result, it is hard to check whether or not a design model is correctly implemented and its context-dependent behavior is faithful to the design. To deal with this problem, we introduce Archface4COP, an architectural interface mechanism for COP (Context-Oriented Programming). Archface4COP exposes architectural points shared between UML-based design models and code written in COP languages. Architectural points represent COP-specific events such as layer in, layer out, layered message send, and layered message receive. These points are important to represent an abstract structure of software architecture focusing on context-awareness. We can verify whether or not a design model and its code can co-evolve each other by checking an Archface4COP interface.

Original languageEnglish
Title of host publicationProceedings of the 5th International Workshop on Context-Oriented Programming, COP 2013
DOIs
Publication statusPublished - 2013
Event5th International Workshop on Context-Oriented Programming, COP 2013 - Montpellier, France
Duration: Jul 2 2013Jul 2 2013

Publication series

NameProceedings of the 5th International Workshop on Context-Oriented Programming, COP 2013

Other

Other5th International Workshop on Context-Oriented Programming, COP 2013
CountryFrance
CityMontpellier
Period7/2/137/2/13

All Science Journal Classification (ASJC) codes

  • Software

Fingerprint Dive into the research topics of 'Archface4COP: Architectural interface for context-oriented programming'. Together they form a unique fingerprint.

Cite this