The renaissance of legacy systems. Method support for software-system evolution. With contribution from Dario Avallone, Markus Breuer, John Favaro, Jane Ransom, Eirik Tryggeseth and Claude Villermain (Q4244404)
From MaRDI portal
!
This is the item page for this Wikibase entity, intended for internal use and editing purposes. Please use the normal view instead:
scientific article; zbMATH DE number 1292559
| Language | Label | Description | Also known as |
|---|---|---|---|
| default for all languages | No label defined |
||
| English | The renaissance of legacy systems. Method support for software-system evolution. With contribution from Dario Avallone, Markus Breuer, John Favaro, Jane Ransom, Eirik Tryggeseth and Claude Villermain |
scientific article; zbMATH DE number 1292559 |
Statements
27 May 1999
0 references
Renaissance
0 references
legacy system evolution
0 references
reengineering systems
0 references
0.7989654
0 references
0.7812189
0 references
0.7772421
0 references
The renaissance of legacy systems. Method support for software-system evolution. With contribution from Dario Avallone, Markus Breuer, John Favaro, Jane Ransom, Eirik Tryggeseth and Claude Villermain (English)
0 references
This book introduces a method, Renaissance, which helps you to recover control over the process of legacy system evolution. We have written this book to help you understand the problems of reengineering and to provide you with a body of practical advice for reengineering systems. Today's technology enables you to build new systems which are evolvable. Techniques and tools have also emerged to support system reengineering. However, the software industry lacks a method which supports system evolution. This book addresses this real need by disseminating our experience and results gained from the RENAISSANCE project, whose goal was to develop a method for transforming legacy systems into an evolvable form. Renaissance supports software evolution from project conception through to deploying the reengineered system. We have designed Renaissance for information systems, but much of it is applicable to other classes of system. In short, Renaissance helps you answer two critical questions: What is the best way to evolve a legacy system? There are three general evolution strategies: continued maintenance, reengineering and replacement. Renaissance provides practical advice and techniques for choosing the right strategy based on technical, organizational and business factors. How do I implement an evolution strategy? Once you have selected a strategy, Renaissance offers guidance on managing activities which are specific to evolution projects.
0 references