@MISC{Tournier_modelingguidelines, author = {Christophe Tournier}, title = {Modeling Guidelines for Legacy Applications}, year = {} }
Share
OpenURL
Abstract
This article provides keys to getting started with modeling legacy applications using the Unified Modeling Language (UML). Legacy applications are often complex and difficult to evolve. Usually, they are written in implementation languages that are not Object-Oriented (OO), the source code is not reverse engineered, and the documentation is not synchronized with prior evolutions. Often, legacy applications have been documented using various methodologies and tools, but there is no synchronization among the tools. If developers need detailed and unambiguous information, they