UML structure

by David H
The article that I read for this week talks about difference type of UML diagrams. However, the author concentrates more about characteristic of transformation operation. There are nine types of UML diagrams which are class diagram, sequence, collaboration, state chart, activity, object, component, deployment, and use case diagram. Transformation operation will take UML diagrams as it operand which is source diagram and produce another diagram of different type of diagram. That diagram is a target diagram. There are four categories of transformation operation which are full transformation, strong transformation, support transformation, and weak transformation.

For full transformation operation, what it does is to full convey the information of source diagram to target diagram. Therefore the full transformation operation will visualize the different diagram and produces the same model. For strong transformation, it used the semantic relationship of difference “metamodel”. The sequence diagram can construct use case and strong transformation operation will engineering the process and generate the code. On the other hand, support transformation is two diagram type do not share the amount of data on “metamodel” level. In addition it interacts on user. For weak transformation, the target diagram will contain small amount of information. However, it uses starting point to create a template diagram and construct new diagram.

This article relates to class because we have discussed about UML which is domain model, use case, sequence diagram, in class last time. I believe understanding the UML very important because it helps us to plan out the design on how we want the program or website work. It likes the frame work. All we need to do is writing code for it.

Reference

Selonen, P., Koskimies, K., & Sakkinen, M. (2003). Transformations between UML diagrams. Journal of Database Management, 14(3), 37-55.

5 thoughts on “UML structure”

  1. I did not realize that there were that many different kinds of UML diagrams, because I remember we only talked about 4 or 5 diagrams in class. So the transformation diagrams takes a current UMl diagram and transforms it to a different type of diagram, for example a use case diagram or a sequence diagram? I am kind of confused on that part.

  2. I also did not realize that there were more than 5 UML diagrams that we talked about in class. The transformation diagram seems like there is a lot to it and also seems like it could be helpful if you know how to use it. thanks for the great article.

  3. great article and well descriptive summary! I actually wrote about UML diagram as well but i focused on the basics of it. However, after reading your article I was like wow! There are many more than what we just talked about in the class. I hope to learn about them all. once again great article thanks for sharing.

  4. UML is far more complex than what I had imagined. I agree with OP in the sense that it is very important to understand UML as its the foundation to the program or website you’re designing. I do wish that when I was taking CIS 235 that we would’ve went further in detail in some of the different kinds of diagrams.

  5. Wow, there are a lot of different UML diagrams! I though we went over all of them in class but I guess I was mistaken. With the transformation diagram, that seems like a real complex one to understand but like Daniel said, I think it could be real beneficial to a person after they know how to use it. Found your article very informative.

Comments are closed.