Aspects preserving properties

Djoko, Simplice Djoko; Douence, Rémi; Fradet, Pascal

doi:10.1016/j.scico.2011.10.010

Cited by 6 publications

(5 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The presented framework can be extended by integrating the around advices and considering more general kinds of pointcuts by defining them on aspects. It can be also interesting to investigate the relationship between the proposed framework and special aspect classes (like those proposed by [Kat06], [DDF12]). It would be interesting to have a better characterization of the non-violation of pre and postconditions depending on the classes of advices.…”

Section: Resultsmentioning

confidence: 99%

“…It would be interesting to have a better characterization of the non-violation of pre and postconditions depending on the classes of advices. For instance, consider two observing aspects [DDF12] (i.e. aspects that can introduce new instructions and a new local state but do not modify the base system' state and control-flow) which are independent (i.e.…”

Section: Resultsmentioning

confidence: 99%

“…Although this will not affect deeply our modeling, we suppose that the considered aspects are not terminating. Moreover, since defining pointcuts on aspects may lead to a non-terminating composition even for an observer aspect (see [DDF12] for more details), we consider only pointcuts that concern the base system. We will show in this step that aspect interaction problem can be transformed into a verification of a generic LTL property.…”

Section: An Overview Of the Proposed Approachmentioning

confidence: 99%

“…This one has the form of uv ω if we consider infinite executions or uv * if finite executions are rather considered (u and v are finite paths). Actually, the woven system fails to preserve the base system properties if one of the two problems occurs: either the composition cannot terminate which means that the final state of the base system will not be reached (as explained in [DDF12]), or a precondition of a given action is not verified by the current state of the system.…”

Section: Interaction Detection and Verificationmentioning

confidence: 99%

See 3 more Smart Citations

On using pre and postconditions to tackle the aspect scheduling problem by rewriting systems: a design-level approach.

Benouhiba¹,

Boudjedir²

2014

JOT

View full text Add to dashboard Cite

The aspect-oriented paradigm promises separation of crosscutting concerns by modularizing them as aspects. This paradigm allows then weaving aspects upon some points in the base system. Unfortunately, the interaction of aspects may have an undesirable effect on each other and/or on the base system if they are executed in any order. Many works tried to solve this problem but the proposed solutions were either limited to some simple models of aspects or used to check if a set of temporal properties is preserved when aspects are introduced. In this paper, we propose a framework based on extended UML diagrams (class and state/transition diagrams) in order to make the detection of undesirable interaction more powerful and realistic. This framework relies on finite state automata (FSA); it transforms the interaction problem into a reachability issue. In fact, bad interaction is expressed as a generic LTL property which is independent of the system to be verified. This property can be checked using any model-checker like Maude. To concretize the proposed framework, we propose a rewriting system that allows an implicit construction of the FSA of the base system and the aspects in addition to the aspects composition and the weaving mechanism. Therefore, the proposed system defines a translation scheme of UML models into rewriting logic specifications written in Maude language. Thanks to the advances of the on-the-fly technique in Maude, the use of its LTL model-checker avoids a systematic exploration of all possible combinations of the aspects. The approach will be illustrated by a case study in order to explain how it works.

show abstract

Section: Resultsmentioning

confidence: 99%

Section: Resultsmentioning

confidence: 99%

Section: An Overview Of the Proposed Approachmentioning

confidence: 99%

Section: Interaction Detection and Verificationmentioning

confidence: 99%

See 2 more Smart Citations

On using pre and postconditions to tackle the aspect scheduling problem by rewriting systems: a design-level approach.

Benouhiba¹,

Boudjedir²

2014

JOT

View full text Add to dashboard Cite

show abstract

“…The work in [41] considers a problem similar to ours in the concrete setting of aspect-oriented programming. They use a dedicated semantic framework (Common Aspect Semantic Base) and look for the classes of properties preserved in any context by relevant classes of updates (observers, aborters, .…”

Section: Related Workmentioning

confidence: 99%

Static and dynamic property-preserving updates

Bresolin¹,

Lanese²

2021

Information and Computation

View full text Add to dashboard Cite

Systems need to be updated to last for a long time in a dynamic environment, and to cope with changing requirements. The update can be performed both statically, by restarting the system, or dynamically. In both the cases, it is important for updates to preserve the desirable properties of the system under update, while possibly enforcing new ones.Here we consider a simple yet general update mechanism, which replaces a component of the system with a new one. The context, i.e., the rest of the system, remains unchanged. We dene contexts and components as Constraint Automata interacting via either asynchronous or synchronous communication, and we express properties using Constraint Automata too. Then we build most general updates which preserve specic properties, considering both a single property and all the properties satised by the original system, in a given context or in all possible contexts. In order to apply our approach also to dynamic update, we consider the state transfer problem, namely how to nd the state in which the new component should be started to ensure that the overall behaviour is correct.

show abstract

Aspect-Oriented Development of Trustworthy Component-based Systems

Dihego

Sampaio

2015

Theoretical Aspects of Computing - ICTAC 2015

View full text Add to dashboard Cite

Aspects preserving properties

Cited by 6 publications

References 10 publications

On using pre and postconditions to tackle the aspect scheduling problem by rewriting systems: a design-level approach.

On using pre and postconditions to tackle the aspect scheduling problem by rewriting systems: a design-level approach.

Static and dynamic property-preserving updates

Aspect-Oriented Development of Trustworthy Component-based Systems

Contact Info

Product

Resources

About