How did you learn UML? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or 开发者_运维百科expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 10 years ago.

I'm going to start learning and using UML.

I need to know what considerations do you suggest for me? What is the best way to learn effectively it do you think?

Thank you

---

In a class named SE101- Software Engineering 1A at CPIT in New Zealand.

In my opinion, you'll find that sequence and use case diagrams will be essential for getting ideas across to non-programmers, and class diagrams (and object diagrams, to a lesser extent), for communicating ideas to other code-monkeys.

Plus, many programming books that you may read in the future, Design Patterns, for example, will use UML diagrams (class and object, mostly) to show the structure of the patterns. Knowing UML will make understanding these books a lot easier. Documentation, too, to a lesser extent.

---

I never did, and I never will. Modelling is not about mastering a type of discipline, good models don't need UML to be understood.

---

First, get a book/tutorial and try to understand the basics (definitions, models drawing, ...) then, learn by example and practice, imagine or use a real problem and try to model it.

---

UML Distilled by Martin Fowler together with Applying UML And Patterns by Craig Larman, makes you understand the concept of UML and how to use it - as well the whole process with UP and so forth.

---

I started by reading an introductory book - Martin Fowler UML Distilled was quite good. Than I decided I really want to know how to use it, so I read a book about UML2 and UP (Unified Process) by Jim Arlow and Ila Neustadt. Afterward I had opportunity to take software engineering basics lecture at university which made me create simple specification with few diagrams. Afterward I took UML lecture, where I had again to create some UML diagrams. Now I am in the phase when UML is clear and I feel I need more knowledge about OO modeling, so I read a book on object oriented data modeling and object oriented programming and there are Use Cases by Alistair Cockbourne and some analytical patterns ahead for me. In between I read much of the model driven stuff and listened to SE Radio about all UML stuff - http://www.se-radio.net/tags/uml .

---

http://www.smartdraw.com/resources/tutorials/uml-diagrams/#/resources/tutorials/Getting-Started

This link was very helpful for me to learn modeling with UML. For open source solutions check out Dia, and dia2code.

---

I read Martin Fowler's UML Distilled. That's all you need. It's thin, dense book that's unmatched on that topic.

---

• I have several UML books, UML Distilled book from Addison Wesley comes to mind,
• then it all gets familiar when you start reading Design Pattern books that illustrates the concepts using UML Diagrams.
• I also use UML when I sketch a design.

---

You can only focus on 2 diagrams and start modeling almost immediately. Usecase diagrams require reading but class diagram can be done at the same time as the code. It means that in less than 3 hours you can model.

Usecase diagram is simple and will help you to define the scope of your project.

Class diagram will define the physical architecture and can therefore be learned at the same time as codding if you use a tool having live code and model synchronization.

Don't spend time on model driven and code generation from a model because nobody really use it today !!

---

Inventor. Sequence diagrams look more like business processes and usecases rather unstandardized.