Duplicate edges in graphviz output.

[ibtaylor]

If topics are named a certain way, or are nested, it seems to cause multiple arrows between requirements.

A possible solution to this (though maybe not the most appropriate), is to tell graphviz not to allow multiple edges by changing the lines:

rmtoo/rmtoo/outputs/graph.py

Line 55 in 5c54b45

"digraph reqdeps {\nrankdir=BT;\nmclimit=10.0;\n"

rmtoo/rmtoo/outputs/graph2.py

Line 61 in 5c54b45

"digraph reqdeps {\nrankdir=BT;\nmclimit=10.0;\n"

from digraph to strict digraph.

See section Lexical and Semantic Notes of https://www.graphviz.org/doc/info/lang.html

[ibtaylor]

Example

I'll try to demonstate with slightly modified version of the template_project with the following topics and requirements:

Topics:

• ropics/NestedTopic.tic

Name: Nested Topic - this should be inside Topic
IncludeRequirements: full

• topics/Topic.tic

Name: Topic Requirement - this should contain NestedTopic
IncludeRequirements: full
SubTopic: NestedTopic

• topics/ReqsDocument.tic

Name: project
Text: This is placeholder for some introductional text.
IncludeRequirements: full
SubTopic: Topic

Requirements

• requirements/project.req

Name: project
Type: master requirement
Invented on: 2010-10-09
Invented by: flonatel
Owner: development
Description: \textsl{project} \textbf{must} exists.
Rationale: The world needs a good, usable and free \textsl{project}.
Status: not done
Solved by: TopicRequirement
Topic: ReqsDocument

• requirements/TopicRequirement.req

Name: Topic Requirement
Type: requirement
Invented on: 2010-10-09
Invented by: flonatel
Owner: development
Description: This \textbf{must} hold the description.
Rationale: This is a dependent requirement.
Status: not done
Topic: Topic
Solved by: NestedTopicRequirement

• requirements/NestedTopicRequirement.req

Name: Nested Topic Requirement
Type: requirement
Invented on: 2010-10-09
Invented by: flonatel
Owner: development
Description: This \textbf{must} hold the description.
Rationale: This is a dependent requirement.
Status: not done
Topic: NestedTopic

Unexpected graph results

• TopicRequirement to be inside of Topic not NestedTopic.
• TopicRequirement to have a single edge to project.

artifacts/req-graph2.dot

digraph reqdeps {
rankdir=BT;
mclimit=10.0;
nslimit=10.0;ranksep=1;
subgraph cluster_GRAPH_ReqsDocument {
 label="Topic: ReqsDocument";
 "project" [fontcolor=red,label="project\n[0.00]"];
 subgraph cluster_GRAPH_Topic {
  label="Topic: Topic";
  "TopicRequirement" [fontcolor=red,label="TopicRequirement\n[0.00]"];
  subgraph cluster_GRAPH_NestedTopic {
   label="Topic: NestedTopic";
   "NestedTopicRequirement" [fontcolor=red,label="NestedTopicRequirement\n[0.00]"];
   "TopicRequirement" [fontcolor=red,label="TopicRequirement\n[0.00]"];
   }
  }
 }
"TopicRequirement" -> "project";
"NestedTopicRequirement" -> "TopicRequirement";
"TopicRequirement" -> "project";
}

Please let me know if this is somehow the intended behavior.