Architectural Aspects of Architectural Aspects

Cuesta, Carlos E.; Romay, María del Pilar; Fuente, Pablo de la; Barrio, Manuel Gértrudix

doi:10.1007/11494713_18

Cited by 32 publications

(19 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This allows a developer to focus on structures and the dynamics between components separately from component implementation. Various architecture description languages (ADLs) and modelling and development techniques have been proposed (Medvidovic & Taylor, 1997;Garlan & Schmerl, 2006;Cuesta et al, 2005;Oquendo et al, 2005). An architectural model captures common concepts found in a variety of architectural description languages: components provide computation, interfaces provide access to black-box components, and connectors provide connections between components.…”

Section: ) Architectural Modellingmentioning

confidence: 99%

Quality-Aware Model-Driven Service Engineering

Pahl

Bošković

Barrett

et al. 2009

Model-Driven Software Development

View full text Add to dashboard Cite

Abstract. Service engineering and service-oriented architecture as an integration and platform technology is a recent approach to software systems integration. Quality aspects ranging from interoperability to maintainability to performance are of central importance for the integration of heterogeneous, distributed service-based systems. Architecture models can substantially influence quality attributes of the implemented software systems. Besides the benefits of explicit architectures on maintainability and reuse, architectural constraints such as styles, reference architectures and architectural patterns can influence observable software properties such as performance. Empirical performance evaluation is a process of measuring and evaluating the performance of implemented software. We present an approach for addressing the quality of services and service-based systems at the model-level in the context of model-driven service engineering. The focus on architecture-level models is a consequence of the black-box character of services.Keywords. Service-oriented architecture, model-driven development, software product quality, architectural modelling, patterns, empirical performance evaluation. 1) IntroductionWith software services becoming a strategic capability for the software sector, a service engineering discipline needs to address service development problems based on suitably flexible modelling and composition support. An increasing need for flexibility in this area is caused by changing user requirements, evolving services, and varying deployment contexts. Software services are application that are provided 'as-is' at certain locations in order to be integrated into existing applications or composed to larger systems. Essential in this process are abstract descriptions or models of the service functionality and other service characteristics. This makes model-driven software development both a highly suitable, but actually also necessary framework to adequately develop service-based software systems. Composition and integration-oriented modelling has already been successfully utilised for model-driven services development. The high complexity of modern software makes its development costly and error-prone. Model-driven development (MDD) is an approach that deals with software complexity by making software models primary artefacts of the software development process. MDD utilises two aspects of models. Firstly, in various engineering disciplines, predictions about a software system can be made based on a model. Secondly, even complete implementations for different platforms and languages can be generated from models.The aim of this chapter is to address quality aspects of model-driven service engineering. We address two specific facets of quality assurance for model-driven software development: the model-driven design and development of high-quality software and the identification of quality aspects in model-driven development. Some specific aspects that we discuss in the context of quality aspects in model-d...

show abstract

Section: ) Architectural Modellingmentioning

confidence: 99%

Quality-Aware Model-Driven Service Engineering

Pahl

Bošković

Barrett

et al. 2009

Model-Driven Software Development

View full text Add to dashboard Cite

show abstract

“…It is with no doubt intuitive by exploiting the analogy with implementation-level concepts of AspectJ. Still, the analogy might turn out to be problematic, it could be assumed as straightforward translation of the concepts in the AspectJ model [14]. Such direct translation is difficult since software architectures use completely different concepts.…”

Section: Definition Of Architectural Concernmentioning

confidence: 99%

Relating architectural views with architectural concerns

Boucké

Holvoet

2006

Proceedings of the 2006 International Workshop on Early Aspects at ICSE

View full text Add to dashboard Cite

Architectural views are at the foundation of software architecture and are used to describe the system from different perspectives. However, some architectural concerns crosscut the decomposition of the architecture in views. The drawbacks of crosscutting with respect to architectural views is similar to the drawbacks with respect to code, i.e. hampering reuse, maintenance and evolution. This paper investigates the relations between architectural concerns and views to identify why concerns tend to crosscut. We propose to extend the architectural description with slices and composition mechanisms to prevent this crosscutting and perform an initial exploration of these concepts in an Online Auction system. Within this limited setting the first results look promising to better separate concerns that otherwise would crosscut the views.

show abstract

“…Below, we relate our work to the most relevant and closely matching ones. Further analysis can be found from extensive surveys in [2,7].…”

Section: Related Workmentioning

confidence: 99%

A concern architecture view for aspect-oriented software design

Katara

Katz

2006

Softw Syst Model

View full text Add to dashboard Cite

Although aspect-oriented programming is becoming popular, support for the independent description of aspect designs and for the incremental design of aspects themselves has been neglected. A conceptual framework for the design of aspects is presented, where aspects are viewed as augmentations that map an existing design into a new one with changes or additions. The principles of a Concern Architecture model are defined both to group designs of aspects, and to make explicit their dependencies and potential interferences in the design of a system with multiple aspects. The aspects are described generically, where any design element can be either required or provided. The required elements resemble formal parameters, and their binding to an existing design shows the context in which the provided parts are to modify that design. Overlap and a partial order among aspects and concerns are visualized in a Concern Architecture Diagram. An instantiation of the ideas as a UML profile is outlined, and the design of a digital sound recorder is used to demonstrate the utility of the approach.

show abstract

Architectural Aspects of Architectural Aspects

Cited by 32 publications

References 25 publications

Quality-Aware Model-Driven Service Engineering

Quality-Aware Model-Driven Service Engineering

Relating architectural views with architectural concerns

A concern architecture view for aspect-oriented software design

Contact Info

Product

Resources

About