The TACO approach for traceability and communication of requirements

Terje Sivertsen, Rune Fredriksen, Atoosa P-J. Thunem, Jan-Erik Holmberg, Janne Valkonen, Olli Ventä, Jan-Ove Andersson

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

    Abstract

    This paper outlines the main achievements of the TACO project. The overall objective of the TACO project was to improve the knowledge about principles and best practices related to the issues concretised in the TACO preproject. On the basis of experiences in the Nordic countries, the project aimed at identifying the best practices and most important criteria for ensuring effective communication in relation to requirements elicitation and analysis, understandability of requirements to all parties, and traceability of requirements through the different design phases. It is expected that the project will provide important input to the development of guidelines and establishment of recommended practices related to these activities.
    Original languageEnglish
    Title of host publicationComputer Safety, Reliability and Security
    Subtitle of host publication24th International Conference, SAFECOMP 2005
    PublisherSpringer
    Pages317-329
    ISBN (Electronic)978-3-540-32000-5
    ISBN (Print)0-540-29200-4, 978-3-540-29200-5
    DOIs
    Publication statusPublished - 2005
    MoE publication typeA4 Article in a conference publication
    Event24th International Conference on Computer Safety, Reliability and Security, SAFECOMP 2005 - Fredrikstad, Norway
    Duration: 26 Sep 200530 Sep 2005

    Publication series

    SeriesLecture Notes in Computer Science
    Volume3688
    ISSN0302-9743

    Conference

    Conference24th International Conference on Computer Safety, Reliability and Security, SAFECOMP 2005
    Country/TerritoryNorway
    CityFredrikstad
    Period26/09/0530/09/05

    Keywords

    • TACO

    Fingerprint

    Dive into the research topics of 'The TACO approach for traceability and communication of requirements'. Together they form a unique fingerprint.

    Cite this