TY - GEN
T1 - Assessing Migration of a 20-Year-Old System to a Micro-Service Platform Using ATAM
AU - Cruz, Pablo
AU - Astudillo, Hernan
AU - Hilliard, Rich
AU - Collado, Miguel
N1 - Publisher Copyright:
© 2019 IEEE.
PY - 2019/5/9
Y1 - 2019/5/9
N2 - Architecture evaluation is a systematic approach to evaluate target architectures and ATAM (Architectural Trade-off Analysis Method) is one of the available methods. Migration of software systems imply many architectural decisions that should be systematically evaluated to assess concrete trade-offs and risks. This article reports on the ATAM usage at a mid-size Chilean specialty software development company to assess the migration of its 20-year old flagship product to a micro-service platform. Over three days, 10 key architectural decisions, addressing 35 scenarios, were considered. Since almost all requirements were deemed essential for legal reasons, the evaluation scheme used a modified importance dimension distinguishing among business-key (first line deal breakers), legally-mandated (second-line deal breakers), and desirable requirements. Key lessons learned include the very positive client feedback on the introduction of systematic evaluation of architectural choices using business criteria.
AB - Architecture evaluation is a systematic approach to evaluate target architectures and ATAM (Architectural Trade-off Analysis Method) is one of the available methods. Migration of software systems imply many architectural decisions that should be systematically evaluated to assess concrete trade-offs and risks. This article reports on the ATAM usage at a mid-size Chilean specialty software development company to assess the migration of its 20-year old flagship product to a micro-service platform. Over three days, 10 key architectural decisions, addressing 35 scenarios, were considered. Since almost all requirements were deemed essential for legal reasons, the evaluation scheme used a modified importance dimension distinguishing among business-key (first line deal breakers), legally-mandated (second-line deal breakers), and desirable requirements. Key lessons learned include the very positive client feedback on the introduction of systematic evaluation of architectural choices using business criteria.
UR - http://www.scopus.com/inward/record.url?scp=85066467824&partnerID=8YFLogxK
U2 - 10.1109/ICSA-C.2019.00039
DO - 10.1109/ICSA-C.2019.00039
M3 - Conference contribution
AN - SCOPUS:85066467824
T3 - Proceedings - 2019 IEEE International Conference on Software Architecture - Companion, ICSA-C 2019
SP - 174
EP - 181
BT - Proceedings - 2019 IEEE International Conference on Software Architecture - Companion, ICSA-C 2019
PB - Institute of Electrical and Electronics Engineers Inc.
T2 - 2019 IEEE International Conference on Software Architecture - Companion, ICSA-C 2019
Y2 - 25 March 2019 through 29 March 2019
ER -