复杂决策树的表设计 [英] Table design for complex decision tree

问题描述

我需要帮助弄清楚如何为复杂的决策树设计表结构。这很复杂，因为有些问题需要两个（或更多）选择才能使答案成立。决策树的结果是法院报告中措辞的变化。我的想法是在组合框中选择犯罪。犯罪将有一些已经输入的文本。然后，决策树会将具体内容放入最终的措辞中。这是一个例子。印第安纳州代码IC 35-45-1-3 Disorderly Conduct 印第安纳州代码IC 35-45-1-3 Disorderly Conduct

I need help figuring out how to design the table structure for a complex decision tree. It is complex because some questions require two (or more) selections to make the answer true. The result of the decision tree is a change of wording in a court report. My idea is that a crime would be selected in a combo box. The crime would have some text already typed in. The decision tree would then just put the specifics into the final wording. Here is an example. Indiana code IC 35-45-1-3 Disorderly Conduct Indiana code IC 35-45-1-3 Disorderly Conduct

展开 | 选择 | Wrap | 行号

推荐答案

如果有任何安慰，我会承认对表设计没有好的想法来满足你的要求，并认为这是一个可以理解的复杂任务。也就是说，我发现挑战很有吸引力，并会尝试思考它，打开和关闭，看看是否有任何弹出。


祝你的项目好运。

If it is any consolation at all, I will admit to having no good ideas for a table design to accommodate your requirements, and consider it a understandably complex task. That said, I find the challenge fascinating, and will try to think about it, on and off and see if anything pops up.

Best of luck with your project.

我很高兴你没有说哦，那很简单。至少有一位专家需要考虑:)。希望你或其他专家最终能想出一个。这并不是我以前做过的任何事情。

I''m glad you didn''t say "oh, that is simple". At least there is one expert that has to think about it :). Hopefully you or another expert can come up with one eventually though. This just isn''t remotely near anything that I have done before.

没有任何冒犯意图：这就是为什么首先设计流程图的原因。

>>在您获得基本流程图之前，我不会尝试任何桌面设计！在大多数情况下，这样做会导致大脑融化。融化的大脑难以从大多数织物上移除，并且不可能从键盘和大多数木材表面上移除。<<


我更喜欢NS系统，即使它们更适合编程一般决策工作： 56 Nassi-Shneiderman排行榜然后就是这样： A结构化流程图的简史（Nassi-Shneiderman Diagrams）


这里有一些好东西：只有几个基本符号可以掌握，并且在每个动作块中， sub-blocks，您可以简单地将引用放在另一个决策树上，然后将其解决，或者列出指令等等。


代码很容易在结构中写入存在某种程度的对象方法中固有的级别代码。但是，请记住，当我学习这种方法时，对象级代码刚刚进入舞台。


您可以使用旧的流程图方法，可能还有新的方法也好。


祝你好运

Without any intent to offend: this is why flow charts were designed in the first place.

>> I wouldn''t attempt any table design until you can get the basic flow chart made! Doing so results, in most cases, brain melt. Melted brain is hard to remove from most fabrics and impossible to remove from the keyboard and most wood surfaces.<<

I prefer the NS system, even though they are more for programing than general decision work: 56 Nassi-Shneiderman charts and then there''s this: A short history of structured flowcharts (Nassi-Shneiderman Diagrams)

There are IMHO a few nice things here: only a few basic symbols to master, and at each action block, "sub-blocks", you can simply place a reference to another decision tree and then work that out, or list instructions and so forth.

Code is easily written within the structure and there is some level of "object" level code inherent in the method. However, keep in mind that object level code was just coming onto the stage when I learned this method.

You can ofcourse use the older flow-chart methods and there maybe new methods out there too.

Best of luck

这篇关于复杂决策树的表设计的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！