On the Evolution of Component-Based Software

  • Isabelle Côté
  • Maritta Heisel
  • Jeanine Souquières
Part of the Lecture Notes in Computer Science book series (LNCS, volume 7054)


In a component-based software system the different components communicate with each other through their interfaces, possibly using adapters. Whenever the requirements or the environment change, the component-based software system must be adapted accordingly. We present a method that supports a systematic evolution of component-based software at the architectural level. It is based on operators and modification schemata that help to identify different architectural alternatives to realize the evolution task.


Software Architecture Sequence Diagram Application Component Architectural Level Evolution Task 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    Zave, P., Jackson, M.: Four Dark Corners for Requirements Engineering. ACM Transactions on Software Engineering and Methodology 6(1), 1–30 (1997)CrossRefGoogle Scholar
  2. 2.
    UML2: Unified Modeling Language: Infrastructure and Superstructure. Object Management Group, Version 2.1.1, formal/07-02-03 (2007),
  3. 3.
    Afadl2000: Etude de cas: système de contrôle d’accès. In: Journées AFADL, Approches formelles dans l’assistance au développement de logiciels, actes LSR/IMAG (2000)Google Scholar
  4. 4.
    Cheesman, J., Daniels, J.: UML Components – A Simple Process for Specifying Component-Based Software. Addison-Wesley (2001)Google Scholar
  5. 5.
    Heisel, M., Souquières, J.: Adding Features to Component-based Systems. In: Ryan, M.D., Meyer, J.-J.C., Ehrich, H.-D. (eds.) Objects, Agents, and Features. LNCS, vol. 2975, pp. 137–153. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  6. 6.
    Lanoix, A., Hatebur, D., Heisel, M., Souquières, J.: Enhancing Dependability of Component-Based Systems. In: Abdennahder, N., Kordon, F. (eds.) Ada-Europe 2007. LNCS, vol. 4498, pp. 41–54. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  7. 7.
    Sadou, N., Tamzalit, D., Oussalah, M.: A Unified Approach for Software Architecture Evolution at Different Abstraction Levels. In: IWPSE 2005: Proceedings of the Eighth International Workshop on Principles of Software Evolution, pp. 65–70. IEEE Computer Society (2005)Google Scholar
  8. 8.
    Tamzalit, D., Sadou, N., Oussalah, M.: Connectors Conveying Software Architecture Evolution. In: COMPSAC (1), pp. 391–396. IEEE Computer Society (2007)Google Scholar
  9. 9.
    Barais, O., Lawall, J., Le Meur, A.F., Duchien, L.: Safe Integration of New Concerns in a Software Architecture. In: Proceedings of the 13th International Conference on Engineering of Computer Based Systems (ECBS 2006), pp. 52–64. IEEE (2006)Google Scholar
  10. 10.
    Casanova, M., Van Der Straeten, R., Jonckers, V.: Supporting Evolution in Component-Based Development Using Component Libraries. In: CSMR 2003: Proceedings of the 7th European Conference on Software Maintenance and Reengineering, p. 123. IEEE Computer Society (2003)Google Scholar

Copyright information

© IFIP International Federation for Information Processing 2012

Authors and Affiliations

  • Isabelle Côté
    • 1
  • Maritta Heisel
    • 1
  • Jeanine Souquières
    • 2
  1. 1.Faculty of Engineering, Department of Computer Science and Cognitive Science, Workgroup Software EngineeringUniversity Duisburg-EssenGermany
  2. 2.LORIA – Nancy UniversitéVandœuvre-les-NancyFrance

Personalised recommendations