Technology risks Recovered information is not useful or used Reverse engineering to representations that
cannot be shared Reengineering technology inadequate to
accomplish reengineering goals
Tool risks Dependence on tools that do not perform as
advertised Not using installed tools
Strategy risks Premature commitment to a reengineering solution
for an entire system Failure to have a long-term vision with interim goals Lack of global view: code, data, process
reengineering No plan for using reengineering tools
Application risks Reengineering with no local application experts
available Existing business knowledge embedded in source
code is lost Reengineered system does not perform adequately
Process risks Extremely high manual reengineering costs Cost benefits not realized in required time frame Cannot economically justify the reengineering effort Reengineering effort drifts Lack of management commitment to ongoing
Personnel risks Programmers inhibiting the start of reengineering Programmers performing less effectively to make
an unpopular reengineering project look less effective
Software Re-engineering is reorganising and modifying existing software systems to make them more maintainable.
Its purpose is to improve the current system. occurs at two different levels of abstraction
Business level Software level
Re-engineering approaches Big Bang Incremental Evolutionary
Roger S. Pressman, “Software Engineering: A Practitioner’s Approach, 5th edition”.
Ian Sommerville, “Software Engineering, 6th edition”, 2000.
linda Rosenberg, “Software Re-Engineering”. A. Sonhaji,Megah Mulya, Mubassiran, Nasruddin, Ari
Yanuar, “Rekayasa Ulang (Reengineering)” Ira D. Baxter,Michael Mehlich, “Reverse Engineering is
Reverse Forward Engineering”, 1997 David Eichman, “Factors in Reuse and Reengineering of
Legacy Software”. Repository Based Software Engineering Program Research Institute for Computing and Information Systems University of Houston – Clear Lake, 1997