The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Telelogic's "Code-Centric Model-Driven Development"

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Steven Kelly

Posts: 294
Nickname: stevek
Registered: Jul, 2005

Steven Kelly is CTO at MetaCase and lead developer of the MetaEdit+ Domain-Specific Modeling tool
Telelogic's "Code-Centric Model-Driven Development" Posted: Oct 29, 2007 2:34 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by Steven Kelly.
Original Post: Telelogic's "Code-Centric Model-Driven Development"
Feed Title: Steven Kelly on DSM
Feed URL: http://www.metacase.com/blogs/stevek/stevek-rss.xml
Feed Description: Domain-Specific Modeling: A Toolmaker Perspective
Latest Agile Buzz Posts
Latest Agile Buzz Posts by Steven Kelly
Latest Posts From Steven Kelly on DSM

Advertisement

Looks like the marketing department at Telelogic is suffering after the takeover by IBM. Their latest webcast advertises "Better Java Development with Code Centric Model Driven Development" -- what an oxymoron, and what a load of baloney! I don't think anyone is fooled, though, and to make sure they go on to blow their own cover:

speed your time to market and improve quality like never before. We'll show you how you can maintain your current development process to obtain these benefits and more, including:
  • Vaulting over your competition by leveraging automated MDD processes to take care of irksome yet essential development processes so you can focus on your passion: engineering

Somehow I find it hard to see people obtaining massive increases in productivity and quality by "maintaining their current development process"... The bulleted sentence says it all: coding is the real thing, just reverse engineer the code to produce those annoying models that your manager requires. Very model-driven.

Reverse engineering legacy code is for organizations who don't know what they've done.
Reverse engineering current code is for organizations who don't know what they're doing.

If you really care about your code, encapsulate your best practices into a domain-specific generator. That's much better than expecting a dumb computer to understand your code better than you. And much better than writing best practices down in Word documents and getting frustrated when developers don't follow them.

Read: Telelogic's "Code-Centric Model-Driven Development"

Topic: Smalltalk Daily - Specifying Behavior Patterns Previous Topic   Next Topic Topic: Stalking the Leopard :)

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use