Deciding to Adopt Requirements Traceability in Practice

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

    Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

    23 Citations (Scopus)
    6 Downloads (Pure)


    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 languageEnglish
    Title of host publicationProceedings 19th International Conference on Advanced Information Systems Engineering (CAiSE'07)
    Place of PublicationLondon
    Number of pages15
    ISBN (Print)978-3-540-72987-7
    Publication statusPublished - 2007
    Event19th International Conference on Advanced Information Systems Engineering, CAiSE 2007 - Trondheim, Norway
    Duration: 13 Jun 200715 Jun 2007
    Conference number: 19

    Publication series

    NameLecture Notes in Computer Science
    PublisherSpringer Verlag
    ISSN (Print)0302-9743
    ISSN (Electronic)1611-3349


    Conference19th International Conference on Advanced Information Systems Engineering, CAiSE 2007
    Abbreviated titleCAiSE


    • Requirements traceability
    • Requirements Engineering
    • SCS-Services
    • Decision Making


    Dive into the research topics of 'Deciding to Adopt Requirements Traceability in Practice'. Together they form a unique fingerprint.

    Cite this