Zur Kurzanzeige

dc.contributor.authorSneed, Harry M.
dc.contributor.editorGimnich, Rainer
dc.contributor.editorKaiser, Uwe
dc.contributor.editorQuante, Jochen
dc.contributor.editorWinter, Andreas
dc.date.accessioned2019-04-04T12:52:58Z
dc.date.available2019-04-04T12:52:58Z
dc.date.issued2008
dc.identifier.isbn3-88579-220-8
dc.identifier.issn1617-5468
dc.identifier.urihttp://dl.gi.de/handle/20.500.12116/21639
dc.description.abstractThis paper is an attempt to define what software reengineering is and what it has accomplished in the light of 20 years of practical application. The paper points out that reengineering is one of the many software maintenance activities, i.e. everything done with software once it has been put to use. Reengineering actions are devoted to improving the technical quality of existing software. By accepting this definition, it is possible to distinguish reengineering from other related activities performed on a software product after its first release such as reverse engineering, redocumentation, evolution and migration.en
dc.language.isoen
dc.publisherGesellschaft für Informatik e. V.
dc.relation.ispartofSoftware archeology and the handbook of software architecture
dc.relation.ispartofseriesLecture Notes in Informatics (LNI) - Proceedings, Volume P-126
dc.subjectSoftware Reengineering
dc.subjectReverse Engineering
dc.subjectRefactoring
dc.subjectMigration
dc.subjectMaintenance
dc.subjectEvolution
dc.title20 Years of Software-Reengineering – A Résuméen
dc.typeText/Conference Paper
dc.pubPlaceBonn
mci.reference.pages115-124
mci.conference.sessiontitleRegular Research Papers
mci.conference.locationBad Honnef
mci.conference.date5-7 May 2008


Dateien zu dieser Ressource

Thumbnail

Zur Kurzanzeige