There are numerous mechanisms for separation of concerns at the source code level. Three mechanisms that are the focus of recent attention – metadata annotations, pointcuts and advice – can be modeled together with good old-fashioned procedures as providing different kinds of bindings: procedure calls bind program points to operations, annotations bind attributes to program points; pointcuts bi...

Building softwares in a concern oriented fashion can be splited in two main steps : rst deening 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 reeection. This interest is particularly motivated by the natural separation between functional and non-...

Constructing software from components is considered to be a key requirement for managing the complexity of software. Separation of concerns makes only sense if the realizations of these concerns can be composed together effectively into a working program. Various publications have shown that composability of software is far from trivial and fails when components express complex behavior such as...

In the (conventional) OO model, the “separation of concerns” principle is supported basically in three ways: (a) by defining objects as the models of the real-world concepts, which are “naturally” separated from each other; (b) by separating the concerns of providing an abstract object interface and the implementation of it; and © by grouping functions together around objects so that functions ...

Separation of concerns is the main principle of Software Engineering. It represents a key element in the teaching process of any Software Engineering methodology. The paper relates the experience of the University of Namur in introducing the separation of concerns principle in its educational scheme through an extended student project.

Experience with building an architecture for an industrial Automatic Guided Vehicle Transportation System (AGVTS) shows that several essential concerns crosscut the architectural views. To cope with this, a stronger separation proved to be necessary, i.e. using different views for different concerns. In practice this was difficult, since the support for relations between views is very limited. ...