Le contrat d'évolution d'architectures. Un outil pour le maintien de propriétés non fonctionnelles

Abstract

Software systems should evolve in order to respond to changing client requirements and their evolving environments. These changes, often unforeseen, done by tiers and in urgency, lead sometimes the software to a state initially undesired by its creators. We present, in this paper, a framework to preserve the consistency of component-based applications during their evolution. This evolution consistency is achieved by maintaining some architectural strategies and thus, preserving the corresponding non-functional properties indicated as important.