M. Wermelinger
G. Koutsoukos
ABSTRACT
A four-layer architecture is outlined for the design of systems required to accommodate higher levels of evolution and personalization. This architecture is based on the separation of four different aspects that concern change: the computations the system has to perform to ensure basic functionalities, the interactions that can be superposed among those computations to make global properties emerge, the configurations of computations and interactions that respond to current business requirements, and the "contexts" in which the system is used according to organizational policies..
- L. F. Andrade and J. L. Fiadeiro, "Coordination: the Evolutionary Dimension", in Technology of Object-Oriented Languages and Systems - TOOLS 38, IEEE Computer Society Press 2001, 136-147. Google Scholar
Digital Library
- L. F. Andrade and J. L. Fiadeiro, "Interconnecting Objects via Contracts", in UML'99 - Beyond the Standard, LNCS 1723, Springer Verlag 1999, 566-583. Google ScholarDigital Library
- L. Andrade, J. L. Fiadeiro, J. Gouveia G. Koutsoukos, M. Wermelinger. Support for Business-Driven Evolution with Coordination Technologies. Intl. Workshop on Principles of Software Evolution, pp. 98-101. Vienna, Sept. 2001 Google ScholarDigital Library
- L. Andrade, J. L. Fiadeiro, M. Wermelinger. "Enforcing Business Policies through Automated Reconfiguration", 16th Intl. Conf. on Automated Software Engineering, pp. 426-429, IEEE Computer Society Press, 2001. Google ScholarDigital Library
- L. Bass, P. Clements, R. Kazman. Software Architecture in Practice, Addison-Wesley, 1998. Google ScholarDigital Library
- Proc. of the 4th Intl. Conf. on Configurable Distributed Systems, IEEE Computer Society Press, 1998.Google Scholar
- M. Endler and J. Wei, "Programming Generic Dynamic Reconfigurations for Distributed Applications", 1st Intl. Workshop on Configurable Distributed Systems, pp. 68-79, 1992.Google Scholar
- N. Francez and I. Fortnan, Interacting Processes, Addison-Wesley 1996.Google Scholar
- D. Gelernter and N. Carriero, "Coordination Languages and their Significance", Communications ACM 35, 2, pp. 97-107, 1992. Google ScholarDigital Library
- J. Gouveia, G. Koutsoukos, L. Andrade and J. L. Fiadeiro, "Tool Support for Coordination-Based Software Evolution", in Technology of Object-Oriented Languages and Systems - TOOLS 38, IEEE Computer Society Press 2001, 184-196. Google ScholarDigital Library
- G. Koutsoukos, J. Gouveia, L. Andrade and J. L. Fiadeiro, "Managing evolution in Telecommunications Systems", in Proc. IFIP Working Conf. on Distributed Applications and Interoperable Systems, Kluwer, 2001. Google ScholarDigital Library
- G. Koutsoukos, T. Kotridis, L. Andrade, J. L. Fiadeiro, J. Gouveia and M. Wermelinger, "Coordination Technologies for Business Strategy Support: a case study in Stock Trading", ECOOP 2001 Workshop on Object Oriented Business Solutions.Google Scholar
- J. Kramer. "Configuration Programming - A Framework for the Development of Distributable Systems", Proc. CompEuro'90, pp. 374-384, IEEE, 1990.Google Scholar
- N. Medvidovic and R. Taylor, "A Classification and Comparison Framework for Software Architecture Description Languages", IEEE Trans. on Software Eng., 26(1):70-93, Jan. 2000. Google ScholarDigital Library
- K. Moazami-Goudarzi, "Consistency Preserving Dynamic Reconfiguration of Distributed Systems", PhD Thesis, Imperial College London, 1999.Google Scholar
- R. Monroe, "Capturing Software Architecture Design Expertise with Armani", Tech. Rep. CMU-CS-98-163, School of Computer Science, Carnegie Mellon University, Oct. 1998.Google Scholar
- M. Wermelinger, A. Lopes, J. L. Fiadeiro. "A Graph Based Architectural (Re)configuration Language", Proc. ESEC/FSE, pp. 21-32. ACM Press, 2001. Google ScholarDigital Library
- A. Young and J. Magee, "A Flexible Approach to Evolution of Reconfigurable Systems", 1st Intl. Workshop on Configurable Distributed Systems, pp. 152-163, 1992.Google Scholar
Recommendations
Evolving Software Architecture Descriptions of Critical Systems
To manage the complexity of developing, maintaining, and evolving a critical software-intensive system, its architecture description must be accurately and traceably linked to its implementation.
Designing and managing evolving systems using a MAS product line approach
We view an evolutionary system as being a software product line. The core architecture is the unchanging part of the system, and each version of the system may be viewed as a product from the product line. Each ''product'' may be described as the core ...
Modularity in continually evolving systems
AOSD '11: Proceedings of the tenth international conference on Aspect-oriented software development companionThe design of a continually-evolving system deteriorates in proportion to the frequency of evolution as much as the complexity of evolution. Here we introduce a design paradigm, Temporal Control Flow Rule-based Architecture (TeCFRA), with a vision to ...
Comments