李彤《软件工程》教学课件ch21.pptVIP

The re-engineering process Reengineering process activities Source code translation Convert code to a new language. Reverse engineering Analyse the program to understand it; Program structure improvement Restructure automatically for understandability; Program modularisation Reorganise the program structure; Data reengineering Clean-up（打扫） and restructure system data. Re-engineering approaches A utoma ted r estructuring with man ual changes A utoma ted sour ce code con v ersion R estructuring plus ar chitectur al changes A utoma ted pr o g r am r estructuring Pr o g r am and da ta r estructuring Incr eased cost Reengineering cost factors The quality of the software to be reengineered. The tool support available for reengineering. The extent of the data conversion which is required. The availability of expert staff for reengineering. This can be a problem with old systems based on technology that is no longer widely used. 21.4 Legacy system evolution Organisations that rely on legacy systems must choose a strategy for evolving these systems Scrap（扔掉） the system completely and modify business processes so that it is no longer required; Continue maintaining the system; Transform the system by re-engineering to improve its maintainability; Replace the system with a new system. The strategy chosen should depend on the system quality and its business value. System quality and business value Business Value Legacy system categories Low quality, low business value These systems should be scrapped. Low-quality, high-business value These make an important business contribution but are expensive to maintain. Should be re-engineered or replaced if a suitable system is available. High-quality, low-business value Replace with COTS, scrap completely or maintain. High-quality, high business value Continue in operation using normal system maintenance. Business value assessment Assessment should take different viewpoints into account System end-users; Business customers; Line m