Browsing by Author "Kienzle, Jorg"

Now showing 1 - 5 of 5
  • No Thumbnail Available
    ItemMetadata only
    Concern-Oriented Software Design
    (Springer, 2013) Alam, Omar; Kienzle, Jorg; Mussbacher, Gunter
    There exist many solutions to solve a given design problem, and it is difficult to capture the essence of a solution and make it reusable for future designs. Furthermore, many variations of a given solution may exist, and choosing the best alternative depends on application-specific high-level goals and non-functional requirements. This paper proposes Concern-Oriented Software Design, a modelling technique that focuses on concerns as units of reuse. A concern groups related models serving the same purpose, and provides three interfaces to facilitate reuse. The variation interface presents the design alternatives and their impact on non-functional requirements. The customization interface of the selected alternative details how to adapt the generic solution to a specific context. Finally, the usage interface specifies the provided behaviour. We illustrate our approach by presenting the concern models of variations of the Observer design pattern, which internally depends on the Association concern to link observers and subjects.
  • No Thumbnail Available
    ItemMetadata only
    Integrating protocol modelling into reusable aspect models
    (ACM, 2013) Ayed, Abir; Kienzle, Jorg
    Aspect-oriented modelling approaches, e.g. the multi-view modelling approach Reusable Aspect Models (RAM), advocate to model concerns separately, and then to use model composition to create complex models in which these concerns are intertwined. In such a context, specifying the composition of the models is a non-trivial task, in particular when it comes to specifying the composition of behavioural models. This is the case for RAM message views, which define behaviour using sequence diagrams. In this paper we describe how we added an additional behavioural view to RAM -- the state view -- that specifies the allowed invocation protocol of class instances.. We discuss why Protocol Modelling, a compositional modelling approach based on state diagrams, is an ideal notation to specify such a state view, and show how we added support for protocol modelling to the RAM metamodel. Finally, we demonstrate how to model using the new state views by means of an example, and explain how state views can be exploited to verify the correctness of compositions.
  • No Thumbnail Available
    ItemMetadata only
    On the challenges of composing multi-view models
    (First Workshop On the Globalization of Modeling Languages, 2013) Schottle, Matthias; Kienzle, Jorg
  • No Thumbnail Available
    ItemMetadata only
    Reusing software design models with TouchRAM
    (ACM, 2013) Kienzle, Jorg
    TouchRAM is a multitouch-enabled tool for agile software design modelling aimed at developing scalable and reusable software design models. This paper briefly summarizes the main features of the Reusable Aspect Models modelling approach that TouchRAM is based on, and then describes how the tool is used during the design process to incrementally elaborate a complex software design model.
  • No Thumbnail Available
    ItemMetadata only
    TouchRAM: A Multitouch-Enabled Tool for Aspect-Oriented Software Design
    (Springer, 2012) Abed, Wisam Al; Bonnet, Valentin; Schottle, Matthias; Yildirim, Engin; Alam, Omar; Kienzle, Jorg
    This paper presents TouchRAM, a multitouch-enabled tool for agile software design modeling aimed at developing scalable and reusable software design models. The tool gives the designer access to a vast library of reusable design models encoding essential recurring design concerns. It exploits model interfaces and aspect-oriented model weaving techniques as defined by the Reusable Aspect Models (RAM) approach to enable the designer to rapidly apply reusable design concerns within the design model of the software under development. The paper highlights the user interface features of the tool specifically designed for ease of use, reuse and agility (multiple ways of input, tool-assisted reuse, multitouch), gives an overview of the library of reusable design models available to the user, and points out how the current state-of-the-art in model weaving had to be extended to support seamless model reuse.