The browser you are using is not supported by this website. All versions of Internet Explorer are no longer supported, either by us or Microsoft (read more here: https://www.microsoft.com/en-us/microsoft-365/windows/end-of-ie-support).

Please use a modern browser to fully experience our website, such as the newest versions of Edge, Chrome, Firefox or Safari etc.

The architectural change process

Author

Summary, in English

Software architecture is recognized as a critical factor for successful products, but few have studied how organizations decide on architectural changes. In this paper we study the topic through several case studies. The changes are in all cases changes to the quality attributes of the system, and follow the same general process. We find that architectural changes have aspects of both functional and organizational changes. An architectural change does not only need to be technically sound, but it also needs to be anchored firmly in the organization. This paper describes the general architectural change process, and gives both architects and managers guidelines to balance short-term project goals and long-term organizational goals within this process

Publishing year

2004

Language

English

Pages

27-36

Publication/Series

2004 International Symposium on Empirical Software Engineering

Document type

Conference paper

Publisher

IEEE - Institute of Electrical and Electronics Engineers Inc.

Topic

  • Computer Science

Keywords

  • architectural change process
  • software architecture
  • quality attributes
  • organizational changes
  • functional changes

Conference name

2004 International Symposium on Empirical Software Engineering

Conference date

2004-08-19 - 2004-08-20

Conference place

Redondo Beach, CA, United States

Status

Published

ISBN/ISSN/Other

  • ISBN: 0-7695-2165-7