Aspect-Oriented Modeling: Bridging the Gap between Implementation and Design

Elrad, Tzilla; Aldawud, Omar; Bader, Atef

doi:10.1007/3-540-45821-2_12

Cited by 60 publications

(42 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In general, aspect oriented languages are designed to separate crosscutting concerns from other concerns and modularize crosscutting ones as an aspect (Kiczales et al, 1997;Elrad et al, 2002). Then, supporting tools (often called aspect weavers) weave aspects into the other parts of an application to complete it.…”

Section: Ballad: the Proposed Aspect Oriented Languagementioning

confidence: 99%

Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

Oba

Wada

Suzuki³

2011

Journal of Database Management

View full text Add to dashboard Cite

In Service Oriented Architecture (SOA), each application is often designed with a set of reusable services and a business process. In order to retain the reusability of services, it is important to separate non-functional properties of applications (e.g., security and reliability) from their functional properties. This paper investigates an end-to-end model-driven development framework that separates non-functional properties from functional properties and consistently manages them from high-level business processes to low-level implementation configurations. This framework proposes two key components: (1) a programming language, called BALLAD, for a new per-process strategy to specify non-functional properties for business processes and (2) a graphical modeling method, called FM-SNFPs, to define a series of constraints among non-functional properties. BALLAD leverages the notion of aspects in aspect oriented programming/modeling. Each aspect is used to specify a set of non-functional properties that crosscut multiple services in a business process. FM-SNFPs leverages the notion of feature modeling in order to explicitly define constraints among non-functional properties such as dependency and mutual exclusion constraints. BALLAD and FM-SNFPs can free application developers from manually specifying, maintaining and validating non-functional properties and constraints for services one by one, thereby reducing the burdens/costs in development and maintenance of service-oriented applications. This paper describes the design details of BALLAD and FM-SNFPs, and demonstrates how they are used in developing service-oriented applications. Empirical evaluation results show that BALLAD significantly reduces the costs to implement and maintain non-functional properties in service-oriented applications. BALLAD and FM-SNFPs are designed and implemented efficient and scalable.

show abstract

Section: Ballad: the Proposed Aspect Oriented Languagementioning

confidence: 99%

Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

Oba

Wada

Suzuki³

2011

Journal of Database Management

View full text Add to dashboard Cite

show abstract

“…The UML Specification [24] includes two behavioral semantics for finite state transition systems: Behavioral State Machines (BSM) and Protocol State Machines (PSM) and several approaches [16,34] use these as a basis for defining aspect semantics.…”

Section: Reusable Aspect Models (Ram)mentioning

confidence: 99%

Aspect-Oriented Development Using Protocol Modeling

McNeile¹,

Roubtsova

2010

Transactions on Aspect-Oriented Software Development VII

View full text Add to dashboard Cite

Abstract. The aim of this paper is to explore the modeling of crosscutting behavioral abstractions. We argue that behavioral aspects can be seen as a particular kind of more general behavioral abstraction called a "mixin". Mixins support a compositional style of modeling, whereby a complete class definition is constructed by composing one or more mixins each of which represents a partial definition of the class. If used as the replacement for inheritance, mixins can provide an expressive power equivalent to multiple inheritance. In this paper we use a modeling semantics called Protocol Modeling to illustrate how mixins can be used to represent behavioral aspects. We use the Crisis Management System case to illustrate the Protocol Modeling approach, and describe how the model can be executed to give early validation of its behavior. We discuss the extent to which the Protocol Modeling approach is scalable to large problems, is suitable for evolutionary development and supports correctness analysis and testing.

show abstract

“…A clear candidate approach to address this issue, therefore, is that proposed by Multi-Dimensional Separation of Concerns (MDSoC) [21], and seconded in Viewpoints [7], aspect-oriented modeling (AOM) or early aspects (EA) [5,17]. These approaches share common ideas, and allow for the separation of functional and extra-functional characteristics of the systems at design time, providing a base for the solution presented in this paper.…”

Section: Introductionmentioning

confidence: 99%

Domain-Specific Multi-modeling of Security Concerns in Service-Oriented Architectures

Gallino

Miguel

Briones

et al. 2012

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. As a common reference for many in-development standards and execution frameworks, special attention is being paid to ServiceOriented Architectures. SOAs modeling, however, is an área in which a consensus has not being achieved. Currently, standardization organizations are defining proposals to offer a solution to this problem. Nevertheless, until very recently, non-functional aspects of services have not been considered for standardization processes. In particular, there exists a lack of a design solution that permits an independent development of the functional and non-functional concerns of SOAs, allowing that each concern be addressed in a convenient manner in early stages of the development, in a way that could guarantee the quality of this type of systems. This paper, leveraging on previous work, presents an approach to intégrate security-related non-functional aspects (such as confidentiality, integrity, and access control) in the development of services.

show abstract

Aspect-Oriented Modeling: Bridging the Gap between Implementation and Design

Cited by 60 publications

References 6 publications

Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

Leveraging Early Aspects in End-to-End Model Driven Development for Non-Functional Properties in Service Oriented Architecture

Aspect-Oriented Development Using Protocol Modeling

Domain-Specific Multi-modeling of Security Concerns in Service-Oriented Architectures

Contact Info

Product

Resources

About