Object Oriented Modeling and Design with UML, 2e

Good book for oops conceptNice chaptersThanks for best value Amazon

Nice book with so much example.highly helpful for my semester exam also.. thanks 😊

The media could not be loaded. Good conditionGood page qualityAwesome priceGood content

pros:A nice reference..cons:You can't use this as text book if you plan to learn the uml concepts...I recommend going with headFirst OOAD and then you buy this book.....conclusion:If you already know uml concepts and want to learn some new tricks , go with this book....If you are totally new to uml , OOAD, I recommend you should use HeadFirst OOAD book

Books cover almost all the units of the MCA UML exam

Good Overall ExperienceTimely Delivery of Product

Awesome book

Nice

The description said it was in good condition, no writing or marks and it is even better. Great condition and I’m very happy with the purchase. I would but from them again.

Solid book, ended up using it very often. No Sol' manual though, which made checking answers a little bit difficult, especially if your professor is tight around the edges.All together, great book, learned quite a lot about program design

UML is still a pretty new notation language which is developing as we speak. An experienced programmer may run into some small ambiguities, where there is no concrete way to do something.There are various names and notations for several things in UML. The capitalizations/small case for state diagrams may not always match up with other books, and some things can be drawn in more than one way. For instance, a pentagon to describe the entire diagram may exist or not be used at all in some cases.The discrepencies not only show the language's slow progression because of many differing opinions of language developers, but it is also a good indication of how difficult it may be to notice and understand how functions and drawings are to be interpretted between books and software usage. What's also interesting is that Rumbaugh has written various UML books, so he is aware of many of these differences. The question is whether authors as a team could only agree on a certain way to write the book, or if Rumbaugh was more in a hurry with the others to just get books done and printed to make money. If Rumbaugh comes out with a book on his own, it may be worth considering strongly! The same could probably be true for Blaha.Like many UML books probably, the book doesn't help you become aware of something like if an interface cannot be pointing to another interface. That is a more simpler example, but there are much more complex case whereas if you do not have a good grip on computer languages, it probably won't make much sense. Even though I cannot expect a book to cover most of these type of things, I think a book can attempt to cover some of these things so that a beginner could learn more easily. Part of the problem is because the language is still developing, and people just want to get books printed. If you know your UML well, here's your chance!You can still pass a course not knowing any of the idiosyncracies, but at a graduate level, it will not be a fulfilling way to learn.The way the book goes over the content it does cover, it does it very well. There are some things missing such as differing ways to show the same things, or it does not elaborate on topics enough that one would probably need to know for a graduate level course.

Thanks

Good Product. Received in a timely manner.