Re-engineering the algorithma project for long-term maintenance

  • Authors:
  • Willie James;Phil Lucas;John O'Connor;Arturo I. Concepcion

  • Affiliations:
  • Environmental Systems Research Institute, Redlands, CA, USA;Cal State San Bernardino, San Bernardino, CA, USA;Northrop Grumman, Redondo Beach, CA, USA;Cal State San Bernardino, San Bernardino, CA, USA

  • Venue:
  • Companion to the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

The AlgorithmA project has been in existence since 1991 and is used as an on-going project in the software engineering class taught at CSUSB. In 1998, the project was first implemented on the Internet using Java. In 2007, the maintenance of the project was a big challenge because of the size of the project and the complexity of the architectural design. This paper talks about the decision process of the software engineering class that led to the reengineering of the entire AlgorithmA project, which is a situation that actually happens in a real software company. The observations and experiences of the project manager, the team leader of the maintenance team, and the team leader of the Java team that implemented the re-design of the project, are discussed in this paper. The re-design followed the Model/View/Controller (MVC) model and using the Observer and Factory patterns, made the AlgorithmA project maintainable and extensible for many more years to come.