Assessing the influence on processes when evolving the software architecture

Software intensive products and systems evolve over the life-cycle. Changing business objectives may drive architectural or process changes. Altering either architecture or process might influence the other. Also the organization may influence and be influenced. This paper describes these relationships and proposes a method for assessing the influence on process that a proposed architectural change can have. The method includes the use of scenarios and process reference models. A case study where the method has been used is described, identifying the need for changes in the processes to be able to utilize the advantages made possible due to the architectural evolution. The case study supports our proposal that a structured method to assess the impacts on process when changing the architecture of a system helps to reduce risks and to facilitate the envisioned business benefits. This also identifies the need to devise methods for other types of changes, e.g. how a process change may influence architecture or organization.