Learn how to make classes, attributes, and methods in this UML Class Diagram tutorial. There’s also in-depth training and examples on inheritance, aggregation, and composition relationships.

UML (or Unified Modeling Language) is a software engineering language that was developed to create a standard way of visualizing the design of a system. And UML Class Diagrams describe the structure of a system by showing the system’s classes and how they relate to one another.

This tutorial explains several characteristics of class diagrams. Within a class, there are attributes, methods, visibility, and data types. All of these components help identify a class and explain what it does.

There are also several different types of relationships that exist within UML Class Diagrams. Inheritance is when a child class (or subclass) takes on all the attributes and methods of the parent class (or superclass). Association is a very basic relationship where there’s no dependency. Aggregation is a relationship where the part can exist outside the whole. And finally, Composition is when a part cannot exist outside the whole. A class would be destroyed if the class it’s related to is destroyed.

Further UML Class Diagram information: https://www.lucidchart.com/pages/uml-class-diagram

——

Learn more and sign up:
http://www.lucidchart.com

Follow us:
Facebook: https://www.facebook.com/lucidchart
Twitter: https://twitter.com/lucidchart
Instagram: https://www.instagram.com/lucidchart
LinkedIn: https://www.linkedin.com/company/lucidsoftware

——

Credits for Photos with Attribution Requirements
Tortoise – by Niccie King – http://bit.ly/2uHaL1G
Otter – by Michael Malz – http://bit.ly/2vrVoYt
Slow Loris – by David Haring – http://bit.ly/2uiBWxg
Creep – by Poorna Kedar – http://bit.ly/2twR4K8
Visitor Center – by McGheiver – http://bit.ly/2uip0Hq
Lobby – by cursedthing – http://bit.ly/2twBWw9

source

48 Comments

  3. This is great. No other videos even come close to being as good as this. Thanks for the great explanation. Someday someone will explain UML diagram and actually show how it relates to code. So the video says that a tortoise can exist without being in a creep, but didn't say how. The assumption is that there is some other class that must have a property/member of List<tortoise> tortoises = new List<tortoise> … probably a 'zoo' class actual owns this list. But some of the tortoises aren't in the cool tortoise 'creep' click, so they don't get to be a part of that group … the List<tortoise> creep = new List<tortoise> … and who knows who owns this creep property … maybe the zoo owns this property too. However this is not mentioned, so it has taken a while to figure this concept out. NO video really explains this. What the relations actually look like when implemented in code. where do these things live; where do they get instantiated. are they passed around, referenced.

  4. Very well explained.

    If order id is duplicated among the several different customers, then isn't there any problem with this design? How do you resolve this issue? If resolved, what would be the new UML Class Diagram for that.

  15. Thanks to this tutorial I was able to begin to get through a ridiculously hard to understand course in Programming. You make something intermediate sound elementary while he makes it sound like rocket science. I'm using Lucidchart for the UML Class Diagrams I have to do in the course too.

  21. Wow . I have a software engineering exam at 9 am today ..it’s 4:34 am and I have to say this video is amazing thank you and wish me good luck ❤️love from Zimbabwe Africa

  26. the fact that i can understand this very well in just within 10mins+ , compare to my university classes that takes 2 weeks worth of time just to explain this, it just shows how most universities or colleges are either a scam or just straight out plain fraud.

  27. Excellent tutorial! When you use the symbols << something >> this specification is about of the stereotypes over kind of class. For example, if your class is of kind Data Entity or in particular another kind of class. The stereotype is only descriptive. Is correct? Excuse if my english ain't very good. Thank. Greets from Argentina. 😃

  28. This has really been a life saver. consise, to the point, no pushy ads. It sums up exactly what I needed for my test, and in less than a fraction of the time it would have taken me to go through the material myself. brief, but not rushed and genuinely fun to watch. This has been one of the best videos I've come across on this site.

  32. If I do student schedule and then tha student become a employee
    I DONT WANT TO REPATE THE SCHEDULE SO WHO CAN I UPGRADE THE STUDENT TO EMPLOYEE SCHEDULE
    WITHOUT REPATING IT

Leave A Reply

Please enter your comment!
Please enter your name here