Which are two sides of the same coin, transformation of code <-> Diagram.
The industry couldn't get the simple one of those (diagram -> code) to work well enough, how would they do the much more complex reverse?
Architectural and even library nuances can't be easily quantified to a particular UML symbol unless you go through the effort of classifying it for every library/design pattern, and keeping that up to date as well.
