Semantics of trace relations in requirements models for consistency checking and inferencing

Arda Göknil, Ivan Kurtev, Klaas van den Berg, Jan-Willem Veldhuis

    Research output: Contribution to journalArticleAcademicpeer-review

    61 Citations (Scopus)
    159 Downloads (Pure)


    Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined. The application of requirements reasoning based on formal semantics resolves many of the deficiencies observed in other approaches. Our tool supports better understanding of dependencies between requirements.
    Original languageEnglish
    Pages (from-to)31-54
    Number of pages24
    JournalSoftware and systems modeling
    Issue number1
    Publication statusPublished - Dec 2009


    • n/a OA procedure


    Dive into the research topics of 'Semantics of trace relations in requirements models for consistency checking and inferencing'. Together they form a unique fingerprint.

    Cite this