blocks|key|2571881|text|类区分行为集。因此，让我们看看你们在这些方面的划分：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2571882|2571883|虽然可以认为折扣/非折扣是行为的一种变化，但将其简化为单一行为是微不足道的:所有产品都有折扣，但非折扣产品的折扣金额恰好是0%25。这只是您的产品(discount_amount)的一个属性，而不是一个单独的class.|unordered-list-item|2571884|Local/exportable可能有也可能没有不同的行为。如果唯一的区别是产品是否允许在国际上运输，那么一个简单的布尔标志应该足以处理这种区别。另一方面，如果可导出产品需要本地产品不支持的行为(例如，记录客户要求和程序)，则适当的做法是使ExportableProduct成为LocalProduct的子类(如果可导出产品行为是本地产品行为的超集)，或者使抽象产品类具有LocalProduct和ExportableProduct子类(如果本地产品也具有可导出产品不支持的行为)。|2571885|2571886|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

Classes distinguish sets of behavior. So let's take a look at your divisions in those terms:

<ul>
<li>While an argument could be made that discounted/non-discounted is a variation in behavior, it's trivial to reduce this to a single behavior: All products have a discount, but the amount of the discount happens to be 0% on non-discounted products. This is just an attribute of your products (discount_amount), not a separate class.</li>
<li>Local/exportable may or may not have distinct behaviors. If the only difference is whether the product is allowed to be shipped internationally or not, then a simple boolean flag should handle this distinction more than adequately. If, on the other hand, exportable products require behaviors not supported by local products (e.g., recording of customs requirements and procedures), then it would be appropriate to either make ExportableProduct a subclass of LocalProduct (if exportable product behaviors are a superset of local product behaviors) or make an abstract Product class with LocalProduct and ExportableProduct subclasses (if local products also have behaviors which are not supported by exportable products).</li>
</ul>

blocks|key|99793|text|为了简单起见，问问你自己，折扣是否真的需要是一个子类型，或者它是否可以是产品的一个属性，其中"NonDiscounted“的折扣为零。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|99794|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|$]]

To keeps things simple, ask yourself if discount really need to be a subtype, or if it could be a property of the product, where "NonDiscounted" have a discount of zero percent.

blocks|key|1161728|text|我会这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1161729|有一个名为"+product“的类，它具有产品的基本属性，如名称、描述、类型等。|1161730|基类"Product“可以有一个名为"DiscountRate”的属性。对于非折扣，它可以是0；对于折扣，它可以是任何值。这将有助于简化计算，因为将始终应用相同的公式，只是在一种情况下折扣为0。|1161731|然后你可以有两个类"ExportableProduct“和"LocalProduct"，它们都继承自”产品“类。|1161732|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I would do this:

Have an class called "Product" that has the basic properties of a product like name, description, type, etc.

The base "Product" class can have a property called "DiscountRate". It can be 0 for non discounted and whatever value for discounted. This will help simplify calculation since the same formula will always be applied, just in one case the discount is 0.

Then you can have two classes "ExportableProduct" and "LocalProduct", they both inherit from the "Product" class.

blocks|key|99800|text|我建议也许折扣/非折扣根本不应该是产品的类型。相反，在父产品中有两个子类型和一个'discount‘属性/字段。然后，每种产品都可以有效地享受任何折扣。这也允许不固定在10%25的折扣。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|99801|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|$]]

I would suggest that perhaps Discounted/NonDiscounted should not be types of products at all. Instead have two subtypes, and a 'discount' property/field in the parent Product. Each product can then effectively have any discount. This also allows for discount that aren't fixed at 10%.

blocks|key|2571750|text|我会避免继承(也就是子类型)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2571751|相反，我会为Discounted+/+NonDiscounted和Local+/+ExportableProduct定义枚举。然后，每个产品类将简单地为每个产品类提供一个属性，以指示其类型。|2571752|然后在一个单独的类中，例如:+PricingCalculator，定义一个接受产品实例的Calculate方法(可能是静态的)。此方法只检查枚举属性，并在计算中应用所需的百分比值。|2571753|这将定价的计算与产品本身完全分开，并允许您将有时复杂的定价计算保存在一个位置。当您的定价方案随着时间的推移而变化时，这种方法很容易维护和测试。|2571754|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I'd avoid inheritance (ie sub typing) just for this. 

Instead I'd define enumerations for Discounted / NonDiscounted and Local / ExportableProduct. Each product class would then simply have a property for each of these indicating its type.

Then in a separate class, eg: PricingCalculator, define a Calculate method (possibly static) that accepts an instance of a product. This method simply examines the enumeration properties and applies the required percentage values in the calculation. 

This completely separates the calculation of pricing from the products themselves and allows you to keep sometimes complex pricing calculations in one location. As your pricing schemes change over time, this approach is easily maintainable and testable.

blocks|key|847940|text|我会避免任何事情，只有两个属性：discount和local|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|847941|因为只有一样东西会改变(价格)，你可以即时计算它(discount+=>+price+*+.9，export+=>+price+*+.85+--甚至同时使用=>+export和discount+=>+price+*+.9+*+.85)|847942|entityMap^0|G|8|P|5|0|11|A|1M|B|2S|G|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|I|$]]

I would avoid everything and just have two properties: <code>discount</code> and <code>local</code>

Since there is only one thing that changes (price), you can calculate it on the fly (discount => <code>price * .9</code>, export => <code>price * .85</code> - or even both => export &amp; discount => <code>price * .9 * .85</code>)

blocks|key|2571810|text|当比thing更多的东西根据类型变化时，继承特别有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2571811|例如，如果折扣、税收和送货方式都根据物品的类型而不同，那么肯定是时候考虑继承和子类化了(你可以说“这个子类型的物品有这个税、这个折扣和这个送货”)。|2571812|另一方面，当只有一件事根据类型而变化时，那么不太明显的是，是否值得拥有几个类型(即具有子类的基类型)，或者是否可以将这种差异更简单地建模为单个类型，其实例具有属性值(例如，命名为"discount_percentage")。|2571813|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Inheritance is especially useful when more than thing varies according to the type.

For example if the discount, and the tax, and the shipping method all varied depending on the type of item, then it's definitely time to consider inheritance and subclassing (where you'd say "this subtype of item has this tax and this discount and this shipping").

On the other hand when only one thing varies according to the type, then it's less obvious whether it's worth having several types (i.e. a base type with subclasses), or instead whether that variance can be modeled more simply as a single type, whose instances have a property value (e.g. named "discount_percentage").

blocks|key|2571925|text|当这是all你需要的行为时，在你的产品中有两个布尔值并打开它们就是最好的解决方案。YAGNI。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2571926|但我担心这只是一个更大问题的一小部分。然后你必须问自己:是什么让一个产品成为一个产品(单一责任)。可税性和可折扣性可能是两个不同的问题，所以你的产品最终有两种策略。|2571927|entityMap^0|3|3|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

When this is all the behaviour you are going to need, just having two booleans in your product and switching on them is the best solution. YAGNI. 

But I'm afraid it's just a small part of a larger problem. And then you have to ask yourself: what makes a product a product (single responsibility). Taxability and discountability are probably two different concerns, so your product ends up with two strategies.

I have a two types of products - Discounted (10% Disc) and NonDiscounted (0%) Each of these can be either LocalProduct / ExportableProduct with export one attracting a 15% sales tax.

What is the best way to model this scenario. 
Me being absolute newbie to S/W design, I have very limited ideas
1. To have 4 different Product sub types 
2. Use Strategy pattern and have 4 different strategies.

Can some one please suggest how can I model this effectively using the above options or other ones.

OO Design question

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我有两种类型的产品-折扣(10%折扣)和NonDiscounted (0%)，每一种都可以是LocalProduct / ExportableProduct，出口一种要缴纳15%的销售税。对此场景进行建模的最佳方式是什么？我是软件设计的新手，我的想法非常有限1.有4种不同的产品子类型2.使用策略模式和4种不同的策略。有人能建议我如何使用上述选项或其他选项有效地建模吗？

问OO设计问题
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OO设计问题EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问OO设计问题
EN