Estimating the costs of a reengineering project

Accurate estimation of project costs is an essential prerequisite to making a reengineering project. Existing systems are usually reengineered because it is cheaper to reengineer them than to redevelop or to replace them. However, to make this decision, management must know what the reengineering will cost. This contribution describes an eight step tool supported process for calculating the time and the costs required to reengineer an existing system. The process is derived from the author's 20 year experience in estimating reengineering projects and has been validated by several real life field experiments in which it has been refined and calibrated

[1]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[2]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[3]  R. Geoff Dromey,et al.  A Model for Software Product Quality , 1995, IEEE Trans. Software Eng..

[4]  Harry M. Sneed Encapsulating legacy software for use in client/server systems , 1996, Proceedings of WCRE '96: 4rd Working Conference on Reverse Engineering.

[5]  Ladan Tahvildari,et al.  Journal of Software Maintenance and Evolution: Research and Practice Improving Design Quality Using Meta-pattern Transformations: a Metric-based Approach , 2022 .

[6]  H. M. SNEED,et al.  Economics of software re-engineering , 1991, J. Softw. Maintenance Res. Pract..

[7]  Harry M. Sneed,et al.  Measuring reusability of legacy software systems , 1998, Softw. Process. Improv. Pract..

[8]  Siu Leung Chung,et al.  An Economic Model to Estimate Software Rewriting and Replacement Times , 1996, IEEE Trans. Software Eng..

[9]  Henry F. Ledgard,et al.  Measuring productivity in the software industry , 2003, CACM.

[10]  Harry M. Sneed,et al.  Risks involved in reengineering projects , 1999, Sixth Working Conference on Reverse Engineering (Cat. No.PR00303).

[11]  H. M. Sneed Bank application reengineering and conversion at the Union Bank of Switzerland , 1991, Proceedings. Conference on Software Maintenance 1991.

[12]  Barry W. Boehm,et al.  Bayesian Analysis of Empirical Software Engineering Cost Models , 1999, IEEE Trans. Software Eng..

[13]  Harry M. Sneed,et al.  Planning the Reengineering of Legacy Systems , 1995, IEEE Softw..

[14]  Martin Fowler,et al.  Refactoring - Improving the Design of Existing Code , 1999, Addison Wesley object technology series.

[15]  Harry M. Sneed,et al.  Understanding software through numbers: A metric based approach to program comprehension , 1995, J. Softw. Maintenance Res. Pract..

[16]  Lei Xue-mei Software quality assurance in SW-CMM2 , 2006 .

[17]  Harry M. Sneed,et al.  Aufwandsschätzung von Software-Reengineering-Projekten , 2003, Wirtschaftsinf..

[18]  K. Kavi,et al.  Software Tools Assessment , 1996, IEEE Software.

[19]  Varun Grover,et al.  Profiling successful reengineering projects , 1998, CACM.

[20]  Mark Keil,et al.  Software project risks and their effect on outcomes , 2004, CACM.

[21]  Alessandro Bianchi,et al.  Iterative Reengineering of Legacy Systems , 2003, IEEE Trans. Software Eng..

[22]  Harry M. Sneed,et al.  Automated Software Quality Assurance , 1985, IEEE Transactions on Software Engineering.

[23]  Harry M. Sneed Software Renewal: A case Study , 1984, IEEE Software.

[24]  Tarek K. Abdel-Hamid,et al.  Adapting, correcting, and perfecting software estimates: a maintenance metaphor , 1993, Computer.