A Conceptual Framework for Adapation

This paper presents a white-box conceptual framework for adaptation that promotes a neat separation of the adaptation logic from the application logic through a clear identification of control data and their role in the adaptation logic. The framework provides an original perspective from which we survey archetypal approaches to (self-)adaptation ranging from programming languages and paradigms, to computational models, to engineering solutions

A Conceptual Framework for Adapation

This paper presents a white-box conceptual framework for adaptation that promotes a neat separation of the adaptation logic from the application logic through a clear identification of control data and their role in the adaptation logic. The framework provides an original perspective from which we survey archetypal approaches to (self-)adaptation ranging from programming languages and paradigms, to computational models, to engineering solutions

A Conceptual Framework for Adapation

We present a white-box conceptual framework for adaptation. We called it CODA, for COntrol Data Adaptation, since it is based on the notion of control data. CODA promotes a neat separation between application and adaptation logic through a clear identification of the set of data that is relevant for the latter. The framework provides an original perspective from which we survey a representative set of approaches to adaptation ranging from programming languages and paradigms, to computational models and architectural solutions

A model driven approach to analysis and synthesis of sequence diagrams

Software design is a vital phase in a software development life cycle as it creates a blueprint for the implementation of the software. It is crucial that software designs are error-free since any unresolved design-errors could lead to costly implementation errors. To minimize these errors, the software community adopted the concept of modelling from various other engineering disciplines. Modelling provides a platform to create and share abstract or conceptual representations of the software system – leading to various modelling languages, among them Unified Modelling Language (UML) and Petri Nets. While Petri Nets strong mathematical capability allows various formal analyses to be performed on the models, UMLs user-friendly nature presented a more appealing platform for system designers. Using Multi Paradigm Modelling, this thesis presents an approach where system designers may have the best of both worlds; SD2PN, a model transformation that maps UML Sequence Diagrams into Petri Nets allows system designers to perform modelling in UML while still using Petri Nets to perform the analysis. Multi Paradigm Modelling also provided a platform for a well-established theory in Petri Nets – synthesis to be adopted into Sequence Diagram as a method of putting-together different Sequence Diagrams based on a set of techniques and algorithms

Recent advances in petri nets and concurrency

CEUR Workshop Proceeding

Weaving of Aspects in Business Process Management

Separation of cross-cutting concerns is an important issue in business process management, where Aspect-Oriented Business Process Modeling (AO-BPM) aims to support this separation through a new form of encapsulation technique. Although different researchers have investigated how these models can be designed to support separation of non-retroactive cross-cutting concerns, there is no study that defines the separation of retroactive ones. The lack of a unified definition of the syntax and the operational semantics for these models hinders their enactment in practice as well. As a result, the perceived usefulness and usability of these approaches have not yet been investigated so far. Thus, this article fills this gap by formalizing an AO-BPM language and the semantics that can support enactment of such models. The semantics is validated through the state-space analysis technique, and the feasibility of the implementation is also demonstrated. The perceived usefulness and easy to use of the AO-BPM is evaluated by applying the Technology Acceptance Model during a workshop session. The result shows that participants perceived the approach usable and easy to use