Architectural evolution of legacy systems

The purpose of this paper is to gain experience in solving real problems faced by a company. We first specify the system architecture of the AFS Master System (R) using our Component Specification Language (CSL). We then identified various problem evident in the current architecture of the AFS Master System (R). Based on an analysis of the architecture and these problems, we proposed a modification to the software architecture that addressed out of the seven main problems identified. The engineers made the appropriate changes to the software system (about one week of effort) and have noted a 25% improvement in efficiency as well as an improved system organization that can be more easily changed to meet future demands. We believe the type of architectural change described in this paper will prove useful to developers using similar technologies as described in this paper.

[1]  Daniel M. Yellin,et al.  Protocol specifications and component adaptors , 1997, TOPL.

[2]  Meir M. Lehman,et al.  Laws of Software Evolution Revisited , 1996, EWSPT.

[3]  Dan Appleman Dan Appleman's Visual Basic Programmer's Guide to the Win32 API , 1997 .

[4]  Peyman Oreizy A flexible approach to decentralized software evolution , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[5]  Richard Grimes,et al.  Professional Dcom Programming , 1997 .

[6]  Mary Shaw,et al.  An Introduction to Software Architecture , 1993, Advances in Software Engineering and Knowledge Engineering.

[7]  Richard N. Taylor,et al.  Separating fact from fiction in software architecture , 1998, ISAW '98.

[8]  Peyman Oreizy,et al.  Architecture-based runtime software evolution , 1998, Proceedings of the 20th International Conference on Software Engineering.

[9]  Walter Mann,et al.  Correction to "Specification and Analysis of System Architecture Using Rapide" , 1995, IEEE Trans. Software Eng..

[10]  Jesper Andersson Reactive dynamic architectures , 1998, ISAW '98.