BabikerEtAl97

PublicReengineering Wiki

They propose a 3 phase methodology for reengineering an application written in a non-OO language into an OO one. First phase is to reverse engineer the legacy. The next phase is to merge the elicited requirements with new requirements. During this phase they check for redundancy, completeness and consistency. finally they forward engineer the requirements into an OO application using a case tool and the OMT (Object Modelling Technique). Their reverse engineering is achieved by examining documentation and code and by interviewing experts. they try to reuse code from the legacy in object methods. They reckon major data structure provide hints for appropriate classes and methods. Don't seem to be wary of the addition of new requirements.


Related pages: Bibliography

This page last edited on 5 January 2000
 
 
  • Search for: