Try doing an image search in Google for "flowchart". The first 18 images have diamond shaped decision boxes, like an ISO flowchart. In fact, as I scroll, nearly all of the images look like ISO flowcharts.
Searches which yield graphs more like what you're doing are "concept maps", "block diagrams", "org charts", or "tree diagram". However, your tool allows zero or more parents and zero or more children, whereas many of these don't allow all those choices or allow more than that.
Flowcharts need at least diamonds and circles in addition to rectangles. They also allow arbitrary connections, not just parent, and children. I'm not a topology person, but from some digging around, it seems like the connections that you're allowing are typical of a "directed acyclic graph".
Comments
I've found it to be the most accurate description. I think the core of what makes a flowchart is that its a directed graph, which knotend is.
Try doing an image search in Google for "flowchart". The first 18 images have diamond shaped decision boxes, like an ISO flowchart. In fact, as I scroll, nearly all of the images look like ISO flowcharts.
Searches which yield graphs more like what you're doing are "concept maps", "block diagrams", "org charts", or "tree diagram". However, your tool allows zero or more parents and zero or more children, whereas many of these don't allow all those choices or allow more than that.
Flowcharts need at least diamonds and circles in addition to rectangles. They also allow arbitrary connections, not just parent, and children. I'm not a topology person, but from some digging around, it seems like the connections that you're allowing are typical of a "directed acyclic graph".
Similar to other comments, I think that a useful "flowchart" needs decision points.
It also needs loops, else it's just a simple tree, precluding a lot of use-cases for flow charts.