这是我在这里的第一篇文章,我不确定它是否属于正确的子类别。
假设我们在某些数据结构中定义了以下工作流程:
使用以下信息绘制有向图的最佳方法是什么:
我使用此信息生成的代码给出了下图:
我在这里想念什么?
Edit1:添加源代码
digraph flow_view {
rankdir = TB;
graph[fontsize="22"];
node [shape="box", fontsize="11.0", style="filled", fillcolor="peachpuff", fontcolor="black"];
"Case created" [fillcolor="seagreen1"];
"Case created" -> "Case assigned" ;
"Case assigned" -> "Case review and initial analysis" ;
"Case review and initial analysis" -> "Further action required?" ;
"Close case" [fillcolor="lightpink"];
"Further action required?" -> "Close case"[label="No", fontsize="8.5"]
"Further action required?" [shape="diamond", fillcolor="peachpuff"] ;
"Further action required?" -> "Further work"[label="Yes", fontsize="8.5"]
"Further action required?" [shape="diamond", fillcolor="peachpuff"] ;
"Close case" [fillcolor="lightpink"];
"Satisfactory explanations?" -> "Close case"[label="Yes", fontsize="8.5"]
"Satisfactory explanations?" [shape="diamond", fillcolor="peachpuff"] ;
"Case escalated / reassigned" -> "Further action required?" ;
"Satisfactory explanations?" -> "Case escalated / reassigned"[label="No", fontsize="8.5"]
"Satisfactory explanations?" [shape="diamond", fillcolor="peachpuff"] ;
"Further work" -> "Satisfactory explanations?" ;
}
我设法调整它以匹配您的示例图像,不确定它的可伸缩性。大概我做了以下事情:
fontsize
定义添加为全局边缘属性,而不是每个连接portPos
)。这指示边缘应连接到节点的哪一侧(n正交,e ast,s outh,w est)。portPos
。这表明订购节点时不应考虑该连接。"Further work":s
constraint=false
以缩短/拉直某些边缘constraint=false