blocks|key|1305189|text|不，他们不一样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1305190|模式是面向对象编程问题的常见解决方案。(我不知道在函数式或声明式编程方面有任何类似的书籍。)这个想法在1995年“四人帮”著名的“设计模式”一书中得到了具体化。|1305191|正如安德烈指出的那样，模式在每一种范式中都是常见的。我将重申我以前的声明:我不知道有任何类似的关于函数式或声明式编程的书籍，但是Andre已经用他提供的下面的链接来弥补我的无知。(谢谢你，安德烈)|1305192|原则不是关于特定语言或范例的，而是更一般的。“不要重复自己”--干原则--对所有程序来说都是正确的。|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

No, they aren't the same.

Patterns are common solutions to object-oriented programming problems. (I'm not aware of any similar books for functional or declarative programming.) The idea was crystallized in the famous "Design Patterns" book by the Gang of Four in 1995. 

As Andre points out, patterns are common in every paradigm. I'll reiterate my previous statement: I'm not aware of any similar books for functional or declarative programming, but Andre has remedied my ignorance with the link he provided below. (Thank you, Andre.) 

Principles are less about particular languages or paradigms, more general. "Don't Repeat Yourself" - DRY principle - is true for all programming.

blocks|key|5403626|text|这些概念不一样:|type|header-two|depth|inlineStyleRanges|entityRanges|data|5403627|*设计原则：*软件设计原则代表了一套指导方针，帮助我们避免出现错误的设计。喜欢:开闭原则|unstyled|5403628|*设计模式：*设计模式是对软件设计中给定上下文中常见问题的通用可重用解决方案。比如:辛格尔顿|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|I|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|J|8|@]|9|@]|A|$]]]|G|$]]

These concepts are not same :

*Design Principle : * Software design principles represent a set of guidelines that help us to avoid having a bad design. like: Open Close Principle

*Design Pattern : * a Design Pattern is a general reusable solution to a commonly occurring problem within a given context in software design. Like: Singleton

blocks|key|1305308|text|模式之于原则，正如实现之于模式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1305309|一个原则是“间接”，它可以通过一个“工厂”模式来实现，这个模式最终被实现为一个带有工厂方法的类。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

Patterns are to principles, what implementations are to patterns.

A principle would be "indirection", which could be accomplished by a "factory" pattern, which gets implemented as a class with factory methods in the end.

blocks|key|5403574|text|模式是比原则更高级的东西。模式可以解决特定的问题。原则可适用于任何地方，不论其背景如何。基于原则的实际模式(SRP、DRY等)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5403575|让我们看看战略模式。它定义了一组算法，封装了每一种算法，并使它们可以互换。所以，这里有一个高层次的算法概念。有了状态模式，您就有了高级的状态概念。有了原则，你就没有任何高层次的概念。原则是实现目标的基石，为模式所用。在实现策略模式时，可以使用SOLID：|5403576|SRP+-您定义代码，负责算法并从另一个代码中提取它。|unordered-list-item|5403577|OCP+-定义抽象，它表示所有不同的算法并使用它。|5403578|LSP+-在客户端代码中不使用具体的算法类，只使用抽象|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|N|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|P|8|@]|9|@]|A|$]]]|K|$]]

Patterns are more high-level things, than principles. Patterns resolve specific issues. Principles could be applied anywhere regardless of context. Actually patterns based on principles (SRP, DRY, etc)

E.G. Lets look on Strategy pattern. It defines a family of algorithms, encapsulates each one, and makes them interchangeable. So, you have here high-level concept of algorithm. With State pattern you have high-level concept of state. With principles you don't have any high-level concepts. Principles are building blocks, which used by patters to achieve goal. When you implement Strategy pattern, you use SOLID:

<ul>
<li>SRP - you define code, which responsible for algorithm and extract it from another code.</li>
<li>OCP - you define abstraction, which represents all different algorithms and use it</li>
<li>LSP - you don't use concrete algorithm classes in client code, only abstraction</li>
</ul>

blocks|key|5403596|text|原则是规则，模式是具体的例子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

Well, Principles are rules while patterns are their concrete examples.

blocks|key|5403659|text|最初为架构编写文档的模式。在建筑中，适用于从房间的门到村庄的布局的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5403660|“四人帮”将这一思想应用于面向对象编程.可能有多个可以用来解决问题的模式，但是每个模式都有一个特定的实现。在其他编程方法中存在模式，但我不知道有任何适用的书籍。正如其他人所提到的，模式涵盖特定的实现。当模式不适用时使用它通常被认为是反模式。|5403661|原则不包括实现，尽管可以有标准的实现方法。原则更多的是涉及一般问题，而不是具体问题。对于倒置控制，我知道至少有三种实现方法。对于DRY+(不要重复自己)，我不知道具体的实现方法，尽管我使用了几个。|5403662|考虑一下|5403663|您已经被要求使用抽象工厂模式这样的模式作为开发程序的唯一方法。这样做合适吗？不，那更有可能是一种模式。|unordered-list-item|5403664|你被要求在所有部件上涂干吗？这样做合适吗？是的，那么这更有可能是一个原则。|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|J|7|S|8|@]|9|@]|A|$]]]|M|$]]

Patterns where originally documented for Architecture. In architecture, apply to things ranging from placement of the door in a room to the layout of a village. 

The Gang of Four applied the idea to Object-Oriented Programming. There may be more than one pattern which can be used to solve a problem, but each pattern will have a specific implementation. Patterns exist in other programming approaches, but I am not aware of any applicable books. As others have mentioned Patterns cover specific implementations. Using a pattern when it doesn't apply is often considered an anti-pattern.

Principles don't cover implementation, although there can be standard implementation approaches. Principles are more about covering general issues rather than specific problems. For Inversion of Control, I am aware of at least three implementation approaches. For DRY (Don't Repeat Yourself) I don't know of a singe specific implementation approach, although I use several.

Consider

<ul>
<li>You have been requested to use a Pattern like Abstract Factory Pattern as the only approach to develop a program. Would this be appropriate? No, then it is more likely a Pattern.</li>
<li>You have been requested to apply DRY to all components?
Would this be appropriate? Yes, then it is more likely to be a Principle.</li>
</ul>

blocks|key|5403901|text|OO设计原则-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5403902|OO原则是一组确保OOP概念的准则。基于面向对象的概念，定义了更好的设计方法，更好的设计方法。基本的面向对象设计原则是坚实的。|5403903|设计模式为设计问题提供了一个通用的解决方案。请注意，“设计模式”也可以应用于中午面向对象的单词。因此，面向对象设计模式(OODP)就是为基于面向对象设计原理的面向对象设计提供通用解决方案的设计模式。设计模式是被发现的，而不是发明的。定义OODP的方法有几种，其中最著名的方法是平衡计分卡(+行为结构创造+)。|5403904|下面是详细解释的链接。http://techythought.wordpress.com/2013/01/21/design-principle-vs-ds-design-pattern-describing-oop-elements/|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|http://techythought.wordpress.com/2013/01/21/design-principle-vs-ds-design-pattern-describing-oop-elements/^0|0|0|0|B|2Z|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@$H|U|I|V|1|W]]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

OO Design Principle—

OO principle is a set of guidelines that ensures OOP concept.
Based on the OOP concept, this defines ways to design better way, a better design.
The basic OO design principle is SOLID.

A Design pattern provides a general solution to a design problem.
Please note “design pattern” can be applied to noon object oriented word too. So A OO design patterns (OODPs) are those which provide a general solution to object oriented design based OO principle.
Design patterns are discovered, not invented.
There are several ways to define OODPs and most famous one is BSC [Behavioral Structural Creational].

Following is the link for detailed explanation.
<a href="http://techythought.wordpress.com/2013/01/21/design-principle-vs-ds-design-pattern-describing-oop-elements/" rel="nofollow">http://techythought.wordpress.com/2013/01/21/design-principle-vs-ds-design-pattern-describing-oop-elements/</a>

What is the difference between Object Oriented Design Patterns and Principles? Are they different things? As far as I understood both of them try to achieve some common goal (e,g. flexibility). So can I say a pattern is a principle and vice versa?

Design Principle = SOLID (i.e. Dependency Inversion Principle)

Design Pattern = Gof (i.e. Abstract Factory Pattern)

Difference between Pattern and Principle

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

面向对象的设计模式和原则有什么区别？它们是不同的东西吗？据我所知，他们两人都试图实现一些共同的目标(例如灵活性)。那么，我是否可以说模式是一个原则，反之亦然？设计原则=实体(即依赖反演原则)设计模式= Gof (即抽象工厂模式)

问模式与原则的区别
EN

回答 7

Software Engineering用户

Software Engineering用户

这些概念不一样:

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问模式与原则的区别EN

回答 7

Software Engineering用户

Software Engineering用户

这些概念不一样:

Software Engineering用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问模式与原则的区别
EN