Closed DanielFroehlich closed 5 years ago
Suggest to look at http://plantuml.com/ which allows generating uml diagrams from easily diffable/writable Text docs.
For any planning I would stick to GitHub projects until the limitations become too apparent - that way information is located at a single point
Regarding plantUML: I do like the approach in general, and support into vscode or atom. Downside: code generation seems to be a problem. Not sure how much much code we could generate. Maybe some SQL/JSON/Swagger/Java Interfaces. Probably depends on wether we go more Model Driven or more Test Driven.
@ortwinschneider , would love to hear your thoughts on Modelling tool!
Ah, i’m a firm nonbeliever in model driven + code gen due to my BPMN history. I haven’t seen roundtripping work, and actually modeling behavior and details was equally complex as simply coding it (with some exaggeration). Therefore in my mind I’ve limited model-driven + code gen to isolated aspects such as stub/skeleton generation from API defs, etc.
I do have some good experience with just forward only generation, e.g. in SQL / Java Data TransferObjects area. But I am inclided to say that we dont need that here as often. And JSON Data Modelling can be simply done with prototypes, i.e. a bunch of JSON files giving examples. So just for the better team working experience, merging etc. I am trending to go with plantUML, but lets see what others are going to add to the discussion.
Switched topic from "Decide on Tooling" to "Decide on UML Tooling" tooling, need to create new issue for each tool we need.
There are tools/projects to generate PlantUML from Swagger or GRPC. For me, thats the final argument to decide PRO plantUML. So: PlantUML it is!
We need to decide on Project Tooling used for: