Abstract

Building softwares in a concern oriented fashion can be splited in two main steps : first defining each concern separately (or reusing existing ones) and then composing (i.e. integrating) those concerns together. Among existing approaches to support this development scheme, we are interested in reflection. This interest is particularly motivated by the natural separation between functional and non-functional concerns provided by reflection. In this paper, we describe our approach based on reflection. We provide a solution to define and compose reusable non-functional concerns, while minimizing integration efforts. Keywords: Concerns Composition ; Concern Reuse ; Metaclasses ; Reflection ; Smalltalk. 1 Introduction Separation of concerns [Dij76] [HL95] is the foundation for the programming paradigm that we named Concern Oriented Programming (COP). This programming paradigm consists of separating concerns before composing (i.e. integrating) them to produce softwares. Once concer...

Citations