Matt Croyden cites Ara Abrahamian on visual development in this post:
This Visually Explicit Programming thread is so interesting.
Imho the biggest problem of UML and MDA-based software development is that, well, the code isn't even close to what you've diagrammed! I mean take a look at buildings around you. It's easy to map what the architect drew on his board to the real tangible building. With UML the diagrams are something the designer guy draws and understands but the real program has very little resemblance to it! The designer prefers to speak a more engineering-oriented language, UML, while the masons (developers) don't like or understand it because they have to build the damn building and the architecture they are given by the modeling guy is so different from what they build. They speak two different languages. That said there is value in a engineering-oriented bureaucratic approach too, after all the civilization is built by architects rather than masons, right? So fix the gap otherwise just shut up and don't preach it :-)
That matches every encounter I've ever had with modeling tool driven development. Worse, some team members tend to become mesmerized by the design tools, and get overly focused on things like the placement of boxes in the diagrams....