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:
|
"digraph reqdeps {\nrankdir=BT;\nmclimit=10.0;\n" |
|
"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
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
rmtoo/rmtoo/outputs/graph2.py
Line 61 in 5c54b45
from
digraphtostrict digraph.See section
Lexical and Semantic Notesof https://www.graphviz.org/doc/info/lang.html