Preserving Architectural Choices throughout the Component-based Software Development Process

Authors:
Chouki Tibermacine;Regis Fleurquin;Salah Sadou
Affiliations:
University of South Brittany, France;University of South Brittany, France;University of South Brittany, France
Venue:
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
Year:
2005

Citing 0
Cited 8

NFRs-aware architectural evolution of component-based software

Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Simplifying transformation of software architecture constraints

Proceedings of the 2006 ACM symposium on Applied computing
A family of languages for architecture constraint specification

Journal of Systems and Software
Enforcing architecture and deployment constraints of distributed component-based software

FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
Building the presentation-tier of rich web applications with hierarchical components

WISE'07 Proceedings of the 8th international conference on Web information systems engineering
Component deployment evolution driven by architecture patterns and resource requirements

EWSA'06 Proceedings of the Third European conference on Software Architecture
CBSE in small and medium-sized enterprise: experience report

CBSE'06 Proceedings of the 9th international conference on Component-Based Software Engineering
On-Demand quality-oriented assistance in component-based software evolution

CBSE'06 Proceedings of the 9th international conference on Component-Based Software Engineering

Quantified Score

Hi-index	0.01

Visualization

Abstract

It is argued that architecture comprehension and regression testing of a software system are the most expensive maintenance activities. This is mainly due to the fact that architectural choices are either not explicit, at every stage of the software development process, or not preserved from one stage to another. In this paper, we present an Architectural Constraint Language (ACL) as a means to formally describe architectural choices at all the stages. This language is based on the UML's Object Constraint Language and on a set of MOF-compliant metamodels. We also present a prototype which validates the proposed approach. It allows the evaluation of ACL expressions at two stages and ensures, by using a transformation mechanism, that the constraints stated at one stage are subsequently preserved.