That's downright silly. If my "noun model" is originally defined in ER/Win, I'm violating the OnceAndOnlyOnce principle by using it in the database also?

Generally that is only for the initial design. But, it would be nice if they were integrated. If the tool could query the structures and make charts based on that, that would be great. MS-SQL-Server does it more or less (although it crashes often). Many MS-SQL-Server shops have such diagrams from the product all over their walls.

I think his point is that the representation of code is much more complex than you are describing. Take a look at [Java Virtual Machine] to see what's involved for Java.

What is your point? Java being complex is not a selling point. IMO it is too complex. If you have good table/relational tools, you don't need a lot of the crap that Java has IMO. Frankly, I don't know what Static's point is. He does not seem to like me personally, so it does not look like I will get an answer.