Re:Devs need system design tools, not diagramming tools
by halfcat on Tuesday July 16, 2024 @06:50PM
(#40981057)
I came to the same conclusion, and the closest thing I’ve found is using a graph database.
Re:Devs need system design tools, not diagramming tools
by XorNot on Tuesday July 16, 2024 @08:31PM
(#40981579)
I've had the same thought but then gave up because it's not even a single graph: we assume it's a single graph because some parts of "concept - connection - concept" tuples...but that fails to capture the reality that the aggregate behavior of a system can implement a wholly different behavior.
A practical example of this would be neural networks in AI: which collectively implement functions much greater then the individual links.
Re:Devs need system design tools, not diagramming tools
by 9dev on Wednesday July 17, 2024 @02:04AM
(#40983021)
You can always build a subgraph and find a connection to bring that into the main graph. If it’s part of a system, it’s part of the graph.
Re:Devs need system design tools, not diagramming tools
by gdegani on Wednesday July 17, 2024 @03:07AM
(#40983290)
I have the same conclusion, if you capture the model as a graph you can then derive from the graph as many visual representations as you need, for instance, this tool can generate archimate context diagrams from the graph data ( mostly by doing "ontology translation" )
https://github.com/zazuko/blueprint
It’s very complex, very interesting, and lots of work.