Supporting architects to improve their software system's decomposition - lessons learned

A. Vanya; A.S. Klusener; R. Premraj; H. van Vliet

doi:10.1002/smr.574

Supporting architects to improve their software system's decomposition - lessons learned

A. Vanya, A.S. Klusener, R. Premraj, H. van Vliet

Research output: Contribution to Journal › Article › Academic › peer-review

Abstract

The architect of a large, evolving system may wish to revise its decomposition from time to time; for instance, because the structure has deteriorated over time, certain components need to be outsourced to another site. One way to assess the current decomposition is to consider the past evolution, searching for components that often changed together. We iteratively devised and implemented a process for doing so at Philips Healthcare MRI. In this paper, we describe the lessons learned on how to effectively support architects to improve their system decomposition. Copyright © 2011 John Wiley &Sons, Ltd.

Original language	English
Pages (from-to)	219-232
Journal	Journal of Software: Evolution and process
Volume	25
Issue number	3
DOIs	https://doi.org/10.1002/smr.574
Publication status	Published - 2013

Access to Document

10.1002/smr.574

Persistent URL (handle)

Copy link address

Cite this

@article{3ea265cd771a4481bcc7491a15102869,

title = "Supporting architects to improve their software system's decomposition - lessons learned",

abstract = "The architect of a large, evolving system may wish to revise its decomposition from time to time; for instance, because the structure has deteriorated over time, certain components need to be outsourced to another site. One way to assess the current decomposition is to consider the past evolution, searching for components that often changed together. We iteratively devised and implemented a process for doing so at Philips Healthcare MRI. In this paper, we describe the lessons learned on how to effectively support architects to improve their system decomposition. Copyright {\textcopyright} 2011 John Wiley &Sons, Ltd.",

author = "A. Vanya and A.S. Klusener and R. Premraj and {van Vliet}, H.",

year = "2013",

doi = "10.1002/smr.574",

language = "English",

volume = "25",

pages = "219--232",

journal = "Journal of Software: Evolution and process",

issn = "2047-7481",

publisher = "John Wiley and Sons Ltd",

number = "3",

}

TY - JOUR

T1 - Supporting architects to improve their software system's decomposition - lessons learned

AU - Vanya, A.

AU - Klusener, A.S.

AU - Premraj, R.

AU - van Vliet, H.

PY - 2013

Y1 - 2013

N2 - The architect of a large, evolving system may wish to revise its decomposition from time to time; for instance, because the structure has deteriorated over time, certain components need to be outsourced to another site. One way to assess the current decomposition is to consider the past evolution, searching for components that often changed together. We iteratively devised and implemented a process for doing so at Philips Healthcare MRI. In this paper, we describe the lessons learned on how to effectively support architects to improve their system decomposition. Copyright © 2011 John Wiley &Sons, Ltd.

AB - The architect of a large, evolving system may wish to revise its decomposition from time to time; for instance, because the structure has deteriorated over time, certain components need to be outsourced to another site. One way to assess the current decomposition is to consider the past evolution, searching for components that often changed together. We iteratively devised and implemented a process for doing so at Philips Healthcare MRI. In this paper, we describe the lessons learned on how to effectively support architects to improve their system decomposition. Copyright © 2011 John Wiley &Sons, Ltd.

U2 - 10.1002/smr.574

DO - 10.1002/smr.574

M3 - Article

SN - 2047-7481

VL - 25

SP - 219

EP - 232

JO - Journal of Software: Evolution and process

JF - Journal of Software: Evolution and process

IS - 3

ER -

Supporting architects to improve their software system's decomposition - lessons learned

Abstract

Access to Document

Persistent URL (handle)

Fingerprint

Cite this