|
|
|
|
|
|
by GianFabien
598 days ago
|
|
|
Perhaps more of wishful-thinking than prediction ... Tooling that works top-down. Starting with UML and similar system of systems diagrams and requirements specs with semi-automated generation of working systems that can be fine-tuned as it runs. We started down that path with Smalltalk, but as David Ungar remarked (from memory), "once you get past the system browser, it's like editing Pascal source code". The limiting factor was not the vision, but the meagre (compared to present day) hardware resources available for tooling. Some UML tooling has been written on Smalltalk systems, but Smalltalk run-times were never suitable for deployment of systems. And then Java happened. |
|
|
Have you tried asking using LLM's to generate your UMl? :-) Or to explain what kind of system a UML diagram is modeling?
Depending upon how fast they move, in 10 or 15 years software development may be unrecognizable and radically different. We might not even need UML (if we ever did).