Deciding to Adopt Requirements Traceability in Practice

F.A. Blaauboer; Nicolaas Sikkel; M.N. Aydin

doi:10.1007/978-3-540-72988-4_21

Deciding to Adopt Requirements Traceability in Practice

F.A. Blaauboer, Nicolaas Sikkel, M.N. Aydin

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › Academic › peer-review

24 Citations (Scopus)

6 Downloads (Pure)

Abstract

The use of requirements traceability for information systems development (ISD) projects is not very common in practice despite its often mentioned advantages in the literature. We conducted a case study in a large IT company to identify the factors that are relevant for the decision whether or not to adopt traceability in an ISD project. Five dominant factors emerged: development organization awareness, customer awareness, return on investment, stakeholder preferences, and process flow. It turned out that the majority of the software development project leaders we interviewed were not aware of the concept of traceability – with the obvious result that using traceability in software project is not even considered. This fact has possibly been underestimated in the present literature of requirements engineering.

Original language	English
Title of host publication	Proceedings 19th International Conference on Advanced Information Systems Engineering (CAiSE'07)
Place of Publication	London
Publisher	Springer
Pages	294-308
Number of pages	15
ISBN (Print)	978-3-540-72987-7
DOIs	https://doi.org/10.1007/978-3-540-72988-4_21
Publication status	Published - 2007
Event	19th International Conference on Advanced Information Systems Engineering, CAiSE 2007 - Trondheim, Norway Duration: 13 Jun 2007 → 15 Jun 2007 Conference number: 19

Publication series

Name	Lecture Notes in Computer Science
Publisher	Springer Verlag
Volume	4495
ISSN (Print)	0302-9743
ISSN (Electronic)	1611-3349

Conference

Conference	19th International Conference on Advanced Information Systems Engineering, CAiSE 2007
Abbreviated title	CAiSE
Country/Territory	Norway
City	Trondheim
Period	13/06/07 → 15/06/07

Keywords

Requirements traceability
Requirements Engineering
SCS-Services
Decision Making

Access to Document

10.1007/978-3-540-72988-4_21

Cite this

@inproceedings{231129bd87d4432883206b6f8a660dee,

title = "Deciding to Adopt Requirements Traceability in Practice",

abstract = "The use of requirements traceability for information systems development (ISD) projects is not very common in practice despite its often mentioned advantages in the literature. We conducted a case study in a large IT company to identify the factors that are relevant for the decision whether or not to adopt traceability in an ISD project. Five dominant factors emerged: development organization awareness, customer awareness, return on investment, stakeholder preferences, and process flow. It turned out that the majority of the software development project leaders we interviewed were not aware of the concept of traceability – with the obvious result that using traceability in software project is not even considered. This fact has possibly been underestimated in the present literature of requirements engineering.",

keywords = "Requirements traceability, Requirements Engineering, SCS-Services, Decision Making",

author = "F.A. Blaauboer and Nicolaas Sikkel and M.N. Aydin",

year = "2007",

doi = "10.1007/978-3-540-72988-4_21",

language = "English",

isbn = "978-3-540-72987-7",

series = "Lecture Notes in Computer Science",

publisher = "Springer",

pages = "294--308",

booktitle = "Proceedings 19th International Conference on Advanced Information Systems Engineering (CAiSE'07)",

address = "Germany",

note = "19th International Conference on Advanced Information Systems Engineering, CAiSE 2007, CAiSE ; Conference date: 13-06-2007 Through 15-06-2007",

}

Blaauboer, FA, Sikkel, N & Aydin, MN 2007, Deciding to Adopt Requirements Traceability in Practice. in Proceedings 19th International Conference on Advanced Information Systems Engineering (CAiSE'07). Lecture Notes in Computer Science, vol. 4495, Springer, London, pp. 294-308, 19th International Conference on Advanced Information Systems Engineering, CAiSE 2007, Trondheim, Norway, 13/06/07. https://doi.org/10.1007/978-3-540-72988-4_21

Deciding to Adopt Requirements Traceability in Practice. / Blaauboer, F.A.; Sikkel, Nicolaas; Aydin, M.N.
Proceedings 19th International Conference on Advanced Information Systems Engineering (CAiSE'07). London: Springer, 2007. p. 294-308 (Lecture Notes in Computer Science; Vol. 4495).

Research output: Chapter in Book/Report/Conference proceeding › Conference contribution › Academic › peer-review

TY - GEN

T1 - Deciding to Adopt Requirements Traceability in Practice

AU - Blaauboer, F.A.

AU - Sikkel, Nicolaas

AU - Aydin, M.N.

N1 - Conference code: 19

PY - 2007

Y1 - 2007

N2 - The use of requirements traceability for information systems development (ISD) projects is not very common in practice despite its often mentioned advantages in the literature. We conducted a case study in a large IT company to identify the factors that are relevant for the decision whether or not to adopt traceability in an ISD project. Five dominant factors emerged: development organization awareness, customer awareness, return on investment, stakeholder preferences, and process flow. It turned out that the majority of the software development project leaders we interviewed were not aware of the concept of traceability – with the obvious result that using traceability in software project is not even considered. This fact has possibly been underestimated in the present literature of requirements engineering.

AB - The use of requirements traceability for information systems development (ISD) projects is not very common in practice despite its often mentioned advantages in the literature. We conducted a case study in a large IT company to identify the factors that are relevant for the decision whether or not to adopt traceability in an ISD project. Five dominant factors emerged: development organization awareness, customer awareness, return on investment, stakeholder preferences, and process flow. It turned out that the majority of the software development project leaders we interviewed were not aware of the concept of traceability – with the obvious result that using traceability in software project is not even considered. This fact has possibly been underestimated in the present literature of requirements engineering.

KW - Requirements traceability

KW - Requirements Engineering

KW - SCS-Services

KW - Decision Making

U2 - 10.1007/978-3-540-72988-4_21

DO - 10.1007/978-3-540-72988-4_21

M3 - Conference contribution

SN - 978-3-540-72987-7

T3 - Lecture Notes in Computer Science

SP - 294

EP - 308

BT - Proceedings 19th International Conference on Advanced Information Systems Engineering (CAiSE'07)

PB - Springer

CY - London

T2 - 19th International Conference on Advanced Information Systems Engineering, CAiSE 2007

Y2 - 13 June 2007 through 15 June 2007

ER -

Deciding to Adopt Requirements Traceability in Practice

Abstract

Publication series

Conference

Keywords

Access to Document

Fingerprint

Cite this