NFRs-aware architectural evolution of component-based software

Authors:
Chouki Tibermacine;Régis Fleurquin;Salah Sadou
Affiliations:
Université de Bretagne Sud, Vannes, France;Université de Bretagne Sud, Vannes, France;Université de Bretagne Sud, Vannes, France
Venue:
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Year:
2005

Citing 9
Cited 3

Foundations for the study of software architecture

ACM SIGSOFT Software Engineering Notes
A Classification and Comparison Framework for Software Architecture Description Languages

IEEE Transactions on Software Engineering
Acme: architectural description of component-based systems

Foundations of component-based systems
The Koala Component Model for Consumer Electronics Software

Computer
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach

IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Software Architecture in Practice

Software Architecture in Practice
Supporting software maintenance with non-functional information

CSMR '97 Proceedings of the 1st Euromicro Working Conference on Software Maintenance and Reengineering (CSMR '97)
A comprehensive approach for the development of modular software architecture description languages

ACM Transactions on Software Engineering and Methodology (TOSEM)
Preserving Architectural Choices throughout the Component-based Software Development Process

WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture

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
Supervising the evolution of web service orchestrations using quality requirements

ECSA'11 Proceedings of the 5th European conference on Software architecture

Quantified Score

Hi-index	0.00

Visualization

Abstract

During software maintenance, some non-functional properties may be lost. This is due to the lack of an explicit definition of their links with the corresponding architectural choices. In this paper, we present a solution that automates the checking of non-functional properties after the evolution of a component-based software. Our approach emphasizes the interest of formally documenting the links binding non-functional requirements to architectural choices. The proposed formalism is based on the Object Constraint Language (OCL) applied to a software component metamodel. We also present a prototype tool which uses this documentation to warn the developer of possible effects of an architectural change on non-functional requirements.