This week's book giveaway is in the General Computing forum. We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line! See this thread for details.
jacob deiter wrote:In my current company,I am not given a opportunity to work in UML diagrams
Expert ,please help explain, how I can get experience in UML ?
Jacob
Learning the UML is the easy part, just get the book Joachim listed and read it about ten times. The experience takes more time and effort. Start by working on the experience by creating UML diagrams for yourself either at work or at home, even if this is on paper or a white board. The diagrams don't have to include the world in them, just do simple designs with enough so that you know where you are going as you code. Start with simple class diagrams and sequence diagrams (few do more than that anyway). Over time start using the UML as the language in which you talk to your co-works (think of it as a passive shove). If your manager wants to know what you did then draw him a UML picture.
I do understand your situation. I have used UML since 1996 when I trained in OOAD with Craig Larman. However, I too am currently in a company that makes almost no use of the UML and have almost no interest in learning it. However, over time I have forced them to learn the most basic UML because that is the only thing I draw on the white board.
You don't really need to read books because UML 2 changed a lot and books are getting rusty btw, Mr Larman is one of the only writer that I would recommend
Yes, books are getting rusty. But UML 2.0 was released 5 years ago. And even though I haven't followed the development of UML extensively, I have my doubts that the basics from version 2.0 to 2.2 have changed so dramatically that you cannot use a book for UML 2.0 to get started.
And for someone who never dealt with UML before your provided tutorial is not at all sufficient and the advice that "you don't really need to read books" is in my opinion misleading.
A good book that shows how to get to code from requirements, through analysis and design, is Use Case Drive Object Modeling with UML by Doug Rosenberg and Matt Stephens. I highly recommend it.
0
