Incorporating Legacy Code
In a perfect world, developers and managers alike would realize the benefits of model-driven development and make the switch away from code-driven processes in one graceful step. Magically, legacy code would be transformed into models, and systems' development would proceed apace. Back in the real world, developers—no matter how well-intentioned and eager—cannot immediately acquire model-driven development skills nor the tools to drive the process. And even if those acquisitions were to come to pass, there's still a large legacy of code that cannot be ignored.
Like the primarily graphical models that comprise the UML, code is also a model, in that it's an abstract representation of a subject under study. The issue at ...
Get MDA Distilled: Principles of Model-Driven Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
