Enforcing UML 2.x compliance

[Kishore Kumar]

While EA is excellent when it comes to support all new UML 2.x specifications, I wonder why no attempt is made to enforce these specifications?

For example

• I can deploy a component on to a node. UML 2.x says you can deploy only artifacts on to nodes.
• I can nest a device inside an execution environment.
• I can create a diagram showing a component being composed of a use case or vice versa (i.e. use a composition relationship between a component and a use case).

All of these are inherently meaningless (though I am not sure if UML 2.x specs are tight enough to prohibit each of these).

Is it possible to strengthen EA to prevent these nonsensical constructs?

In the absence of such restrictions, you will be amazed at the kind of nonsense some of my colleagues generate. I admit the fundamental problem is one of lack of understanding of UML, but a stringent tool will speed up the learning process.