What is this UML diagram?

Question

What is this UML diagram?

_{(source: tripod.com )}

Answer 1

This is a class diagram with added stereotypes.

Answer 2

This is a class diagram in a very abstract or initial form , because all relationships are shown as an association .

Usually we start with such a class diagram, and then continue refinement by transforming the association (arrow, as shown above) into stronger relationships, such as generalization, composition, implementation, etc.

Association is seen as a weaker form of relationship between classes. Thus, a finite class diagram should have fewer associations.

Answer 3

This class diagram is incorrect because there is confusion between Java EE stereotypes and class names!

What are the stereotypes of << class module>> , << module>> and Session , Session persistence names should be Java EE stereotypes. If it is stored in the database, then this is the essence! Perseverance etc. It can be written by attributes. This chart does not make sense!

The main advantage of the diagram in this diagram is that if you use a code generator such as AndroMDA, MIA software or Blue Age, then you can generate your database directly from the model. These tools look at stereotypes during code generation.

If you do not want to generate code from the model, but prefer that the hibernate mapping do the job, then the entity stereotype can be written as an annotation in your Java code. Then, thanks to live code and model synchronization, hibernate can take the annotation and create a mapping.

That's why stereotyping is really very important, and using the wrong stereotype can be a very serious mistake!

Answer 4

What is the purpose or purpose of this chart? If these are classes and relationships, then this is a class diagram. If this is a comparison between classes and levels of function or responsibility in the system, then it looks like a layer diagram. These columns look like layers: presentation, business logic, data ...

Answer 5

Now I see the problem after a good sleep :-)

This seems to be a powerpoint diagram, not a class diagram, because you cannot have a straight line in the class diagram. I mean, you cannot have 3 delimiters like Presentation / objectos ....... etc.

This powerpoint tried to use a class diagram and added headers to separate 3 layers. The problem is that the class diagram is incorrect, and this is not because you present it with 3 layers so that it becomes correct! This is a poor understanding of what JPA stereotypes mean inside class diagrams.

Answer 6

It looks like a class diagram that uses “swimlanes” in the background to facilitate some kind of MVC.