Improving requirements-test alignment by prescribing practices that mitigate communication gaps

Research output: Contribution to journalArticle

Standard

Improving requirements-test alignment by prescribing practices that mitigate communication gaps. / Bjarnason, Elizabeth; Sharp, Helen; Regnell, Björn.

In: Empirical Software Engineering, Vol. 24, No. 4, 29.07.2019, p. 2364-2409.

Research output: Contribution to journalArticle

Harvard

APA

CBE

MLA

Vancouver

Author

RIS

TY - JOUR

T1 - Improving requirements-test alignment by prescribing practices that mitigate communication gaps

AU - Bjarnason, Elizabeth

AU - Sharp, Helen

AU - Regnell, Björn

PY - 2019/7/29

Y1 - 2019/7/29

N2 - The communication of requirements within software development is vital for project success. Requirements engineering and testing are two processes that when aligned can enable the discovery of issues and misunderstandings earlier, rather than later, and avoid costly and time-consuming rework and delays. There are a number of practices that support requirements-test alignment. However, each organisation and project is different and there is no one-fits-all set of practices. The software process improvement method called Gap Finder is designed to increase requirements-tes t alignment. The method contains two parts: an assessment part and a prescriptive part. It detects potential communication gaps between people and between artefacts (the assessment part), and identifies practices for mitigating these gaps (the prescriptive part). This paper presents the design and formative evaluation of the prescriptive part; an evaluation of the assessment part was published previously. The Gap Finder method was constructed using a design science research approach and is built on the Theory of Distances for Software Engineering, which in turn is grounded in empirical evidence from five case companies. The formative evaluation was performed through a case study in which Gap Finder was applied to an on-going development project. A qualitative and mixed-method approachwas taken in the evaluation, including ethnographically-informed observations. The results show that Gap Finder can detect relevant communication gaps and seven of the nine prescribed practices were deemed practically relevant for mitigating these gaps. The project team found the method to be useful and supported joint reflection and improvement of their requirementscommunication. Our findings demonstrate that an empirically-based theory can be used to improve software development practices and provide a foundation for further research on factors that affect requirements communication.

AB - The communication of requirements within software development is vital for project success. Requirements engineering and testing are two processes that when aligned can enable the discovery of issues and misunderstandings earlier, rather than later, and avoid costly and time-consuming rework and delays. There are a number of practices that support requirements-test alignment. However, each organisation and project is different and there is no one-fits-all set of practices. The software process improvement method called Gap Finder is designed to increase requirements-tes t alignment. The method contains two parts: an assessment part and a prescriptive part. It detects potential communication gaps between people and between artefacts (the assessment part), and identifies practices for mitigating these gaps (the prescriptive part). This paper presents the design and formative evaluation of the prescriptive part; an evaluation of the assessment part was published previously. The Gap Finder method was constructed using a design science research approach and is built on the Theory of Distances for Software Engineering, which in turn is grounded in empirical evidence from five case companies. The formative evaluation was performed through a case study in which Gap Finder was applied to an on-going development project. A qualitative and mixed-method approachwas taken in the evaluation, including ethnographically-informed observations. The results show that Gap Finder can detect relevant communication gaps and seven of the nine prescribed practices were deemed practically relevant for mitigating these gaps. The project team found the method to be useful and supported joint reflection and improvement of their requirementscommunication. Our findings demonstrate that an empirically-based theory can be used to improve software development practices and provide a foundation for further research on factors that affect requirements communication.

KW - Empirical Software Engineering

KW - Software Process Improvement

KW - Communication

KW - Requirements Engineering

KW - Testing

KW - Software Engineering Theory

U2 - 10.1007/s10664-019-09698-6

DO - 10.1007/s10664-019-09698-6

M3 - Article

VL - 24

SP - 2364

EP - 2409

JO - Empirical Software Engineering

JF - Empirical Software Engineering

SN - 1573-7616

IS - 4

ER -