TUTCRIS - Tampereen teknillinen yliopisto

TUTCRIS

Software architecture design in global software development: An empirical study

Tutkimustuotosvertaisarvioitu

Standard

Software architecture design in global software development : An empirical study. / Sievi-Korte, Outi; Richardson, Ita; Beecham, Sarah.

julkaisussa: Journal of Systems and Software, Vuosikerta 158, 110400, 01.12.2019.

Tutkimustuotosvertaisarvioitu

Harvard

Sievi-Korte, O, Richardson, I & Beecham, S 2019, 'Software architecture design in global software development: An empirical study', Journal of Systems and Software, Vuosikerta. 158, 110400. https://doi.org/10.1016/j.jss.2019.110400

APA

Sievi-Korte, O., Richardson, I., & Beecham, S. (2019). Software architecture design in global software development: An empirical study. Journal of Systems and Software, 158, [110400]. https://doi.org/10.1016/j.jss.2019.110400

Vancouver

Author

Sievi-Korte, Outi ; Richardson, Ita ; Beecham, Sarah. / Software architecture design in global software development : An empirical study. Julkaisussa: Journal of Systems and Software. 2019 ; Vuosikerta 158.

Bibtex - Lataa

@article{832ba21bb6694207a07d529387f09134,
title = "Software architecture design in global software development: An empirical study",
abstract = "In Global Software Development (GSD), the additional complexity caused by global distance requires processes to ease collaboration difficulties, reduce communication overhead, and improve control. How development tasks are broken down, shared and prioritized is key to project success. While the related literature provides some support for architects involved in GSD, guidelines are far from complete. This paper presents a GSD Architectural Practice Framework reflecting the views of software architects, all of whom are working in a distributed setting. In-depth interviews with architects from seven different GSD organizations revealed a complex set of challenges and practices. We found that designing software for distributed teams requires careful selection of practices that support understanding and adherence to defined architectural plans across sites. Teams used Scrum which aided communication, and Continuous Integration which helped solve synchronization issues. However, teams deviated from the design, causing conflicts. Furthermore, there needs to be a balance between the self-organizing Scrum team methodology and the need to impose architectural design decisions across distributed sites. The research presented provides an enhanced understanding of architectural practices in GSD companies. Our GSD Architectural Practice Framework gives practitioners a cohesive set of warnings, which for the most part, are matched by recommendations.",
keywords = "Empirical study, Global software development, GSD, GSE, Scrum, Software architecture",
author = "Outi Sievi-Korte and Ita Richardson and Sarah Beecham",
year = "2019",
month = "12",
day = "1",
doi = "10.1016/j.jss.2019.110400",
language = "English",
volume = "158",
journal = "Journal of Systems and Software",
issn = "0164-1212",
publisher = "Elsevier",

}

RIS (suitable for import to EndNote) - Lataa

TY - JOUR

T1 - Software architecture design in global software development

T2 - An empirical study

AU - Sievi-Korte, Outi

AU - Richardson, Ita

AU - Beecham, Sarah

PY - 2019/12/1

Y1 - 2019/12/1

N2 - In Global Software Development (GSD), the additional complexity caused by global distance requires processes to ease collaboration difficulties, reduce communication overhead, and improve control. How development tasks are broken down, shared and prioritized is key to project success. While the related literature provides some support for architects involved in GSD, guidelines are far from complete. This paper presents a GSD Architectural Practice Framework reflecting the views of software architects, all of whom are working in a distributed setting. In-depth interviews with architects from seven different GSD organizations revealed a complex set of challenges and practices. We found that designing software for distributed teams requires careful selection of practices that support understanding and adherence to defined architectural plans across sites. Teams used Scrum which aided communication, and Continuous Integration which helped solve synchronization issues. However, teams deviated from the design, causing conflicts. Furthermore, there needs to be a balance between the self-organizing Scrum team methodology and the need to impose architectural design decisions across distributed sites. The research presented provides an enhanced understanding of architectural practices in GSD companies. Our GSD Architectural Practice Framework gives practitioners a cohesive set of warnings, which for the most part, are matched by recommendations.

AB - In Global Software Development (GSD), the additional complexity caused by global distance requires processes to ease collaboration difficulties, reduce communication overhead, and improve control. How development tasks are broken down, shared and prioritized is key to project success. While the related literature provides some support for architects involved in GSD, guidelines are far from complete. This paper presents a GSD Architectural Practice Framework reflecting the views of software architects, all of whom are working in a distributed setting. In-depth interviews with architects from seven different GSD organizations revealed a complex set of challenges and practices. We found that designing software for distributed teams requires careful selection of practices that support understanding and adherence to defined architectural plans across sites. Teams used Scrum which aided communication, and Continuous Integration which helped solve synchronization issues. However, teams deviated from the design, causing conflicts. Furthermore, there needs to be a balance between the self-organizing Scrum team methodology and the need to impose architectural design decisions across distributed sites. The research presented provides an enhanced understanding of architectural practices in GSD companies. Our GSD Architectural Practice Framework gives practitioners a cohesive set of warnings, which for the most part, are matched by recommendations.

KW - Empirical study

KW - Global software development

KW - GSD

KW - GSE

KW - Scrum

KW - Software architecture

U2 - 10.1016/j.jss.2019.110400

DO - 10.1016/j.jss.2019.110400

M3 - Article

VL - 158

JO - Journal of Systems and Software

JF - Journal of Systems and Software

SN - 0164-1212

M1 - 110400

ER -