Designing and Weaving Aspect-Oriented Executable UML Models.

Fuentes, Lidia; Sánchez, Pablo

doi:10.5381/jot.2007.6.7.a5

Cited by 30 publications

(40 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There is a lack of automated tool support when it comes to AOM. Weavers for AOM exist but are typically in-house built or implemented within a testing framework and not available, [12,21,27,45,49,54]. Robustness is defined as "The degree to which a system or component can function correctly in the presence of invalid inputs or stressful environment conditions" [1].…”

Section: Example Systemmentioning

confidence: 99%

Using mutation to design tests for aspect-oriented models

Lindström

Offutt

Sundmark

et al. 2017

Information and Software Technology

View full text Add to dashboard Cite

Using mutation to design tests for aspect-oriented models. Technology, http://dx.doi.org/10. 1016/j.infsof.2016.04.007 Access to the published version may require subscription. N.B. When citing this work, cite the original published paper. Information and Software AbstractContext: Testing for properties such as robustness or security is complicated because their concerns are often repeated in many locations and muddled with the normal code. Such "cross-cutting concerns" include things like interrupt events, exception handling, and security protocols. Aspect-oriented (AO) modeling allows developers to model the cross-cutting behavior independently of the normal behavior, thus supporting model-based testing of cross-cutting concerns. However, mutation operators defined for AO programs (source code) are usually not applicable to AO models (AOMs) and operators defined for models do not target the AO features.Objective: We present a method to design abstract tests at the aspect-oriented model level. We define mutation operators for aspect-oriented models and evaluate the generated mutants for an example system. Method: AOMs are mutated with novel operators that specifically target the AO modeling features. Test traces killing these mutant models are then generated. The generated and selected traces are abstract tests that can be transformed to concrete black-box tests and run on the implementation level, to evaluate the behavior of the woven cross-cutting concerns (combined aspect and base models). Results: This paper is a significant extension of our paper at Mutation 2015. We present a complete fault model, additional mutation operators, and a thorough analysis of the mutants generated for an example system. Conclusions: The analysis shows that some mutants are stillborn (syntactically illegal) but none is equivalent (exhibiting the same behavior as the original model). Additionally, our AOM-specific mutation operators can be combined with pre-existing operators to mutate code or models without any overlap.

show abstract

Section: Example Systemmentioning

confidence: 99%

Using mutation to design tests for aspect-oriented models

Lindström

Offutt

Sundmark

et al. 2017

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…This system has previously been used in AOSD literature to explain some AOM notations (e.g., [25]). It has to be emphasized here that by selection of this example system, our intention is not to prove the strength of the selected modeling notations, since it has already been shown by means of the case studies and modeling examples evaluated in other reviews such as [18].…”

Section: Modeling Example: the Online Book Store Systemmentioning

confidence: 99%

“…However, following the presentation of [25], we will focus on the ordering of books, which is described below: 1) Ordering of books use case starts by the customer selecting a book and its desired quantity.…”

Section: Modeling Example: the Online Book Store Systemmentioning

confidence: 99%

Reusable Aspect Models versus Theme/UML: the Aspect-Oriented Code Generation Perspective

Mehmood

Jawawi²

2013

IJSEIA

View full text Add to dashboard Cite

show abstract

“…As a consequence, inaccuracies and errors contained in application models are not detected and fixed at the design level, and may therefore be propagated to the implementation level, where detecting and fixing them can be more complex and expensive [2,7] This paper presents a process for designing and implementing context-awareness pervasive applications that alleviate these problems. We propose using the aspect-oriented executable modelling (AOEM) UML profile [16] for designing and simulating pervasive applications. This profile constitutes the basis for debugging these models at design time, before moving into an implementation.…”

Section: Introductionmentioning

confidence: 99%

Aspect-oriented design and implementation of context-aware pervasive applications

Fuentes

Gámez

Sánchez

2009

Innovations Syst Softw Eng

Self Cite

View full text Add to dashboard Cite

Pervasive applications must be aware of the contexts where they are executed. These contexts may vary greatly and change quickly. Two main problems are associated with this issue: (1) context-awareness is a crosscutting concern that cannot be well-encapsulated in a single module using traditional technologies, thus hindering software maintenance and reusability; and (2) reasoning about application design correctness can be complex due to the number and diversity of potential contexts where a pervasive application could be executed. In order to overcome these problems, we present a process for the design and implementation of context-aware pervasive applications that uses aspect-orientation and executable modelling in order to overcome these shortcomings. Aspect-oriented techniques contribute to the encapsulation of crosscutting concerns, such as context-awareness, into well-localized modules. Executable modelling helps engineers to reason about application design by executing the design models in different contexts and situations. Pervasive applications are modelled using the aspect-oriented executable modelling UML 2.0 profile, executed at the modelling level for testing purposes, and then mapped into an aspect-oriented middleware platform for pervasive applications. This process is illustrated using a

show abstract

Designing and Weaving Aspect-Oriented Executable UML Models.

Cited by 30 publications

References 22 publications

Using mutation to design tests for aspect-oriented models

Using mutation to design tests for aspect-oriented models

Reusable Aspect Models versus Theme/UML: the Aspect-Oriented Code Generation Perspective

Aspect-oriented design and implementation of context-aware pervasive applications

Contact Info

Product

Resources

About