UML 2.0 Deployment Diagrams

UML 2.0 Deployment DiagramsWelcome to my UML 2.0 Deployment Diagrams tutorial. You use deployment diagrams to show how software and hardware work together.

In this tutorial, I explain how to use nodes, artifacts, dependency arrows, communication lines, deployment specs and much more.

Following the video, you’ll find a deployment diagram cheat sheet. You should use that to help you understand everything covered in the video and as a cheat sheet for the future.

If you like videos like this, it helps to tell Google [googleplusone]

Share if you know anyone interested in UML 🙂

UML Deployment Diagram Cheat Sheet

Click the image below to show it full screen

UML Deployment Diagram Cheat Sheet

2 Responses to “UML 2.0 Deployment Diagrams”

  1. Sid Rajan says:

    Hello Derek,

    Thanks for your informative and enjoyable videos. They really help me with my computer science and programming class. I am in high school and my dream is to be a computer programmer one day. Watching your videos are helpful, but for the tests in my class, I need to use my textbook. I wanted to ask you if you have any general suggestions for reading programming books and understanding the material without having to force it in? I tried some of the methods from you Study Methods video and it doesn’t seem to work that well with computing classes and textbooks. What is the best way to fully and deeply learn programming concepts and constructs? Any help would be greatly appreciated!

    • admin says:


      I learned in the days before video tutorials. I learned by studying one thing like looping. Then I would make my own program that utilized that part of the language. Then I’d read the next chapter on decision making for example and either add that new tool to the previous program or make a new one. Each program used everything I had previously learned. Because I learned by re-writing everything over and over eventually I just remembered.

      By the time I reached the end of a book I would have a folder full of programs. I then copied and pasted from those programs to make more complicated stuff. I did my best to help you build that library of code. In the real world you aren’t forced to memorize everything. If you forget something you just look into your previous code. After a while you remember the most important things.

      Try to apply programs to whatever you are interested in. I used to be very into stats so I would make a bunch of programs like that. If you are into games, start by making a text based game like Zork. Then move towards 2d stuff. If you make simple games that are fun, your more complicated games will be awesome because you learned the importance of story telling and interaction.

      Have fun! If you don’t have fun it will just be another thing you have to do. If you have fun though you’ll realize that you can make just about anything imaginable through programming. You’ll be able to automate work, make games, make cool stuff that you can show friends, etc. Programming is about making cool stuff and not memorizing like many teachers think.

      I hope that helps

Leave a Reply

Your email address will not be published.