Designing Software Architectures with an Aspect-Oriented Architecture Description Language

Pérez, Jennifer; Alí, Nour; Carsí, José A.; Ramos, Isidro

doi:10.1007/11783565_9

Cited by 29 publications

(26 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The PRISMA approach [1] proposes a formal model to integrate aspects into Architectural Description Languages (ADL). In fact, aspects are considered since the first stages of the development cycle (i.e.…”

Section: Inter-component Approachesmentioning

confidence: 99%

Review on Formal Approaches for the Verification of Aspect-Oriented Adaptations of Component-Based Systems

Hariati¹,

Meslati²

2017

IJSEIA

View full text Add to dashboard Cite

show abstract

Section: Inter-component Approachesmentioning

confidence: 99%

Review on Formal Approaches for the Verification of Aspect-Oriented Adaptations of Component-Based Systems

Hariati¹,

Meslati²

2017

IJSEIA

View full text Add to dashboard Cite

show abstract

“…PPC's approach applies the advantages of aspectoriented software architectures [15] (see Figure l.a) by defining components as fragment boxes that hook a set of reusable fragments of code-aspects-, which makes components easier to be maintained, and by extension software architectures. Specifically, PPCs take advantage of aspect-oriented concepts to specify the internal variation of components, in such a way that part of its behavior corresponds to the core functionality of a SPL and part of its behavior is specific of a product or set of products from that SPL.…”

Section: A Variability In Software Architecturementioning

confidence: 99%

Model-to-Code Transformation from Product-Line Architecture Models to AspectJ

Díaz

Pérez

Fernández-Sánchez

et al. 2013

2013 39th Euromicro Conference on Software Engineering and Advanced Applications

View full text Add to dashboard Cite

Abstract-Software Product Line Engineering has significant advantages in family-based software development. The common and variable structure for all products of a family is defined through a Product-Line Architecture (PLA) that consists of a common set of reusable components and connectors which can be configured to build the different products. The design of PLA requires solutions for capturing such configuration (variability). The Flexible-PLA Model is a solution that supports the specification of external variability of the PLA configuration, as well as internal variability of components. However, a complete support for product-line development requires translating architecture specifications into code. This complex task needs automation to avoid human error. Since Model-Driven Development allows automatic code generation from models, this paper presents a solution to automatically generate AspectJ code from Flexible-PLA modelspreviously configured to derive specific products. This solution is supported by a modeling framework and validated in a software factory.

show abstract

“…There are two candidate models: scenarios, which represents a candidate model that conforms to the ATRIUM Scenario metamodel; and archmodel, which represents a candidate model that conforms to the selected architectural metamodel to be instantiated. Specifically, we have used the ATRIUM Scenarios and PRISMA [14] metamodels to execute the transformations. In addition, the transformation can define keys to uniquely identify the elements and avoid duplicate instances.…”

Section: Using M2m Transformations For Architectural Stylesmentioning

confidence: 99%

Using Model Transformation Techniques for the Superimposition of Architectural Styles

Navarro

Cuesta

Perry

et al. 2011

Software Architecture

View full text Add to dashboard Cite

Abstract. Software Architecture is a key artifact in the software development process, as it provides a bridge between the requirements of the system-to-be and its final design. Architectural description is therefore a critical step, which can be assisted by the use of Architectural Styles. Styles make it possible to reuse architectural knowledge by providing guidelines for its description, and by constraining the configuration and behavior of the target system. The architect must superimpose these constraints, but this could be an error-prone task unless some kind of automatic support is provided. Therefore, this paper presents a proposal that generates proto-architectures by superimposing architectural styles on the initial requirements' operationalization, using model-to-model (M2M) transformation techniques. Our proposal includes a tool called MORPHEUS, which applies QVT as the transformation language; a real-world example is provided to explain how the superimposition process works, and how the QVT language is used to express these style-based transformations.

show abstract

Designing Software Architectures with an Aspect-Oriented Architecture Description Language

Cited by 29 publications

References 13 publications

Review on Formal Approaches for the Verification of Aspect-Oriented Adaptations of Component-Based Systems

Review on Formal Approaches for the Verification of Aspect-Oriented Adaptations of Component-Based Systems

Model-to-Code Transformation from Product-Line Architecture Models to AspectJ

Using Model Transformation Techniques for the Superimposition of Architectural Styles

Contact Info

Product

Resources

About