Change Impact Analysis based on Formalization of Trace Relations for Requirements

Arda Göknil, Ivan Ivanov, Klaas van den Berg

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

    50 Downloads (Pure)

    Abstract

    Evolving customer needs is one of the driving factors in software development. There is a need to analyze the impact of requirement changes in order to determine possible conflicts and design alternatives influenced by these changes. The analysis of the impact of requirement changes on related requirements can be based on requirements traceability. In this paper, we propose a requirements metamodel with well defined types of requirements relations. This metamodel represents the common concepts extracted from some prevalent requirements engineering approaches. The requirements relations in the metamodel are used to trace related requirements for change impact analysis. We formalize the relations. Based on this formalization, we define change impact rules for requirements. As a case study, we apply these rules to changes in the requirements specification for Course Management System.
    Original languageEnglish
    Title of host publicationECMDA Traceability Workshop (ECMDA-TW) 2008
    Subtitle of host publicationProceedings
    EditorsJ. Oldevik, G. K. Olsen, T. Neple, R. Paige
    Place of PublicationTrondheim, Norway
    PublisherSINTEF Report
    Pages59-75
    Number of pages17
    ISBN (Print)978-82-14-04396-9
    Publication statusPublished - Jun 2008
    EventECMDA Traceability Workshop, ECMDA-TW 2008 - Berlin, Germany
    Duration: 12 Jun 200812 Jun 2008

    Publication series

    Name
    PublisherSINTEF Report
    Number274

    Conference

    ConferenceECMDA Traceability Workshop, ECMDA-TW 2008
    Abbreviated titleECMDA-TW
    Country/TerritoryGermany
    CityBerlin
    Period12/06/0812/06/08

    Keywords

    • CR-D.2
    • SE-MDA: Model Driven Architecture

    Fingerprint

    Dive into the research topics of 'Change Impact Analysis based on Formalization of Trace Relations for Requirements'. Together they form a unique fingerprint.

    Cite this