UML class diagram

• generalization

It can be understood as inheritance , Standard interpretation ： is-a Relationship ,

• Realization

  Inherited abstract class , Implementation interface , All belong to implementation

• relation

  One class knows the properties and methods of another class

• polymerization

  The relationship between the whole and the part , Part can leave the whole , Such as car engine , tire

• Combine

  The relationship between the whole and the part , The part cannot exist alone without the whole , company department

• rely on

  local variable , Method , Parameters or calls to static methods

• The strength of each relationship generalization = Realization > Combine > polymerization > relation > rely on

1. Combine company There can be multiple departments , The department cannot leave the company ,—— Member variables of non collection classes
2. Departments can have multiple yard farmers —— Collection class member variables ,
3. Code farmers can have multiple mobile phones —— Member variables
4. Coder relies on multiple MAC —— Yes mac can coding, It can be understood as relying on mac To complete the method call
5. mac It's the expansion of computers —— Inherit
6. Computer is an implementation of the concept of processable computer —— Realization relationship

— Inherit
6. Computer is an implementation of the concept of processable computer —— Realization relationship