Write a customer review.
There's a problem loading this menu right now. Get fast, free shipping with Amazon Prime. Your recently viewed items and featured recommendations. View or edit your browsing history. Get to Know Us.
English Choose a language for shopping. Amazon Music Stream millions of songs. Amazon Drive Cloud storage from Amazon.
Alexa Actionable Analytics for the Web. AmazonGlobal Ship Orders Internationally. Amazon Inspire Digital Educational Resources. Amazon Rapids Fun stories for kids on the go. Amazon Restaurants Food delivery from local restaurants. One person found this helpful. This book is not even worth Rs. Most helpful customer reviews on Amazon.
Start reading Chapter 1 of this book for even just the first few pages, and for various topics, it will say to go to future Chapters. If you take a look at those future chapters, there will be notes on the side telling you to go back to Chapter 1 or to other chapters. You can run into infinite loops or dead ends not really picking up anything. It is possible to maybe find what you were looking for, or find that the explanation for it is just not sufficient.
If I'm trying to look for a topic to remember, this book is not an easy read with the index either. If you look up some topics in the index and go to all the pages listed, it may not list all the important pages.
Apr 13, Philip rated it really liked it Shelves: Goodreads helps you keep track of books you want to read. It is now the twenty-first century — to be precise — and UML has gained traction in our profession. I'd like to read this book on Kindle Don't have a Kindle? For example, it does not provide a way for a band manager to listen to songs from the different albums on the Billboard — i. There are no discussion topics on this book yet. Who other than the inventors of the Unified Modeling Language to write the definitive guide to it?
Sometimes, when I had to look for information on something, say a "use case" for instance, then I'd look that topic up in the index. I'd go to all the different pages listed in the index and it might not be what I was looking for. Then I'd have to look at the side of the page of usually the lowest or 2nd lowest numbered page listed by the indexed topic, and go to the Chapter s listed.
When I went to those chapter s I'd still have to scour the entire chapter s until I might find what I was looking for. An example was when I was trying to understand what one of the diagram types was, a "state diagram" I believe it was, as compared to say an "activity diagram. This book may have some good use, but I haven't found that yet. It's hard to read and hard to look things up, and hard to learn from if you don't already know much or anything that is for sure. It is not as much, however, a follow-on to Jacobson's classic analysis and methodology book "Object-Oriented Software Engineering," so do not expect to walk away from this book with everything you need to implement a formal development process.
Software Engineering Mit Der Unified Modeling Language (German Edition). Other editions Die Unified Modeling Language (UML) ist die Standardnotation fur. Grundkurs Software-Engineering mit UML: Der pragmatische Weg zu erfolgreichen Weg zu erfolgreichen Softwareprojekten (German Edition) ( German) 2., korr. und erw. edition (November 12, ); Language: German; ISBN
This book is destined to become a core text for software developers wishing to master object-oriented design, which makes the occasional lapses in technical editing all the more regrettable. The introductory chapters, which I suspect weren't given the same scrutiny from authors and editors as the "meat" of the book, have just enough minor mistakes to introduce a vague feeling of mistrust. Small things like using the "simple notation" for realization in a diagram without having yet introduced it in the text and referring to a code file as Hello.
This is doubly a pity because chapters contain some of the best advice in the book regarding the pragmatics of modeling. The core of the book, which presents a modeling notation and syntax designed to scale across the entire universe of software development, is far more formal.
Each chapter ends with a discussion of how the particular diagram or relationship is commonly modeled, a nice device but one that falls short of presenting a unified methodology. Rather, the success of the book is the presentation of a modeling framework which can support many different methodologies. Who other than the inventors of the Unified Modeling Language to write the definitive guide to it? Booch, Jacobson, and Rumbaugh have answered the call with this book describing UML syntax, semantics, and diagrams with great detail.
Throughout the book, the authors draw parallels to building architecture for corresponding UML elements for software architecture. There's effective use of two-color printing to distinguish metadiscourse and metadiagrams from actual UML diagrams.
In that regard, this book makes a better reference manual than a user's guide. I'd recommend getting this book to sit on the shelf when you have questions or want to solve an ambiguity, but stick with Martin Fowler's "UML Distilled" for the core UML that you'll use day-to-day. I have read both the User's Guide and the Reference Manual, which are generally intended to be bought as a pair.
The Reference Manual is better organized, and is an invaluable resource for anyone who does a lot of UML modeling. This book, however, is just a dump of UML information, fairly ecletic but not always in sufficient depth. It is good information, but the poor organization makes it useless after the initial reading.
However, something like "UML for Dummies" will also give you a good introduction, at a better price. If you will be modeling a lot, and want a deep understanding of UML, then it would be wiser to buy the Reference Manual instead.
Your recently viewed items and featured recommendations. View or edit your browsing history. Get to Know Us.