[ Summary | Objectives
& Results | Work Packages | Deliverables
| Partners | EC Projects
| Re-Engineering Links ]
[ Summary | Objectives
& Results | Work Packages | Deliverables
| Partners | EC Projects
| Re-Engineering Links ]
This report will include a description of target client-server models including legacy systems components, an assessment of the applicability of OLE and CORBA and conversion of systems using teleprocessing monitors to these frameworks, and advice on specific problems of re-organising monolithic systems to a client-server model. The use of UI generation systems for client implementation will be described and techniques of data migration to distributed systems (components, data, transaction processing monitors, user interfaces) servers will be covered.
Full report (Adobe PDF format)
A modified version of the initial baseline report (3.1a) which incorporates changes as a result of evaluation feedback and which is prepared to a high-quality for use outside of the RENAISSANCE project.
This report will provide detailed advice on how current research in architectural modelling styles may be applied to identify the architecture of legacy systems and especially its reusable building blocks. It will suggest a documentation framework for architectural models and explain how systems may be analysed (manually and with tool assistance) to produce this documentation.
Full report titlepage, and body (Adobe PDF format)
A modified version of the initial baseline report (3.2a) which incorporates changes as a result of evaluation feedback and which is prepared to a high-quality for use outside of the RENAISSANCE project.
This will provide guidelines for managers on planning and managing the evolution of legacy systems. It will describe evolution strategies which may be applied to all or part of a system, explain where these strategies are likely to be cost-effective and suggest how techniques such as algorithmic cost modelling may be used to estimate the cost-effectiveness of these strategies. It may also include advice on other issues which must be taken into account such as hardware platform evolution, training, effects on other installed systems, etc.
Full report head, body, Appendices 1, and Appendices 2 (Adobe PDF format)
A modified version of the initial baseline report (3.3a) which incorporates changes as a result of evaluation feedback and which is prepared to a high-quality for use outside of the RENAISSANCE project.
This generic method description will focus on process descriptions for re-engineering legacy systems in 3GLs and 4Gls, the documentation which may be produced and rules and guidelines which should be applied in the evolution processes. The use of existing CASE tools to support process activities will be explained. There will be method variants for 3GL and 4GL evolution.
Full report (Adobe PDF format)
This will be an initial description of the RENAISSANCE method in a form which will be suitable for application and evaluation. The results of the baseline workpackages will be integrated with the method framework to form a comprehensive method for legacy system evolution including evolution planning and management, detailed architectural modelling and client-server migration.
Full report (Adobe PDF format)
This will be a complete package of all the RENAISSANCE consultancy reports. Each report will include modifications made in response to feedback from the applications and from internal review by consultancy divisions of technology partners.
A final draft of a book which will be submitted for commercial publication. Modifications to the initial method will be included according to feedback from the evaluation activities.
This report will use the evaluation framework to assess the revised RENAISSANCE reports and the extended method developed in WP3 and WP4. The work will be carried out as described in D5.2 and will be driven by identified evolution problems.