Object confinement in Object Teams—reconciling encapsulation and flexible integration

introduce invisible links and control flows in an application, which are perceived as an obstacle to understandability, predictability and safety. The resulting trade-off between flexibly structuring crosscutting concerns and rigorously pursuing program safety impedes the usefulness of AOSD for many fields of application. The model of Object Teams combines ideas from many programming languages providing greater expressiveness than each of its predecessors. In this position paper it is argued, that Object Teams also provide strong concepts for encapsulation, which help for modular reasoning about aspect-oriented programs developed in this model. 1 Object Teams in a nutshell The Object Teams programming model [7, 14] has its roots in the concept of Aspectual Components [11]. It has gone through several iterations [12, 5, 6, 17] before its current incarnation as ObjectTeams/Java, an implementation based on a combination of a modified Java compiler and a runtime system performing load-time byte-code adaptation using JMangler [10]. Object Teams combine the expressive power for aspect-oriented software composition in the style of many existing programming languages with a lean language design, which requires the programmer to learn only a minimum of new concepts and syntactical constructs