Aspect Validation Using Model Checking

Katz, Shmuel; Sihman, Marcelo

doi:10.1007/978-3-540-39910-0_18

Cited by 13 publications

(7 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [20], model checking tasks are automatically generated for the augmented system that results from each weaving of an aspect. That approach has the disadvantage of having to treat the augmented system, but offers the benefit that needed annotations and set-up need only be prepared once.…”

Section: Modular Aspect Verificationmentioning

confidence: 99%

MAVEN: modular aspect verification and interference analysis

Goldman¹,

Katz

2010

Form Methods Syst Des

Self Cite

View full text Add to dashboard Cite

Aspects are program modules that include descriptions of key events (called joinpoints) and code segments (called advice) to be executed at those key events when the aspect is bound (woven) to an underlying system. The MAVEN tool verifies the correctness of an aspect relative to its specification, independently of any specific underlying system to which it may be woven, and also allows establishing noninterference among aspects, or detecting potential interference. The specification includes assumptions about properties of the underlying system, and guaranteed properties of any system after the aspect is woven into it. The approach is based on model checking of a state machine constructed using the linear temporal logic (LTL) description of the assumptions, a description of the join-points, and the state machine of the aspect advice. The tableau of the LTL assumption is used in a unique way, as a representative of any underlying system satisfying the assumptions. This is the first technique for once-and-for-all verification of an aspect relative to its specification, thereby increasing the modularity of proofs for systems with aspects. The individual correctness proofs along with proofs of interference freedom are appropriate for a library of reusable aspects, when multiple aspects are to be woven to a system.

show abstract

Section: Modular Aspect Verificationmentioning

confidence: 99%

MAVEN: modular aspect verification and interference analysis

Goldman¹,

Katz

2010

Form Methods Syst Des

Self Cite

View full text Add to dashboard Cite

show abstract

“…In a series of papers, Katz and his group have addressed various issues of model-checking aspect-oriented code. In [9], model checking tasks are automatically generated for the woven code of aspect-oriented programs. In [8], they treat crosscutting scenarios as aspects and use model checking to prove the conformance between the scenario-based specification of aspects and the systems with aspects woven into them.…”

Section: Related Workmentioning

confidence: 99%

Model Checking Aspect-Oriented Design Specification

Alsmadi

2007

31st Annual International Computer Software and Applications Conference - Vol. 1- (COMPSAC 2007)

View full text Add to dashboard Cite

show abstract

“…Properties of the composed system are verified using the LTSA model checker. The work in [27] also applies model-checking techniques. This project aims at encouraging the reuse of generic aspects to specify collections of aspects which they call superimpositions.…”

mentioning

confidence: 99%

Design-Level Detection of Interactions in Aspect-UML Models Using Alloy.

Mostefaoui¹,

Vachon²

2007

JOT

View full text Add to dashboard Cite

Aspect-oriented (AO) programming has emerged as a promising paradigm to improve modularity by providing mechanisms to capture and execute crosscutting concerns in software applications. Among others, AO allows developers to incrementally modify the behavior of a base program, by introducing aspects which implement crosscutting concerns having effects at various points throughout a program. Hence, despite the clean separation of concerns in aspect-oriented systems, it remains difficult to predict the effect of a given aspect on this base program. Once woven, does an aspect still achieve what it was intended for? Does it violate base program properties that should be preserved? Does it interfere with the properties of other aspects? These questions address the well known aspect interaction problem, encountered within the AO paradigm. This article tackles the interaction problem in the context of formal AO system model analysis and verification. To be more precise, this work considers AO models written in Aspect-UML (our UML profile). Aspect-UML does not depend on any AO language specific features nor is it associated with any specific development process. This paper first explains how Aspect-UML models can be translated into Alloy, a simple structural first-order logic modeling language which can be formally analyzed. Given this translation, it then demonstrates how Alloy's model analyzer can be used to verify aspect interactions of an Aspect-UML model.

show abstract

Aspect Validation Using Model Checking

Cited by 13 publications

References 13 publications

MAVEN: modular aspect verification and interference analysis

MAVEN: modular aspect verification and interference analysis

Model Checking Aspect-Oriented Design Specification

Design-Level Detection of Interactions in Aspect-UML Models Using Alloy.

Contact Info

Product

Resources

About