Publication: Identifying outdated requirements based on source code changes
Identifying outdated requirements based on source code changes
Date
Date
Date
Citations
Ben Charrada, E., Koziolek, A., & Glinz, M. (2012). Identifying outdated requirements based on source code changes. 61–70. https://doi.org/10.1109/RE.2012.6345840
Abstract
Abstract
Abstract
Keeping requirements specifications up-to-date when systems evolve is a manual and expensive task. Software engineers have to go through the whole requirements document and look for the requirements that are affected by a change. Consequently, engineers usually apply changes to the implementation directly and leave requirements unchanged. In this paper, we propose an approach for automatically detecting outdated requirements based on changes in the code. Our approach first identifies the changes in the code that are likely to affect r
Metrics
Downloads
Views
Additional indexing
Creators (Authors)
Event Title
Event Title
Event Title
Event Location
Event Location
Event Location
Event Country
Event Country
Event Country
Event Start Date
Event Start Date
Event Start Date
Event End Date
Event End Date
Event End Date
Page range/Item number
Page range/Item number
Page range/Item number
Page end
Page end
Page end
Item Type
Item Type
Item Type
In collections
Dewey Decimal Classifikation
Dewey Decimal Classifikation
Dewey Decimal Classifikation
Scope
Scope
Scope
Language
Language
Language
Date available
Date available
Date available
OA Status
OA Status
OA Status
Publisher DOI
Other Identification Number
Other Identification Number
Other Identification Number
Metrics
Downloads
Views
Citations
Ben Charrada, E., Koziolek, A., & Glinz, M. (2012). Identifying outdated requirements based on source code changes. 61–70. https://doi.org/10.1109/RE.2012.6345840