Towards an aspect-oriented language module

Molderez, Tim; Meyers, Bart; Janssens, Dirk; Vangheluwe, Hans

doi:10.1145/2162037.2162044

Cited by 3 publications

(2 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Based on Xu's aspect-oriented PrT nets (Xu and Nygard, 2006) and Nagy's et al (2005) aspect relations definitions, Guan et al (2008) proposed solutions to resolve the problems about aspect-aspect correctness that may exist among the aspect nets. Molderez et al (2012) presented the aspect-oriented extension to Petri nets. They defined stereotypes for places and transitions, and introductions in an advice.…”

Section: Aspect-oriented Correctnessmentioning

confidence: 99%

Correctness of aspect-oriented business process modeling

Wang

Zhang

et al. 2018

BPMJ

View full text Add to dashboard Cite

Purpose -Business process models, while primarily intended for process documentation, communication, and improvement, are often also used as input for developing process-oriented software systems (Ouyang et al., 2009). Ensuring correctness, handling complexity, and improving reusability and maintainability of business process models are important for all these goals. The purpose of this paper is to propose an aspect-oriented business process modeling and correctness controlling method based on Petri nets to satisfy these goals. Design/methodology/approach -The aspect-oriented paradigm provides a proper mechanism to modularization, and thus reduces the complexity of models, and also improves reusability and maintainability. However, weaving aspects into base processes may bring in mistakes or errors. To ensure correctness of modeling, this paper presents a formal approach to modeling aspect-oriented business processes and a method to ensure modeling correctness. Petri net is used as the process modeling language and its analysis techniques are applied to analyze the correctness of modeling. Two types of correctness, specifically, aspect-aspect correctness and base-aspect correctness are analyzed. A real banking process model is studied systematically in the case study to evaluate the approach and the performance assessments are conducted to show the cost and effect of the approach. Findings -Designing aspect-oriented business process models help organizations reusing the model elements to reduce redundancy of their model repository, improving their maintainability, and supporting them to adapt to the changes of business requirements with flexible modeling. It is important to stress that the correctness of business process modeling is important in ensuring the quality of the models, especially in the safety-critical business domains, such as financial business domain. Originality/value -In this paper, separation of concerns is used to separate the cross-cutting activities and core activities in accordance with the different functions of these activities, and an approach to modeling aspect-oriented business processes is proposed. First, the cross-cutting activities are encapsulated as aspects, while core business activities are modeled as base processes. Then, according to the correctness requirements of business process models, based on the weaving mechanisms of aspect-oriented approach, weaving correctness is defined. Weaving correctness controlling methods between multi-aspects and between aspects and base processes are designed. Errors or mistakes of aspect-oriented business process modeling are prevented during the procedure of modeling to ensure error-free business process modeling.

show abstract

Section: Aspect-oriented Correctnessmentioning

confidence: 99%

Correctness of aspect-oriented business process modeling

Wang

Zhang

et al. 2018

BPMJ

View full text Add to dashboard Cite

show abstract

“…Aspects. Several languages have been proposed to define aspects for a variety of modelling languages, ranging from general-purpose like UML [17,35], to domain-specific ones like Petri nets [22,37] and Building Information Models (BIM) [18]. In most cases, aspects are defined using graphical patterns, thus pointcuts require pattern matching while advices and introductions imply pattern creation.…”

mentioning

confidence: 99%

Towards the Systematic Construction of Domain-Specific Transformation Languages

Cuadrado

Guerra

Lara

2014

Modelling Foundations and Applications

View full text Add to dashboard Cite

El acceso a la versión del editor puede requerir la suscripción del recurso Access to the published version may require subscription Towards the Systematic Construction of Domain-Specific Transformation LanguagesJesús Sánchez Cuadrado, Esther Guerra, and Juan de Lara Universidad Autónoma de Madrid (Spain) Abstract. General-purpose transformation languages, like ATL or QVT, are the basis for model manipulation in Model-Driven Engineering (MDE). However, as MDE moves to more complex scenarios, there is the need for specialized transformation languages for activities like model merging, migration or aspect weaving, or for specific domains of wide use like UML. Such domain-specific transformation languages (DSTLs) encapsulate transformation knowledge within a language, enabling the reuse of recurrent solutions to transformation problems. Nowadays, many DSTLs are built in an ad-hoc manner, which requires a high development cost to achieve a full-featured implementation. Alternatively, they are realised by an embedding into general-purpose transformation or programming languages like ATL or Java. In this paper, we propose a framework for the systematic creation of DSTLs. First, we look into the characteristics of domain-specific transformation tools, deriving a categorization which is the basis of our framework. Then, we propose a domain-specific language to describe DSTLs, from which we derive a ready-to-run workbench which includes the abstract syntax, concrete syntax and translational semantics of the DSTL.

show abstract

Using aspect-oriented state machines for detecting and resolving feature interactions

2012

View full text Add to dashboard Cite

Composing different features in a software system may lead to conflicting situations. The presence of one feature may interfere with the correct functionality of another feature, resulting in an incorrect behavior of the system. In this work we present an approach to manage feature interactions. A formal model, using Finite State Machines (FSM) and Aspect-Oriented (AO) technology, is used to specify, detect and resolve features interactions. In fact aspects can resolve interactions by intercepting the events which causes troubleshoot. Also a Domain-Specific Language (DSL) was developed to handle Finite State Machines using a pattern matching technique.

show abstract

Towards an aspect-oriented language module

Cited by 3 publications

References 6 publications

Correctness of aspect-oriented business process modeling

Correctness of aspect-oriented business process modeling

Towards the Systematic Construction of Domain-Specific Transformation Languages

Using aspect-oriented state machines for detecting and resolving feature interactions

Contact Info

Product

Resources

About