This textbook mainly addresses beginners and readers with a basic knowledge of object-oriented programming languages like Java or C#, but with little or no modeling or software engineering experience – thus reflecting the majority of students in introductory courses at universities. Using UML, it introduces basic modeling concepts in a highly precise manner, while refraining from the interpretation of rare special cases. After a brief explanation of why modeling is an indispensable part of software development, the authors introduce the individual diagram types of UML (the class and object diagram, the sequence diagram, the state machine diagram, the activity diagram, and the use case diagram), as well as their interrelationships, in a step-by-step manner. The topics covered include not only the syntax and the semantics of the individual language elements, but also pragmatic aspects, i.e., how to use them wisely at various stages in the software development process. To this end, the work is complemented with examples that were carefully selected for their educational and illustrative value. Overall, the book provides a solid foundation and deeper understanding of the most important object-oriented modeling concepts and their application in software development. An additional website offers a complete set of slides to aid in teaching the contents of the book, exercises and further e-learning material.
I've been fucked reading this book. It dazzles on top shelf of a self-claim UML expert. And he unhesitantly calls this the best one, the very first introductory book of both UML and the page. Having downloaded it and half way through this shit, I realized I've never been so wrong. This book is written by Germans, four Germans. Yes German is good, German is perfectionists, blah blah blah...but not in this motherfucking book. Why? Because the language of this trash is unreadable. uncomprehensible and systematically temper-challenging. I feels like it's the combination of a flowery Novelist and a disabled advanced bilingual academic who don't know what he is doing. I feel like the book is written by an alien, or a foreigner who learnt English to highest level but only the grammar. It cost me a day to make it to 2 pages. Every paragraph takes me hours and hours. Don't be persuaded. Yes they are experts. Yes they are professors and academics. But by no way this book is readable.
It's a big pain in the ass if you make it through even just half way of it.
The UML is an over-engineered notation (own vocabulary of concepts, too abstract, verbose, awkward) from early 2000s (times of J2EE, cult of XML, code generation from visual models :D )...
This book does a good job to serve as a concise reference book. Some less used diagrams like Deployment have just a single paragraph dedicated to them, so reference is not complete, but good enough.
Nice overview of UML. Used in our undergrad software engineering course as a reference. The lectures provide a high level overview. In various exercises students then need to actually create diagrams, using this book to understand the details of the various diagram types. Students use plantuml to create the diagrams -- which also has extensive documentation that combines well with this book.