All You Need to Know About UML Diagrams: Types and 5+ Examples

Article   on Technology Trends by Amit on Tallyfy

Design and run your business process in minutes

Sign up to see the full power of Tallyfy

Design your step-by-step workflow in minutes
Launch a process and track every task in your team
Make sure that no task ever slips through the cracks

Start for Free   or book a demo or see more



Tallyfy provides modern teams with amazingly easy workflow management. Get started for free


6 thoughts on “All You Need to Know About UML Diagrams: Types and 5+ Examples


  1. hello. you said “Not all of the 14 different types of UML diagrams are used on a regular basis when documenting systems and/or architectures”. Can you help me to give me some reference book that says it. Thank you. I hope you answer my question.


    1. Hello Wilda! Thank you for reading our post on UML diagrams and asking such a valuable question.
      There has been several research conducted related to this. I have linked two among many of the conducted research/surveys below:

      https://pdfs.semanticscholar.org/18fa/60329a3f466207faa3dc998dcaf1637befde.pdf

      and

      https://www.researchgate.net/publication/220373821_Dimensions_of_UML_Diagram_Use_A_Survey_of_Practitioners

      We hope this is the answer you were looking for and we will be glad to answer any further questions on the topic.


  2. Igor Ganapolsky Reply

    Thank you for this broad and comprehensive overview of UML diagrams. One thing I’ll say in response to your statement about Class Diagrams:
    ~”most software being created nowadays is still based on the Object-Oriented Programming paradigm”
    – actually, most software is taking the functional and reactive approach these days (i.e. RxJava, Node.js, Kotlin). How would you alter your Class Diagram to meet such a shift in thinking?


    1. Hi Igor,

      I think the basic notion still applies to micro-services. Instead of designing monolithic software, you’d instead design smaller micro-services which trigger from events. Such an approach is highly scalable and would also let you compute requests in parallel. So the difference to your design portion is that class diagrams are smaller and more numerous.

      I hope this helps?

      Amit



  3. Thanks for putting this together. I am learning from it; however, I think I found some issues with it in the Activity Diagram section. You may be confusing “activities” with “actions”. For example.

    “The example above depicts the set of activities that take place in a content publishing process.”

    I think is should be “The example above depicts the set of ACTIONS that take place in a content publishing process.” In this case process is the Activity. The rounded boxes represent actions, as far as I read somewhere else.
    Again, I maybe confused, but I think I am right about this.

Leave a Reply

Your email address will not be published. Required fields are marked *

Bring clarity to your entire team

With one tool, everyone sees the same workflows