Deciding to Adopt Requirements Traceability in Practice


Share/Save/Bookmark

Blaauboer, Floris and Sikkel, Klaas and Aydin, Mehmet N. (2007) Deciding to Adopt Requirements Traceability in Practice. In: 19th International Conference on Advanced Information Systems Engineering, CAiSE 2007, 13-15 June 2007, Trondheim, Norway.

[img]PDF
Restricted to UT campus only
: Request a copy
130Kb
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.
Item Type:Conference or Workshop Item
Copyright:© 2007 Springer
Faculty:
Electrical Engineering, Mathematics and Computer Science (EEMCS)
Research Group:
Link to this item:http://purl.utwente.nl/publications/63981
Official URL:http://dx.doi.org/10.1007/978-3-540-72988-4_21
Export this item as:BibTeX
EndNote
HTML Citation
Reference Manager

 

Repository Staff Only: item control page

Metis ID: 242162