Recommended book: UML object-oriented modeling Basics

In the past, I felt that I could not use UML. I didn't know what I was doing, that is, I knew there was a use case diagram, a class diagram, and a sequence diagram. At most, I wanted to express my needs, express the design to reach consensus. I recently worked on a project to know that UML is actually quite useful. From requirement to analysis, from analysis to design, from design to coding, UML is useful, in addition, I feel that correct use of UML can improve the project success rate.
Later, I read Xu Feng's article series "Practical oo" from the magazine programmer. This gives me a deeper understanding of the objects and OO, and explains them step by step, once you read it, you can use it. Later, the author wrote a book based on this series of articles, that is, the book I recommended to you, "UML surface Object Modeling basics". I have been here for several days, the UML overview, class diagram, object diagram, package diagram, use case diagram, and construction diagram are all well discussed and suitable for beginners of UML, or someone who has been running the program for several years but does not have a deep understanding of OO and cannot use it flexibly. The entire book has a reasonable architecture. First, I introduced the overview of UML (both useful and rarely explained concepts of empty theory), and then I gradually introduced several big charts of UML (uml2.0, I have introduced several more diagrams than uml1.0.) Then I have explained requirement modeling, design modeling, and database modeling in several sections. Finally I have explained how Rose has been used for model management.
At the beginning of each section, the knowledge points in this chapter are also drawn graphically, which is very vivid and easy to remember. There are also a number of actual examples for the specific description, so that you can know how to draw the example when you want to draw a picture. The book also introduces some principles for using UML, which are accumulated by the author's experience. It is better to draw a picture than to draw multiple pictures. The author gave a guide to what kind of pictures to draw and what kind of pictures to read, and followed them step by step to avoid detours. There are exercise questions behind each section. After reading a chapter, you can try to do exercises to consolidate and help you remember. The arrangement is especially reasonable.
UML is indeed a basic thing and has benefited from early learning. You have to learn the design pattern, learn the architecture design, learn the reconstruction, even the UML diagram can not understand, can not draw, it is very difficult to learn. First, we must have oo ideas, so that we can have OO design. With OO design, we can write OO programs. Of course, it is not that the program is more Oo, the better. In short, I feel that this book has helped me a lot and recommended good things to everyone. I hope that after reading this book, you can truly use UML and use it well to improve your coding quality, to improve the project success rate, I think this is also the goal of the author.
The book is not thick, more than 200 pages, the price is not expensive, more than 20. The key is to help us. We can't write code every day. It's time to stop and lay the foundation.