{"id":18512692,"url":"https://github.com/knightsj/object-oriented-design","last_synced_at":"2025-04-06T20:12:06.009Z","repository":{"id":42040978,"uuid":"148023153","full_name":"knightsj/object-oriented-design","owner":"knightsj","description":"面向对象设计的设计原则和设计模式","archived":false,"fork":false,"pushed_at":"2019-03-24T03:44:19.000Z","size":1819,"stargazers_count":428,"open_issues_count":0,"forks_count":92,"subscribers_count":18,"default_branch":"master","last_synced_at":"2025-03-30T19:06:43.527Z","etag":null,"topics":["design-pattern","design-patterns","object-oriented","object-oriented-design","object-oriented-programming"],"latest_commit_sha":null,"homepage":"","language":"Objective-C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/knightsj.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2018-09-09T12:28:42.000Z","updated_at":"2025-03-25T02:47:43.000Z","dependencies_parsed_at":"2022-09-16T22:51:51.165Z","dependency_job_id":null,"html_url":"https://github.com/knightsj/object-oriented-design","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/knightsj%2Fobject-oriented-design","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/knightsj%2Fobject-oriented-design/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/knightsj%2Fobject-oriented-design/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/knightsj%2Fobject-oriented-design/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/knightsj","download_url":"https://codeload.github.com/knightsj/object-oriented-design/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":247543593,"owners_count":20955865,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["design-pattern","design-patterns","object-oriented","object-oriented-design","object-oriented-programming"],"created_at":"2024-11-06T15:35:04.109Z","updated_at":"2025-04-06T20:12:05.990Z","avatar_url":"https://github.com/knightsj.png","language":"Objective-C","readme":"\n![](res/banner.png)\n\n![](https://img.shields.io/badge/language-Objective--C-30A3FC.svg)\n[![](https://img.shields.io/badge/License-MIT-ff69b4.svg)](https://github.com/knightsj/object-oriented-design/blob/master/LICENSE)\n\n\n\n中文博客链接：\n\n- [面向对象设计的六大设计原则（附 Demo \u0026 UML类图）](https://juejin.im/post/5b9526c1e51d450e69731dc2)\n- [面向对象设计的设计模式（一）：创建型模式（附 Demo \u0026 UML类图）](https://juejin.im/post/5bcb0362e51d450e7042eb6d)\n- [面向对象设计的设计模式（二）：结构型模式（附 Demo \u0026 UML类图）](https://juejin.im/post/5bfd60455188257a5a24f2d4)\n- [面向对象设计的设计模式（三）：行为型模式（附 Demo \u0026 UML类图）](https://juejin.im/post/5c8df92151882545bc34f7a5)\n\n\n\n# Catalogue \u0026 Link\n\n- [Chapter 1: 面向对象设计原则（Object Oriented Design Principles）](\u003chttps://github.com/knightsj/object-oriented-design#chapter-1%E9%9D%A2%E5%90%91%E5%AF%B9%E8%B1%A1%E8%AE%BE%E8%AE%A1%E5%8E%9F%E5%88%99\u003e)\n\n  - [原则一：开闭原则（Open Close Principle）](\u003chttps://github.com/knightsj/object-oriented-design#%E5%8E%9F%E5%88%99%E4%B8%80%E5%BC%80%E9%97%AD%E5%8E%9F%E5%88%99open-close-principle\u003e)\n  - [原则二：单一职责原则（Single Responsibility Principle）](\u003chttps://github.com/knightsj/object-oriented-design#%E5%8E%9F%E5%88%99%E4%BA%8C%E5%8D%95%E4%B8%80%E8%81%8C%E8%B4%A3%E5%8E%9F%E5%88%99single-responsibility-principle\u003e)\n  - [原则三：依赖倒置原则（Dependency Inversion Principle）](\u003chttps://github.com/knightsj/object-oriented-design#%E5%8E%9F%E5%88%99%E4%B8%89%E4%BE%9D%E8%B5%96%E5%80%92%E7%BD%AE%E5%8E%9F%E5%88%99dependency-inversion-principle\u003e)\n  - [原则四：接口分离原则（Interface Segregation Principle）](\u003chttps://github.com/knightsj/object-oriented-design#%E5%8E%9F%E5%88%99%E5%9B%9B%E6%8E%A5%E5%8F%A3%E5%88%86%E7%A6%BB%E5%8E%9F%E5%88%99interface-segregation-principle\u003e)\n  - [原则五：迪米特法则（Law of Demeter）](\u003chttps://github.com/knightsj/object-oriented-design#%E5%8E%9F%E5%88%99%E4%BA%94%E8%BF%AA%E7%B1%B3%E7%89%B9%E6%B3%95%E5%88%99law-of-demeter\u003e)\n  - [原则六：里氏替换原则（Liskov Substitution Principle）](\u003chttps://github.com/knightsj/object-oriented-design#%E5%8E%9F%E5%88%99%E5%85%AD%E9%87%8C%E6%B0%8F%E6%9B%BF%E6%8D%A2%E5%8E%9F%E5%88%99liskov-substitution-principle\u003e)\n\n- [Chapter 2: 面向对象设计模式（Object Oriented Design Patterns）](\u003chttps://github.com/knightsj/object-oriented-design#chapter-2%E9%9D%A2%E5%90%91%E5%AF%B9%E8%B1%A1%E8%AE%BE%E8%AE%A1%E6%A8%A1%E5%BC%8F\u003e)\n\n  - [2.1 创建型设计模式](\u003chttps://github.com/knightsj/object-oriented-design#chapter-2%E9%9D%A2%E5%90%91%E5%AF%B9%E8%B1%A1%E8%AE%BE%E8%AE%A1%E6%A8%A1%E5%BC%8F\u003e)\n\n    - [2.11 简单工厂模式](\u003chttps://github.com/knightsj/object-oriented-design#211-%E7%AE%80%E5%8D%95%E5%B7%A5%E5%8E%82%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.12 工厂方法模式](\u003chttps://github.com/knightsj/object-oriented-design#212-%E5%B7%A5%E5%8E%82%E6%96%B9%E6%B3%95%E6%A8%A1%E5%BC%8F%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.13 抽象工厂模式](\u003chttps://github.com/knightsj/object-oriented-design#213-%E6%8A%BD%E8%B1%A1%E5%B7%A5%E5%8E%82%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.14 单例模式](\u003chttps://github.com/knightsj/object-oriented-design#214-%E5%8D%95%E4%BE%8B%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.15 生成器模式](\u003chttps://github.com/knightsj/object-oriented-design#215-%E7%94%9F%E6%88%90%E5%99%A8%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.16 原型模式](\u003chttps://github.com/knightsj/object-oriented-design#216-%E5%8E%9F%E5%9E%8B%E6%A8%A1%E5%BC%8F\u003e)\n\n  - [2.2 结构型设计模式](\u003chttps://github.com/knightsj/object-oriented-design#22-%E7%BB%93%E6%9E%84%E5%9E%8B%E8%AE%BE%E8%AE%A1%E6%A8%A1%E5%BC%8F\u003e)\n\n    - [2.21 外观模式](\u003chttps://github.com/knightsj/object-oriented-design#221-%E5%A4%96%E8%A7%82%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.22 适配器模式](\u003chttps://github.com/knightsj/object-oriented-design#222-%E9%80%82%E9%85%8D%E5%99%A8%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.23 桥接模式](\u003chttps://github.com/knightsj/object-oriented-design#223-%E6%A1%A5%E6%8E%A5%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.24 代理模式](\u003chttps://github.com/knightsj/object-oriented-design#224-%E4%BB%A3%E7%90%86%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.25 装饰者模式](\u003chttps://github.com/knightsj/object-oriented-design#225-%E8%A3%85%E9%A5%B0%E8%80%85%E6%A8%A1%E5%BC%8F\u003e)\n    - [2.26 享元模式](\u003chttps://github.com/knightsj/object-oriented-design#226-%E4%BA%AB%E5%85%83%E6%A8%A1%E5%BC%8F\u003e)\n\n  - [2.3 行为型设计模式](https://github.com/knightsj/object-oriented-design#23-%E8%A1%8C%E4%B8%BA%E5%9E%8B%E8%AE%BE%E8%AE%A1%E6%A8%A1%E5%BC%8F)\n\n    - [2.31 模板方法模式](https://github.com/knightsj/object-oriented-design#231-%E6%A8%A1%E6%9D%BF%E6%96%B9%E6%B3%95%E6%A8%A1%E5%BC%8F)\n    - [2.32 策略模式](https://github.com/knightsj/object-oriented-design#232-%E7%AD%96%E7%95%A5%E6%A8%A1%E5%BC%8F)\n    - [2.33 责任链模式](https://github.com/knightsj/object-oriented-design#233-%E8%B4%A3%E4%BB%BB%E9%93%BE%E6%A8%A1%E5%BC%8F)\n    - [2.34 状态模式](https://github.com/knightsj/object-oriented-design#234-%E7%8A%B6%E6%80%81%E6%A8%A1%E5%BC%8F)\n    - [2.35 命令模式](https://github.com/knightsj/object-oriented-design#235-%E5%91%BD%E4%BB%A4%E6%A8%A1%E5%BC%8F)\n    - [2.36 观察者模式](https://github.com/knightsj/object-oriented-design#236-%E8%A7%82%E5%AF%9F%E8%80%85%E6%A8%A1%E5%BC%8F)\n    - [2.37 中介者模式](https://github.com/knightsj/object-oriented-design#237-%E4%B8%AD%E4%BB%8B%E8%80%85%E6%A8%A1%E5%BC%8F)\n\n# Chapter 1：面向对象设计原则\n\n\n缩写 | 英文名称 | 中文名称\n---| ----| -----\nSRP | Single Responsibility Principle | 单一职责原则\nOCP | Open Close Principle | 开闭原则\nLSP | Liskov Substitution Principle | 里氏替换原则\nLoD | Law of Demeter （ Least Knowledge Principle） | 迪米特法则（最少知道原则）\nISP | Interface Segregation Principle | 接口分离原则\nDIP | Dependency Inversion Principle | 依赖倒置原则\n\n\n## 原则一：开闭原则（Open Close Principle）\n\n\n### 定义\n\n\u003e Software entities (classes, modules, functions, etc.) should be open for extension, but closed for modification.\n\n即：一个软件实体如类、模块和函数应该对扩展开放，对修改关闭。\n\n### 定义的解读\n\n- 用抽象构建框架，用实现扩展细节。\n- 不以改动原有类的方式来实现新需求，而是应该以实现事先抽象出来的接口（或具体类继承抽象类）的方式来实现。\n\n\n### UML 类图对比\n\n未实践开闭原则：\n![未实践开闭原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/OCP11.png)\n\n实践了开闭原则：\n![实践了开闭原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/OCP2.png)\n\n\n### Demo\n\n1. 未实践开闭原则：[OCPDemo1](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B2%5D.%20Open%20Close%20Principle/OCPDemo1)\n2. 实践了开闭原则：[OCPDemo2](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B2%5D.%20Open%20Close%20Principle/OCPDemo2)\n\n\n\n## 原则二：单一职责原则（Single Responsibility Principle）\n\n\n### 定义\n\n\u003eA class should have a single responsibility, where a responsibility is nothing but a reason to change.\n\n即：一个类只允许有一个职责，即只有一个导致该类变更的原因。\n\n\n### 定义的解读\n\n- 类职责的变化往往就是导致类变化的原因：也就是说如果一个类具有多种职责，就会有多种导致这个类变化的原因，从而导致这个类的维护变得困难。\n\n- 往往在软件开发中随着需求的不断增加，可能会给原来的类添加一些本来不属于它的一些职责，从而违反了单一职责原则。如果我们发现当前类的职责不仅仅有一个，就应该将本来不属于该类真正的职责分离出去。\n- 不仅仅是类，函数（方法）也要遵循单一职责原则，即：一个函数（方法）只做一件事情。如果发现一个函数（方法）里面有不同的任务，则需要将不同的任务以另一个函数（方法）的形式分离出去。\n\n\n\n\n### UML 类图对比\n\n未实践单一职责原则：\n![未实践单一职责原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/SRP11.png)\n\n实践了单一职责原则：\n![实践了单一职责原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/SRP2.png)\n\n### Demo\n\n\n1. 未实践单一职责原则：[SRPDemo1](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B1%5D%20.Single%20Responsibility%20Principle/SRPDemo1)\n2. 实践了单一职责原则：[SRPDemo2](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B1%5D%20.Single%20Responsibility%20Principle/SRPDemo2)\n\n\n\n## 原则三：依赖倒置原则（Dependency Inversion Principle）\n\n### 定义\n\n\u003e- Depend upon Abstractions. Do not depend upon concretions.\n\u003e- Abstractions should not depend upon details. Details should depend upon abstractions\n\u003e- High-level modules should not depend on low-level modules. Both should depend on abstractions.\n\n即：\n\n- 依赖抽象，而不是依赖实现。\n- 抽象不应该依赖细节；细节应该依赖抽象。\n- 高层模块不能依赖低层模块，二者都应该依赖抽象。\n\n\n### 定义解读\n\n\n- 针对接口编程，而不是针对实现编程。\n- 尽量不要从具体的类派生，而是以继承抽象类或实现接口来实现。\n- 关于高层模块与低层模块的划分可以按照决策能力的高低进行划分。业务层自然就处于上层模块，逻辑层和数据层自然就归类为底层。 \n\n\n\n### UML 类图对比\n\n未实践依赖倒置原则：\n\n![未实践依赖倒置原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/DIP1.png)\n\n实践了依赖倒置原则：\n![实践了依赖倒置原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/DIP22.png)\n\n### Demo\n\n1. 未实践依赖倒置原则：[DIPDemo1](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B6%5D.%20Dependency%20Inversion%20Principle/DIPDemo1)\n2. 实践了依赖倒置原则：[DIPDemo2](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B6%5D.%20Dependency%20Inversion%20Principle/DIPDemo2)\n\n\n\n## 原则四：接口分离原则（Interface Segregation Principle）\n\n\n### 定义\n\n\n\u003eMany client specific interfaces are better than one general purpose interface.\n\n即：多个特定的客户端接口要好于一个通用性的总接口。\n\n\n### 定义解读\n\n- 客户端不应该依赖它不需要实现的接口。\n- 不建立庞大臃肿的接口，应尽量细化接口，接口中的方法应该尽量少。\n\n需要注意的是：接口的粒度也不能太小。如果过小，则会造成接口数量过多，使设计复杂化。\n\n\n\n\n### UML 类图对比\n\n未实践接口分离原则：\n![未实践接口分离原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/ISP1.png)\n\n实践了接口分离原则：\n![实践了接口分离原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/ISP2.png)\n\n\u003e通过遵守接口分离原则，接口的设计变得更加简洁，而且各种客户类不需要实现自己不需要实现的接口。\n\n### Demo\n\n1. 未实践接口分离原则：[ISPDemo1](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B5%5D.%20Interface%20Segregation%20Principle/ISPDemo1)\n2. 实践了接口分离原则：[ISPDemo2](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B5%5D.%20Interface%20Segregation%20Principle/ISPDemo2)\n\n## 原则五：迪米特法则（Law of Demeter）\n\n\n### 定义\n\n\u003eYou only ask for objects which you directly need.\n\n即：一个对象应该对尽可能少的对象有接触，也就是只接触那些真正需要接触的对象。\n\n### 定义解读\n\n\n- 迪米特原则也叫做最少知道原则（Least Know Principle）， 一个类应该只和它的成员变量，方法的输入，返回参数中的类作交流，而不应该引入其他的类（间接交流）。\n\n\n### UML 类图对比\n\n未实践迪米特法则：\n![未实践迪米特法则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/LOD111.png)\n\n\n\n实践了迪米特法则：\n![实践了迪米特法则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/LOD2.png)\n\n\u003e很明显，在实践了迪米特法则的 UML 类图里面，没有了``Client``对``GasEngine``的依赖，耦合性降低。\n\n### Demo\n\n1. 未实践迪米特法则：[LODDemo1](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B4%5D.%20Law%20of%20Demeter/LODDemo1)\n2. 实践了迪米特法则：[LODDemo2](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B4%5D.%20Law%20of%20Demeter/LODDemo2)\n\n## 原则六：里氏替换原则（Liskov Substitution Principle）\n\n\n### 定义\n\n\u003eIn a computer program, if S is a subtype of T, then objects of type T may be replaced with objects of type S (i.e. an object of type T may be substituted with any object of a subtype S) without altering any of the desirable properties of the program (correctness, task performed, etc.)\n\n\n即：所有引用基类的地方必须能透明地使用其子类的对象，也就是说子类对象可以替换其父类对象，而程序执行效果不变。\n\n\n### 定义的解读\n\n在继承体系中，子类中可以增加自己特有的方法，也可以实现父类的抽象方法，但是不能重写父类的非抽象方法，否则该继承关系就不是一个正确的继承关系。\n\n\n\n### UML 类图对比\n\n未实践里氏替换原则：\n\n![未实践里氏替换原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/LSP11.png)\n\n\n\n实践了里氏替换原则：\n![实践了里氏替换原则](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-principle/LSP22.png)\n\n### Demo\n\n1. 未实践里氏替换原则：[LSPDemo1](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B3%5D.%20Liskov%20Substitution%20Principle/LSPDemo1)\n2. 实践了里氏替换原则：[LSPDemo2](https://github.com/knightsj/object-oriented-design/tree/master/%5B1%5D.%20Ojbect-Oriented%20design%20principle%20Demo/%5B3%5D.%20Liskov%20Substitution%20Principle/LSPDemo2)\n\n\n\n# Chapter 2：面向对象设计模式\n\n\n\n## 2.1 创建型设计模式\n\n\n\n创建型设计模式分为：\n\n\n\n1. 简单工厂模式（Simple Factory Pattern）\n2. 工厂方法模式（Factory Method Pattern）\n3. 抽象工厂模式（Abstract Factory Pattern）\n4. 单例模式（Singleton Pattern）\n5. 生成器模式（Builder Pattern）\n6. 原型模式（Prototype Pattern）\n\n\n\n\n\n### 2.11 简单工厂模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 简单工厂模式(Simple Factory Pattern)：专门定义一个类（工厂类）来负责创建其他类的实例。可以根据创建方法的参数来返回不同类的实例，被创建的实例通常都具有共同的父类。\n\n\n\n#### 模式类图\n\n![简单工厂模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_sfp_1.png)\n\n\n\n#### Demo\n\n\n\n- Demo地址：[Simple Factory Pattern Demo](\u003chttps://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B1%5D.%20Simple%20Factory%20Pattern%20Demo\u003e)\n\n- Demo UML：![简单工厂模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_sfp_2.png)\n\n\n\n\n\n\n\n### 2.12 工厂方法模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 工厂方法模式(Factory Method Pattern)又称为工厂模式，工厂父类负责定义创建产品对象的公共接口，而工厂子类则负责生成具体的产品对象，即通过不同的工厂子类来创建不同的产品对象。\n\n\n\n\n\n#### 模式类图\n\n![工厂方法模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_fmp_1.png)\n\n#### Demo\n\n\n\n- Demo地址：[Factory Method Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B2%5D.%20Factory%20Method%20Pattern%20Demo)\n\n- Demo UML：\n\n![工厂方法模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_fmp_2.png)\n\n### 2.13 抽象工厂模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 抽象工厂模式(Abstract Factory Pattern)：提供一个创建一系列相关或相互依赖对象的接口，而无须指定它们具体的类。\n\n\n\n#### 模式类图\n\n![抽象工厂模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_afp_1.png)\n\n#### Demo\n\n\n\n- Demo地址：[Abstract Factory Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B3%5D.%20Abstract%20Factory%20Pattern%20Demo)\n\n\n\n- Demo UML：\n\n![抽象工厂模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_afp_1.png)\n\n\n\n### 2.14 单例模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 单例模式(Singleton Pattern)：单例模式确保某一个类只有一个实例，并提供一个访问它的全剧访问点。\n\n\n\n#### 模式类图\n\n![单例模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_sp_1.png)\n\n#### Demo\n\n\n\n- Demo地址：[Singleton Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B4%5D.%20Singleton%20Pattern%20Demo)\n\n\n\n- Demo UML：\n\n  ![单例模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_sp_2.png)\n\n\n\n\n### 2.15 生成器模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 生成器模式(Builder Pattern)：也叫创建者模式，它将一个复杂对象的构建与它的表示分离，使得同样的构建过程可以创建不同的表示。\n\n\n\n\n\n#### 模式类图\n\n![生成器模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_bp_11.png)\n\n#### Demo\n\n\n\n- Demo Link: [Builder Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B5%5D.%20Builder%20Pattern%20Demo)\n\n\n\n- Demo UML：\n\n![生成器模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_bp_2.png)\n\n\n\n### 2.16 原型模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 原型模式（Prototype Pattern）: 使用原型实例指定待创建对象的类型，并且通过复制这个原型来创建新的对象。\n\n\n\n#### 模式类图\n\n![原型模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_pp_1111.png)\n\n#### Demo\n\n\n\n- Demo Link: [Prototype Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B6%5D.%20Prototype%20Pattern%20Demo)\n\n- Demo UML：\n\n![原型模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-creation/dp_pp_21.png) \n\n\n\n\n\n\n\n## 2.2 结构型设计模式\n\n\n\n### 2.21 外观模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 外观模式(Facade Pattern)：外观模式定义了一个高层接口，为子系统中的一组接口提供一个统一的接口。外观模式又称为门面模式，它是一种结构型设计模式模式。\n\n\n\n#### 模式类图\n\n![外观模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/fp_1.png)\n\n#### Demo\n\n\n\n- Demo Link：[Facade Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B7%5D.%20Facade%20Pattern%20Demo)\n\n- Demo UML：\n\n![外观模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/fp_2.png)\n\n\n### 2.22 适配器模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 适配器模式(Adapter Pattern) ：将一个接口转换成客户希望的另一个接口，使得原本由于接口不兼容而不能一起工作的那些类可以一起工作。适配器模式的别名是包装器模式（Wrapper），是一种结构型设计模式。\n\n\n\n#### 模式类图\n\n对象适配器模式：\n\n![适配器模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/ap_1.png)\n\n\n类适配器模式：\n![类适配器模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/ap_11.png)\n\n#### Demo\n\n\n\n- Demo Link：[Adaptor Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B8%5D.%20Adaptor%20Pattern%20Demo)\n\n- Demo UML：\n\n![适配器模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/ap_2.png)\n\n\n### 2.23 桥接模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 桥接模式(Simple Factory Pattern)：将抽象部分与它的实现部分分离,使它们都可以独立地变化。\n\n\n\n#### 模式类图\n\n![桥接模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/bp_11.png)\n\n\n#### Demo\n\n\n\n- Demo Link: [Bridge Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B9%5D.%20Bridge%20Pattern%20Demo)\n\n- Demo UML：\n\n![桥接模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/bp_2.png)\n\n\n### 2.24 代理模式\n\n\n#### 模式定义\n\n\n\n\u003e 代理模式(Proxy Pattern) ：为某个对象提供一个代理，并由这个代理对象控制对原对象的访问。\n\n\n\n#### 模式类图\n\n![代理模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/pp_1.png)\n\n#### Demo\n\n\n- Demo Link: [Proxy Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B10%5D.%20Proxy%20Pattern%20Demo)\n\n- Demo UML：\n\n![代理模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/pp_2.png)\n\n### 2.25 装饰者模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 装饰模式(Decorator Pattern) ：不改变原有对象的前提下，动态地给一个对象增加一些额外的功能。\n\n\n\n#### 模式类图\n\n![装饰者模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/dp_1.png)\n\n#### Demo\n\n\n\n- Demo Link: [Decorator Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B11%5D.%20Decorator%20Pattern%20Demo)\n\n- Demo UML：\n\n![装饰者模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/dp_2.png)\n\n\n### 2.26 享元模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 享元模式(Flyweight Pattern)：运用共享技术复用大量细粒度的对象,降低程序内存的占用,提高程序的性能。\n\n\n\n#### 模式类图\n\n![享元模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/fwp_1.png)\n\n#### Demo\n\n\n\n- Demo Link: [Flyweight Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B12%5D.%20Flyweight%20Pattern%20Demo)\n\n- Demo UML：\n\n![享元模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-structure/fwp_223.png)\n\n\n\n\n## 2.3 行为型设计模式\n\n### 2.31 模板方法模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 在模板模式（Template Method Pattern）中，定义一个操作中的算法的框架，而将一些步骤的执行延迟到子类中，使得子类可以在不改变算法的结构的前提下即可重新定义该算法的某些特定步骤。\n\n\n#### 模式类图\n\n![模板方法模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/tp_1.png)\n\n\n#### Demo\n\n\n\n- Demo Link: [Template Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B13%5D.%20Template%20Pattern%20Demo)\n\n- Demo UML：\n\n\n![模板方法模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/tp_2.png)\n\n\n\n\n### 2.32 策略模式\n\n\n\n#### 模式定义\n\n\n\u003e 策略模式(Strategy Pattern)：定义一系列算法，将每一个算法封装起来，并让它们可以相互替换。\n\n\n#### 模式类图\n\n![策略模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/stap_1.png)\n\n\n#### Demo\n\n\n\n- Demo Link: [Strategy Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B14%5D.%20Strategy%20Pattern%20Demo)\n\n- Demo UML：\n\n![策略模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/stap_2.png)\n\n\n### 2.33 责任链模式\n\n\n#### 模式定义\n\n\n\u003e 责任链模式（Chain of Responsibility Pattern）：为请求创建了一个接收者对象的链，每个接收者都包含对另一个接收者的引用。如果一个对象不能处理该请求，那么它会把相同的请求传给下一个接收者，依此类推。\n\n\n\n\n#### 模式类图\n\n\n![责任链模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/crp_1.png)\n\n\n#### Demo\n\n\n\n- Demo Link: \n  - Before refactoring:[Chain of Responsibilty Pattern Demo (before refactoring)](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B15%5D.%20Chain%20of%20Responsibilty%20Pattern%20Demo%20(before%20refactoring))\n  - After refactoring:[Chain of Responsibilty Pattern Demo (after refactoring)](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B16%5D.%20Chain%20of%20Responsibilty%20Pattern%20Demo%20(after%20refactoring))\n- Demo UML：\n\n  - Before refactoring：\n  ![责任链模式代码示例类图一](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/cp_2.png)\n\n  - After refactoring：\n  ![责任链模式代码示例类图二](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/cp_3.png)\n\n\n\n### 2.34 状态模式\n\n\n\n#### 模式定义\n\n\n\u003e 在状态模式（State Pattern）：允许一个对象在其内部状态改变时，改变它的行为。\n\n\n\n#### 模式类图\n\n\n![状态模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/sp_1.png)\n\n\n#### Demo\n\n\n\n- Demo Link: [State Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B17%5D.%20State%20Pattern%20Demo)\n- Demo UML：\n\n![状态模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/sp_2.png)\n\n\n### 2.35 命令模式\n\n\n\n#### 模式定义\n\n\n\u003e 命令模式(Command Pattern)：命令（或请求）被封装成对象。客户端将命令（或请求）对象先传递给调用对象。调用对象再把该命令（或请求）对象传给合适的，可处理该命令（或请求）的对象来做处理。\n\n\n\n#### 模式类图\n\n![命令模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/cd_1.png)\n\n#### Demo\n\n\n\n- Demo Link: [Command Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B18%5D.%20Command%20Pattern%20Demo)\n\n- Demo UML：\n\n![命令模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/cd_2.png)\n\n\n### 2.36 观察者模式\n\n\n\n#### 模式定义\n\n\n\n\u003e 观察者模式(Observer Pattern)：定义对象间的一种一对多的依赖关系，使得每当一个对象状态发生改变时，其相关依赖对象都可以到通知并做相应针对性的处理。\n\n\n\n#### 模式类图\n\n![观察者模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/op_1.png)\n\n\n#### Demo\n\n\n\n- Demo Link: [Obsever Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B19%5D.%20Observer%20Pattern%20Demo)\n\n- Demo UML：\n\n![观察者模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/op_2.png)\n\n\n### 2.37 中介者模式\n\n\n\n#### 模式定义\n\n\n\u003e 中介者模式(Mediator Pattern)：用一个中介对象来封装一系列的对象交互，中介者使各对象之间不需要显式地相互引用，从而使其耦合松散，而且可以独立地改变它们之间的交互。\n\n\n#### 模式类图\n\n![状态模式类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/mp_1.png)\n\n#### Demo\n\n\n\n- Demo Link: [Mediator Pattern Demo](https://github.com/knightsj/object-oriented-design/tree/master/%5B2%5D.%20Ojbect-Oriented%20design%20pattern%20Demo/%5B20%5D.Mediator%20Pattern%20Demo)\n\n- Demo UML：\n\n\n![中介者模式代码示例类图](http://jknight-blog.oss-cn-shanghai.aliyuncs.com/design-pattern-behavior/mp_2.png)\n\n\n# License\n\nThis repository is released under [MIT License](https://github.com/knightsj/object-oriented-design/blob/master/LICENSE)\n\n\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fknightsj%2Fobject-oriented-design","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fknightsj%2Fobject-oriented-design","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fknightsj%2Fobject-oriented-design/lists"}