Guidance for Design Rationale Capture to Support Software Evolution
| dc.contributor.author | Schubanz, Mathias | |
| dc.contributor.author | Pleuss, Andreas | |
| dc.contributor.author | Jordan, Howell | |
| dc.contributor.author | Botterweck, Goetz | |
| dc.date.accessioned | 2023-03-16T11:05:42Z | |
| dc.date.available | 2023-03-16T11:05:42Z | |
| dc.date.issued | 2014 | |
| dc.description.abstract | Documenting design rationale (DR) helps to preserve knowledge over long time to diminish software erosion and to ease maintenance and refactoring. However, use of DR in practice is still limited. One reason for this is the lack of concrete guidance for capturing DR. This paper provides a first step towards identifying DR questions that can guide DR capturing and discusses required future research. | en |
| dc.identifier.pissn | 0720-8928 | |
| dc.identifier.uri | https://dl.gi.de/handle/20.500.12116/40870 | |
| dc.language.iso | en | |
| dc.publisher | Geselllschaft für Informatik e.V. | |
| dc.relation.ispartof | Softwaretechnik-Trends Band 34, Heft 2 | |
| dc.title | Guidance for Design Rationale Capture to Support Software Evolution | en |
| dc.type | Text/Journal Article | |
| gi.citation.publisherPlace | Bonn | |
| gi.conference.sessiontitle | Fachgruppenberichte: FG SRE und AK L2S2 - Berichte und Beiträge vom 16. Workshop „Software-Reengineering und -Evolution“ und 6. Workshop „Design for Future“, 28. - 30. April 2014 in Bad Honnef |
Dateien
Originalbündel
1 - 1 von 1
Vorschaubild nicht verfügbar
- Name:
- wsre_dff_2014-06_submission_d5.pdf
- Größe:
- 207.27 KB
- Format:
- Adobe Portable Document Format