Re-reading "UML Foundation, Case and Application" (I.)

A long time without serious and complete reading a book, one is the work is busy, can not pull out, two people also become more and more dry, unable to calm down the heart.

Today is Sunday, the south rare a cool weather, the afternoon is relatively quiet, then from the bookshelf to turn out this book, formerly considered to have been over once, formed some rough concept, some time ago also listened to some Microsoft about the design mode of lectures, read some related articles, coupled with recent continuous do some minor projects, So there's been some improvement. I want to reread this book, there should be a different harvest it.

The UML (Unified Modeling Language) Unified Modeling Language is a visual modeling language that enables system constructors to build a system blueprint that expresses their imaginations in a standard, understandable way, and provides a mechanism for In order to effectively share and communicate design results between different people.

UML is the crystallization of the wisdom of Grady Booch, James Rumbaugh and Ivar Jacobson, they are called "three good Friends" by people. In 1997, the UML Alliance developed the UML1.0 version and submitted it to the OMG in response to the recommendation of the "Object Management Group" (Management group,omg) to solicit the standard modeling language from outside.

UML includes a number of graphical elements that can be grouped together into a chart.
1. Class Diagram
2. Object graph
3. Use case diagram
4. State diagram
5. Sequence diagram
6. Activity Chart
7. Collaboration diagram
8. Component Drawing
9. Deployment diagram

A new figure in UML2.0
1, composition structure diagram: Used to put a component class into a whole
2. Interactive overview diagram: Using sequence diagram or collaboration diagram to describe some activities in the activity diagram, the interactive overview is obtained.
3. Timing Chart: Indicates the duration of the object in a state.
4, there are innovative also have a reserved package diagram: Like a folder.

Previously thought that the program is the most important part of the project, and now increasingly found that system analysis is more important, especially now the development tools more and more automation, writing code more and more become a "no technical content" thing. And how to design the perfect system architecture according to the customer's demand is an important step to the success of the project. UML is actually a kind of graphical tool, it through some standardized graphics, the needs of the image to draw out, so that everyone can understand, and understand what to do, and so everyone in the help of these graphs to understand the needs of the right, the system analyst can be based on this thing to design the architecture, the programmer to complete the code.