决策表的替代方案
我们的应用程序正在快速增长。因此，我开始研究业务规则，将其作为将部分逻辑与代码分离的方法（大 DAAAH；）。主要目标是允许我们的业务人员编辑和部署规则，而无需重新编译任何内容（另一个大 DAAAH）。到目前为止，我只能找到“决策表”作为企业管理规则的一种方式的参考。问题是，我试图将决策表的概念引入我们的业务，但至少可以说，得到了非常“混合”的回应:) 简而言之，他们不想理解它们。问题：决策表有替代方案吗？对于销售人员来说更容易理解的东西是什么？
Our app is growing rapidly. So, I begun looking into business rules as a way to separate some of our logic from the code (big DAAAH ;). The main goal is to allow our business guys to edit and deploy rules without recompiling anything (another big DAAAH). So far, I could only find references to "decision tables" as a way for business to manage rules. The thing is that I tried to introduce the concept of decision tables to our business and got a very "mixed" response, to say the least :) In short, they don't want to understand them. Question: is there an alternative to decision tables? Something that is easier to understand for sales people?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我认为决策表只有一种替代方案 - 决策树。我认为有些人也称它们为“流程图”。我知道一些商业工具将 UI 显示为树，让用户通过拖放“构建”规则。但在内部，当您将规则保存为文件时，它们会将这些树转换为决策表或类似结构的对象。
I think there is only one alternative to decision tables - decision trees. Some guys also call them "flow charts", I think. I know several commercial tools that present UI as trees to let users "build" rules with drag-n-drop. Internally though, they convert those trees into decision tables or similarly structured objects when you save rules as files.
通常，像您在问题中提出的规则一样的规则会聚集在一起，例如
可以轻松地将这个逻辑放入只有 2 个标头 Price 和 Action 的决策表中。大多数现代规则引擎都支持这种决策表。经验表明，业务用户理解此类表没有问题
Usually the rules like the one that you presented in your question go in clusters, such as
There is easily to put this logic in a decision table with just 2 headers Price and Action. Most of the modern rule engines have support for this kind of decision tables. The experience shows that business users have no problems to understand such tables