blocks|key|2353551|text|维基百科列出了一个相当全面的列表：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2353552|哲学|offset|length|2353553|敏捷软件开发|unordered-list-item|2353554|敏捷统一过程(AUP)|2353555|行为驱动开发(BDD)|2353556|大设计前沿(BDUF)|2353557|布鲁克斯定律|2353558|大教堂和集市|2353559|代码与修复|2353560|建构主义设计方法学(CDM)|2353561|牛仔编码|2353562|晶莹剔透|2353563|设计驱动开发(D3)|2353564|不要重复自己(干)或一次和一次(OAOO)，单点真理(SPoT)|2353565|动态系统开发方法(DSDM)|2353566|极限编程(XP)|2353567|特征驱动开发|2353568|好莱坞原则|2353569|迭代和增量开发|2353570|联合应用程序设计，又名JAD或“联合应用程序开发”|2353571|凯岑|2353572|看板|2353573|亲吻原则(保持简单，愚蠢)|2353574|精益软件开发|2353575|Microsoft解决方案框架(MSF)|2353576|模型驱动架构(MDA)|2353577|开源|2353578|开放统一过程|2353579|快又脏|2353580|Rational统一过程(RUP)|2353581|Scrum|2353582|智能(敏捷开发)|2353583|关注点分离(SoC)|2353584|面向服务的建模|2353585|软件工艺|2353586|软件系统安全|2353587|螺旋模型|2353588|测试驱动开发(TDD)|2353589|统一处理(UP)|2353590|V-模型|2353591|瀑布模型|2353592|轮辐模型|2353593|更糟的是更好的(与麻省理工学院的方法相比，新泽西风格)|2353594|特雷|2353595|你不会需要它的(YAGNI)|2353596|零一无限|2353597|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/List_of_software_development_philosophies^0|0|0|2|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|34|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|35|8|@]|9|@$D|36|E|37|1|38]]|A|$]]|$1|F|3|G|5|H|7|39|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|3A|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|3B|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|3C|8|@]|9|@]|A|$]]|$1|O|3|P|5|H|7|3D|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|3E|8|@]|9|@]|A|$]]|$1|S|3|T|5|H|7|3F|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|3G|8|@]|9|@]|A|$]]|$1|W|3|X|5|H|7|3H|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|H|7|3I|8|@]|9|@]|A|$]]|$1|10|3|11|5|H|7|3J|8|@]|9|@]|A|$]]|$1|12|3|13|5|H|7|3K|8|@]|9|@]|A|$]]|$1|14|3|15|5|H|7|3L|8|@]|9|@]|A|$]]|$1|16|3|17|5|H|7|3M|8|@]|9|@]|A|$]]|$1|18|3|19|5|H|7|3N|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|H|7|3O|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|H|7|3P|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|H|7|3Q|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|H|7|3R|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|H|7|3S|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|H|7|3T|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|H|7|3U|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|H|7|3V|8|@]|9|@]|A|$]]|$1|1Q|3|1R|5|H|7|3W|8|@]|9|@]|A|$]]|$1|1S|3|1T|5|H|7|3X|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|H|7|3Y|8|@]|9|@]|A|$]]|$1|1W|3|1X|5|H|7|3Z|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|H|7|40|8|@]|9|@]|A|$]]|$1|20|3|21|5|H|7|41|8|@]|9|@]|A|$]]|$1|22|3|23|5|H|7|42|8|@]|9|@]|A|$]]|$1|24|3|25|5|H|7|43|8|@]|9|@]|A|$]]|$1|26|3|27|5|H|7|44|8|@]|9|@]|A|$]]|$1|28|3|29|5|H|7|45|8|@]|9|@]|A|$]]|$1|2A|3|2B|5|H|7|46|8|@]|9|@]|A|$]]|$1|2C|3|2D|5|H|7|47|8|@]|9|@]|A|$]]|$1|2E|3|2F|5|H|7|48|8|@]|9|@]|A|$]]|$1|2G|3|2H|5|H|7|49|8|@]|9|@]|A|$]]|$1|2I|3|2J|5|H|7|4A|8|@]|9|@]|A|$]]|$1|2K|3|2L|5|H|7|4B|8|@]|9|@]|A|$]]|$1|2M|3|2N|5|H|7|4C|8|@]|9|@]|A|$]]|$1|2O|3|2P|5|H|7|4D|8|@]|9|@]|A|$]]|$1|2Q|3|2R|5|H|7|4E|8|@]|9|@]|A|$]]|$1|2S|3|2T|5|H|7|4F|8|@]|9|@]|A|$]]|$1|2U|3|2V|5|H|7|4G|8|@]|9|@]|A|$]]|$1|2W|3|-4|5|6|7|4H|8|@]|9|@]|A|$]]]|2X|$2Y|$5|2Z|30|31|A|$32|33]]]]

A fairly comprehensive list from Wikipedia:

<a href="http://en.wikipedia.org/wiki/List_of_software_development_philosophies" rel="noreferrer">http://en.wikipedia.org/wiki/List_of_software_development_philosophies</a>

<ul>
<li>Agile software development</li>
<li>Agile Unified Process (AUP) </li>
<li>Behavior Driven Development (BDD) </li>
<li>Big Design Up Front (BDUF) </li>
<li>Brooks's law </li>
<li>Cathedral and the Bazaar </li>
<li>Code and fix </li>
<li>Constructionist design methodology (CDM) </li>
<li>Cowboy coding </li>
<li>Crystal Clear </li>
<li>Design-driven development (D3) </li>
<li>Don't repeat yourself (DRY) or Once and Only Once (OAOO), Single Point of Truth (SPoT) </li>
<li>Dynamic Systems Development Method (DSDM) </li>
<li>Extreme Programming (XP) </li>
<li>Feature Driven Development </li>
<li>Hollywood Principle </li>
<li>Iterative and incremental development </li>
<li>Joint application design, aka JAD or "Joint Application Development" </li>
<li>Kaizen </li>
<li>Kanban </li>
<li>KISS principle (Keep It Simple, Stupid) </li>
<li>Lean software development </li>
<li>Microsoft Solutions Framework (MSF) </li>
<li>Model-driven architecture (MDA) </li>
<li>Open source </li>
<li>Open Unified Process </li>
<li>Quick-and-dirty </li>
<li>Rational Unified Process (RUP) </li>
<li>Scrum </li>
<li>Smart (agile development) </li>
<li>Separation of concerns (SoC) </li>
<li>Service-oriented modeling </li>
<li>Software Craftsmanship </li>
<li>Software System Safety </li>
<li>Spiral model </li>
<li>Test-driven development (TDD) </li>
<li>Unified Process (UP) </li>
<li>V-Model </li>
<li>Waterfall model </li>
<li>Wheel and spoke model </li>
<li>Worse is better (New Jersey style, as contrasted with the MIT approach) </li>
<li>Xtreme </li>
<li>You Ain't Gonna Need It (YAGNI) </li>
<li>Zero One Infinity </li>
</ul>

blocks|key|827919|text|高内聚力+--你正在设计的模块的职责是多么专注。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|827920|低耦合+-模块依赖于其他模块的程度。|827921|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Cohesion_(computer_science)|1|http://en.wikipedia.org/wiki/Coupling_(computer_science)^0|0|4|0|0|0|3|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

<a href="http://en.wikipedia.org/wiki/Cohesion_(computer_science)" rel="nofollow noreferrer">High Cohesion</a> - How focused are the responsibilities of the modules you are designing.

<a href="http://en.wikipedia.org/wiki/Coupling_(computer_science)" rel="nofollow noreferrer">Low Coupling</a> - The degree to which modules rely on other modules.

blocks|key|2353407|text|接吻|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2353408|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/KISS_principle^0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

blocks|key|944804|text|选择组合而不是继承，是一体的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|944805|许多人，特别是那些刚开始使用OO的人，当他们真正需要的是使用组合时，就会开始扩展类。真的，如果你问你自己，新的B级是A级吗？如果没有，你就不应该延长。|944806|例如，假设我有一个Person类，一个Car类，我想创建一个名为DrivenCar类的新类。一个简单的实现就是说(让我们假设我们获得了多个继承)|offset|length|style|CODE|944807|class+DrivenCar+extends+Person,+Car++{+...+}|code-block|syntax|javascript|944808|DrivenCar是一种人吗？不，所以它不应该是延长人。DrivenCar是一辆车吗？是的，所以有必要扩展|944809|使用组合时，植入看起来就像|944810|class+DrivenCar+extends+Car+{
++++private+Person+driver;
}|944811|entityMap^0|0|0|9|6|J|3|W|9|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@$F|Z|G|10|H|I]|$F|11|G|12|H|I]|$F|13|G|14|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|17|8|@]|9|@]|A|$]]|$1|S|3|T|5|L|7|18|8|@]|9|@]|A|$M|N]]|$1|U|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|V|$]]

Chose composition over inheritance, is one.

Many people, especially those new to OO will start extending classes when all they really need to is to use composition. Really if you should ask your self, is the new class B a Class A? If not then you shouldn't extend.

For example, let's say I have a <code>Person</code> Class, a <code>Car</code> Class, and I would like to make a new class called a <code>DrivenCar</code> class. A naive implementation would be to say (let's pretend we got multiple inheritance)

<pre><code>class DrivenCar extends Person, Car { ... }
</code></pre>

Is the DrivenCar a type of Person? No so it shouldn't be extending Person. Is the DrivenCar a Car? yes so it makes sense to extend

Using composition the implmentation would look like 

<pre><code>class DrivenCar extends Car {
 private Person driver;
}
</code></pre>

blocks|key|828013|text|抓取模式。是的，它们看起来很琐碎。更像是精益求精的核心品质，其他的，更复杂的模式展示。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|828014|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/GRASP_%2528object-oriented_design%2529^0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

The <a href="http://en.wikipedia.org/wiki/GRASP_%28object-oriented_design%29" rel="nofollow">GRASP</a> patterns. Yes, they seem rather trivial. More like distillation down to core qualities that other, more involved patterns demonstrate.

blocks|key|945537|text|雅格尼|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|945538|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/YAGNI^0|0|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://en.wikipedia.org/wiki/YAGNI" rel="nofollow noreferrer">YAGNI</a>

blocks|key|2353608|text|接口。大多数设计模式都是基于接口和实现的分离。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2353609|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Interface. Most design patterns are based on separation of interface &amp; implementation.

blocks|key|2353640|text|当您的API预期增长时，请使用抽象类而不是接口。在接口中添加一个新方法需要更改实现它的所有类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2353641|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

When your API are expected to grow, use Abstract class instead of Interface. Adding a new method in Interface requires to change ALL the classes which implement it.

I am a huge fan of software design principles such as SOLID and DRY. What other principles exist for OO software design? 

Note. I’m not looking for answers like "comment your code" but instead looking for OO design principles like the ones discussed by <a href="http://butunclebob.com/ArticleS.UncleBob.PrinciplesOfOod" rel="nofollow noreferrer">Uncle Bob</a>.

OO Software Design Principles

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我非常喜欢软件设计原则，比如、SOLID和DRY。面向对象软件设计还存在哪些其他原则？请注意。我不是在寻找像“注释你的代码”这样的答案，而是寻找像所讨论的那样的面向对象设计原则。

问OO软件设计原则
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OO软件设计原则EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OO软件设计原则
EN