September 2007 marks a decade since the OMG began its formal voting process to adopt the Unified Modeling Language™ (UML™) 1.1 as its standard language for modeling software-intensive systems. Since then the UML has become the industry standard language for many Model-Driven Development (MDD) technology initiatives, ranging from the OMG's Model Driven Architecture™ to various commercial vendor and open source offerings.

This talk will contrast MDD's marketecture (marketing architecture) hyperbole with its tarchitecture (technical architecture) potential. The first part of the talk describes the progression of symptoms associated with the dreaded Muddle-Driven Marketecture (MDM) syndrome, an architecture and process anti-pattern.

The principle symptoms of MDM syndrome include bloated modeling languages, dysfunctional tools, anorexic/bulimic processes, and fractured frameworks. If not detected and treated early, the syndrome typically results in chronic schedule slippage or project failure. MDM syndrome is widespread and has already afflicted a large number of telecom, commercial IT, and defense/aerospace applications.

The rest of the talk discusses Model Driven Tarchitecture principles and best practices that will help you avoid the pitfalls of MDM syndrome, and realize the technical and business advantages of effectively applying MDD technologies to your projects.