Show simple item record

dc.contributor.authorCharrada, Eya Ben
dc.contributor.authorKoziolek, Anne
dc.contributor.authorGlinz, Martin
dc.contributor.editorKnoop, Jens
dc.contributor.editorZdun, Uwe
dc.date.accessioned2017-06-21T07:37:16Z
dc.date.available2017-06-21T07:37:16Z
dc.date.issued2016
dc.identifier.isbn978-3-88579-646-6
dc.identifier.issn1617-5468
dc.description.abstractKeeping the requirements specification up-to-date is crucial for several maintenance and evolution tasks. Nevertheless, due to time and budget constrains, software maintainers usually apply changes to the code only and leave the requirements unchanged, so they rapidly become obsolete and useless. In this work, we propose an approach for automatically identifying what requirements are likely to be impacted when the code is changed. We use a two-step approach. First, we identify the code changes that are likely to have an impact on requirements based on some heuristics. Second, we trace the relevant changes back to the requirements in order to identify those that are likely to be impacted [?]. The output of the tracing is a list of requirements that are sorted according to their likelihood of being impacted. We applied our approach to three case studies and could identify for each case between 70\% and 100\% of the impacted requirements within a list that includes less than 20\% of the total number of requirements in the specification [?]. We are currently exploring ways to extend the approach to other types of software artifacts such as tests.en
dc.language.isoen
dc.publisherGesellschaft für Informatik e.V.
dc.relation.ispartofSoftware Engineering 2016
dc.relation.ispartofseriesLecture Notes in Informatics (LNI) - Proceedings, Volume P-252
dc.titleSupporting requirements update during software evolutionen
dc.typeText/Conference Paper
dc.pubPlaceBonn
mci.reference.pages39-39
mci.conference.locationWien
mci.conference.date23.-26. Februar 2016


Files in this item

Thumbnail

Show simple item record