今天重温了这本经典，摘录出以下精华中的“精华”：
use case diagram: system boundary and the interactions with the outside world
use case: external view of the system, capturing user goal for tying together a set of scenarios(a sequence of steps describing an interaction between a user and a system)
feature(user story): may be a whole use case, a scenario in a use case, a step in a use case, or some variant behavior, usually end up being more fine grained than use cases
conceptual class diagram / CRC cards: responsibility, communication, domain model / language
package diagram: large scale system structure and dependencies (compile time)
composite structure (componenet) diagram: large scale system structure and dependencies (run time), with provided and required interfaces
sequence diagram: behavior and collaborations of several objects within a single use case
deployment diagram: phycial layout, which pieces of software(artifact, often the implementation of a component) run on what pieces of hardware or execution environment(node)
不过称这些是精华中的精华实在是以偏概全，倒不如说只是一些我个人使用UML的重点与思路，毕竟不同的团队或个人都有各自的设计习惯。