Renaissance: a method to support software system evolution

@article{Warren2002RenaissanceAM,
  title={Renaissance: a method to support software system evolution},
  author={I. Warren and J. Ransom},
  journal={Proceedings 26th Annual International Computer Software and Applications},
  year={2002},
  pages={415-420}
}
  • I. Warren, J. Ransom
  • Published 2002
  • Engineering, Computer Science
  • Proceedings 26th Annual International Computer Software and Applications
Legacy systems are often business critical and are associated with high maintenance costs. In this paper, we present an overview of a method, Renaissance, which aims to manage the process of regaining control over such systems. Renaissance supports system evolution by first recovering a stable basis using reengineering, and subsequently continuously improving the system by a stream of incremental changes. In both cases, the extent of evolution is determined by a phase which takes into account… Expand
The Challenge of Evolving Existing Systems to Service-Oriented Architectures
Software systems are an integral part of industrial processes at every level, from low-level production control to enterprise planning. The maintenance challenge presented by such systems is aboutExpand
Systematic Review of Legacy System Migration
  • B. Althani, S. Khaddaj
  • Computer Science
  • 2017 16th International Symposium on Distributed Computing and Applications to Business, Engineering and Science (DCABES)
  • 2017
TLDR
The integration of quality into migration processes, which has a considerable impact on cost and risk, is proposed. Expand
Evolving Existing Systems to Service-Oriented Architectures: Perspective and Challenges
TLDR
A review of a number of approaches that may contribute to a pragmatic strategy for addressing the SOA problem and outline the significant challenges that remain. Expand
Semiautomatic Reverse Engineering Tool on Oracle Forms Information Systems
Legacy information systems are systems that have had a long evolution, longer than the typical turnaround time of the developers in the company. They are essential to the business and encode largeExpand
Legacy to SOA Evolution
TLDR
This chapter conducted a systematic literature review to collect legacy to SOA evolution approaches reported from 2000 to August 2011 and evaluated using an evaluation framework, developed from three evolution and modernization methods widely used in software re-engineering domain. Expand
An Agile Methodology for Reengineering Object-Oriented Software
TLDR
The methodology has a quick planning phase followed by a series of iterative reengineering phases and consists of three legs: the reverse engineering leg, the reincarnation leg, and the validation leg. Expand
Proposition d'une Méthode pour l'Ingénierie de l'Alignement Métier/SI: Diagnostic, Évolution, Alternatives technologiques et Décision. (A Method for Business/IT Alignment Engineering: Diagnosis, Evolution, Technological alternatives, Decision)
TLDR
The proposed method DEEVA method provides a solution to a complex problem such as alignment engineering by proposing and using a set of classifications that allow to break down the problem of misalignment capture and requirements evolution specification as well as their implementation by choosing the “best” technical scenario. Expand
An Assessment Tool to Prepare the Leap to the Cloud
TLDR
This chapter presents an approach for assessing the maturity of these applications and the convenience of migrating to the new cloud paradigm and, for the first time, the business value is directly attached to the technical performance. Expand
Evaluation of Software Evolution Options
ELTIS (Extending the Lifetime of Information Systems) is a research project carried out in the Information Technology Research Institute, University of Jyväskylä, and financed by National TechnologyExpand
A Quality Assured Framework for Cloud Adaptation and Modernization of Enterprise Applications
  • B. Althani, S. Khaddaj, B. Makoond
  • Computer Science
  • 2016 IEEE Intl Conference on Computational Science and Engineering (CSE) and IEEE Intl Conference on Embedded and Ubiquitous Computing (EUC) and 15th Intl Symposium on Distributed Computing and Applications for Business Engineering (DCABES)
  • 2016
TLDR
A System Migration Life Cycle (SMLC) framework is proposed, which includes a step by-stepmigration strategy that is descriptive at the business analyst level and based on quality metrics modelling at the technical level, to estimate the potential computational needs, risks, and costs for an organisation. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 16 REFERENCES
A method for assessing legacy systems for evolution
TLDR
An assessment method is presented that examines a legacy system from its technical, business and organisational perspectives, and guides users through assessment of these perspectives by selecting assessment characteristics and assigning values to them. Expand
Legacy Systems: Coping with Success
  • K. Bennett
  • Engineering, Computer Science
  • IEEE Softw.
  • 1995
Legacy systems may be defined informally as "large software systems that we don't know how to cope with but that are vital to our organization". Legacy software was written years ago using outdatedExpand
Planning the Reengineering of Legacy Systems
TLDR
A way to quantify the costs and prove the benefits of reengineering over other alternatives is proposed and some advice on contracting a reengineering project is offered. Expand
Proceedings of the 26 th Annual International Computer Software and Applications Conference
  • Proceedings of the 26 th Annual International Computer Software and Applications Conference
  • 2002
The Renaissance of Legacy Systems. Practitioner series
  • The Renaissance of Legacy Systems. Practitioner series
  • 2000
The Renaissance of Legacy Systems
  • I. Warren
  • Computer Science
  • Practitioner Series
  • 1999
Architectural Modelling. RENAISSANCE project deliverable, D3.2
  • Architectural Modelling. RENAISSANCE project deliverable, D3.2
  • 1998
Client/Server Migration. RENAISSANCE project deliverable
  • Client/Server Migration. RENAISSANCE project deliverable
  • 1998
Evolution Planning. RENAISSANCE project deliverable, D3.3
  • Evolution Planning. RENAISSANCE project deliverable, D3.3
  • 1998
The Renaissance Method. RENAISSANCE project deliverable, D4.2
  • The Renaissance Method. RENAISSANCE project deliverable, D4.2
  • 1998
...
1
2
...