Auflistung nach Autor:in "Hanenberg, Stefan"
1 - 4 von 4
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragModularizing security related concerns in enterprise applications – A case study with J2EE and aspectJ(NODe 2005 – GSEM 2005, 2005) Zubairov, Renat; Hanenberg, Stefan; Unland, Rainer
- KonferenzbeitragPath expression pointcuts: Abstracting over non-local object relationships in aspect-oriented languages(NODe 2006 – GSEM 2006, 2006) Al-Mansari, Mohammed; Hanenberg, StefanIn aspect-oriented programming, aspects require access to join point information for selecting join points within pointcuts as well as for specifying aspect-specific behavior at such join points within advice. Unfortunately, aspectoriented systems typically provide only local information about join points, i.e. information that is directly accessible from the execution context at the corresponding join points like the target object within a method call. However, there are many situations where the needed information is not directly available and relies on object information that is non-local concerning the execution context at the corresponding join points. As a consequence, developers are forced to specify a number of work-arounds – pointcuts and advice that neither reflect on the conceptual join point selection nor purely on the conceptual aspect behavior. In this paper, we show recurring situations in which "local" join point information is not sufficient for specifying aspects. We propose so called "path expression pointcuts" that permit to abstract over (non-local) object-relationships within pointcuts – and show that this overcomes the problem.
- KonferenzbeitragEine Taxonomie für aspektorientierte Systeme(Software Engineering 2005, 2005) Hanenberg, Stefan; Stein, Dominik; Unland, RainerDie aspektorientierte Softwareentwicklung entwickelte sich aus der Beobachtung heraus, dass eine Vielzahl logisch zusammenhängender Softwareelemente mit Hilfe konventioneller Techniken nicht modularisierbar ist. Eine mangelhafte Modularisierung wiederum reduziert die Verständlichkeit und Wartbarkeit der Software. Aspektorientierte Systeme bieten zusätzliche Konstrukte, um ein höheres Maß an Modularisierung zu ermöglichen. Es existiert bereits eine Reihe von Systemen, welche die aspektorientierte Softwareentwicklung in unterschiedlichsten Ausprägungen unterstützen. Es fehlt jedoch an Kriterien, anhand derer überprüft werden kann, ob ein bestimmtes System die Modularisierung eines gegebenen Anwendungsproblems ermöglicht. In diesem Papier schlagen wir eine Taxonomie aspektorientierter Systeme vor. Anhand derer können zum einen unterschiedliche aspektorientierte Systeme miteinander verglichen werden. Zum anderen ermöglicht die Taxonomie es festzustellen, ob ein System zur Lösung eines gegebenen Problems geeignet ist.
- KonferenzbeitragVisualizing join point selections using interaction-based vs. state-based notations exemplified with help of business rules(Enterprise modelling and information systems architectures, 2005) Stein, Dominik; Hanenberg, Stefan; Unland, RainerIn Aspect-Oriented Software Development, the selection of join points is an essential part. Join point selections identify the points in a program (i.e. in its code, or during its execution) at which aspectual adaptations need to take place. In order to communicate such selections independent of the underlying aspectoriented programming language, it is desirable to visualize join point selections in an appropriate way. In this paper we focus on the appropriateness of interaction diagram-based and state diagram-based visualizations of join point queries, exemplified with help of two business rule examples. As a result, we discover that even if join point queries are based on interactions in the base application, state diagram-based representations are needed to appropriately capture the selection semantic of that query.