The F16 has the air inlet below the body, clearly identifyable. The top right plane is definitely NOT a F-16. (Just perform a Google image search). Moreover, the F16 has only a single tail wing.
With version 2.0, UML is going to make an enormous step towards visual application design. Several ambiguities are resolved. Class diagrams and OCL are now built on precise foundations (set theory and predicate logics) [1] -- instead of having most of the semantics described in plain English; the fundations of other diagram types were also formalized.
The advantages of more precise models are that they can better form the basis for code generation [2] or even direct interpretation [3,4]. In contrast to earlier approaches to code generation, a common standard now allows interchange between different tools (at least to some extent).
Here, one of the main advantages is probably not "point and click", but a higher level of abstraction: current programming languages simply do not support high level diagram elements--such as bidirectional associations--as first class members. Things that can be expressed by simple means in class diagrams and OCL expressions become multi-line code in a regular programming languages[5]. Of course, building on UML directly also may resolve maintenance problems such as inconsistencies between diagrams and the actual code.
Slashdot Mirror
The F16 has the air inlet below the body, clearly identifyable. The top right plane is definitely NOT a F-16. (Just perform a Google image search). Moreover, the F16 has only a single tail wing.
With version 2.0, UML is going to make an enormous step towards visual application design. Several ambiguities are resolved. Class diagrams and OCL are now built on precise foundations (set theory and predicate logics) [1] -- instead of having most of the semantics described in plain English; the fundations of other diagram types were also formalized.
The advantages of more precise models are that they can better form the basis for code generation [2] or even direct interpretation [3,4]. In contrast to earlier approaches to code generation, a common standard now allows interchange between different tools (at least to some extent).
Here, one of the main advantages is probably not "point and click", but a higher level of abstraction: current programming languages simply do not support high level diagram elements--such as bidirectional associations--as first class members. Things that can be expressed by simple means in class diagrams and OCL expressions become multi-line code in a regular programming languages[5]. Of course, building on UML directly also may resolve maintenance problems such as inconsistencies between diagrams and the actual code.