Skip to main content
SpringerLink
Log in

Architectural refactoring of corporate program systems

  • Published:
Programming and Computer Software Aims and scope Submit manuscript

Abstract

This paper is devoted to the maintenance and improvement of inherited software. A technique of iterative transformations of the software architecture (also known as architectural refactoring) is used as a key organizing principle of the software maintenance and improvement. Basic problems associated with scaling this technique and methods for solving them are considered. Particular emphasis is placed on corporate software, specific features of its architecture, and on the application of the architectural refactoring to this class of software.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  1. van Deursen, A., Klint, P., and Verhoef, C., Research Issues in the Renovation of Legacy Systems, CWI Res. Rep., April, 1999.

  2. Fowler, M., Refactoring: Improving the Design of Existing Code, Addison-Wesley, 1999. Translated under the title Refaktoring: uluchshenie sushchestvuyushchego koda, St. Petersburg: Simvol, 2003.

  3. Ksenzov, M. V., Refactoring of Software Architecture, Preprint of Inst. of System Programming, Russ. Acad. Sci., Moscow, 2004, no. 4.

  4. Alexander, C., Ishikawa, S., Silverstein, M., Jakobson, M., Fiksdahl-King, I., and Angel, S., A Pattern Language, New York: Oxford Univ. Press, 1977.

    Google Scholar 

  5. Rajala, N., Campara, D., and Mansurov, N., Insight: Reverse Engineer Case Tool, Proc. 21st Int. Conf. on Software Engineeing, Los Alamitos, CA, USA: IEEE Comput. Soc., 1999, pp. 630–633.

    Google Scholar 

  6. The JBoss 4 Application Server Guide, JBoss AS 4.0.1, Release 2, JBoss, 2005.

  7. Enterprise JavaBeansTM Specification, Version 2.1, Sun Microsystems, November 12, 2003.

  8. Java Management Extensions Instrumentation and Agent Specification V1.2 (JSR003), http://jcp.org/en/jsr/detail?id=3.

  9. Lindfors, J. and Fleury, M., JMX: Managing J2EE with Java Management Extensions, Indianapolis: Sams, 2002.

    Google Scholar 

  10. Andersen, L., JDBC@TM 4.0 Specification, JSR 221, Specification Lead, Sun Microsystems, June 2, 2005.

  11. Hibernate—Relational Persistence for Idiomatic Java, Hibernate Reference Documentation 3.0.5, http://www.hibernate.org.

  12. JSR-000012 JavaTM Data Objects (JDO) Specification, Sun Microsystems, http://java.sun.com/products/jdo/index.jsp.

  13. Java Servlet Technology Documentation, Sun Microsystems, http://java.sun.com/products/servlet/docs.html.

  14. Cocoon, The Apache Software Foundation, http://cocoon.apache.org/.

Download references

Author information

Authors and Affiliations

  1. Institute of System Programming, Russian Academy of Sciences, ul. Bols’shaya Kommunisticheskaya 25, Moscow, 109004, Russia

    M. V. Ksenzov

Authors
  1. M. V. Ksenzov
    View author publications

    You can also search for this author in PubMed Google Scholar

Additional information

Original Russian Text © M.V. Ksenzov, 2006, published in Programmirovanie, 2006, Vol. 32, No. 1.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Ksenzov, M.V. Architectural refactoring of corporate program systems. Program Comput Soft 32, 31–43 (2006). https://doi.org/10.1134/S036176880601004X

Download citation

  • Received:

  • Issue Date:

  • DOI: https://doi.org/10.1134/S036176880601004X

Keywords

Search

Navigation