1
General Board / Re: Make EA<->C Code synchronization more "intelligent"?
« on: May 25, 2022, 03:33:07 pm »So what I learned: there's a media break between UML (which is excellent to model customer views up to a technical design) and IDEs (which support coding in all directions like code intellisense, debugging, etc.). Give the modelers/architects a good UML tool and gibe the coders a good IDE. And the real issue to get the technical part (SDs upward) being documented by coders EASILY. EA is not the best for the latter, unfortunately.
I agree that UML (EA, respectively) is too often not the best way for the detailed design part, i.e. to describe how the code shall actually work.
But somehow I have to ensure "traceability" between high level requirement, architecture, design and eventually the code.
Of course, "code reviews" are one way to catch the "media break" you mentioned, and they are inevitable anyway wherever manual coding is done.
Yet I'm still not convinced that - at least for the interfaces part - code generation brings no benefit in this point (and it seems that with EA there doesn't have to be tags or other fancy stuff).
Yes, this is just a small part and can be easily done during code review, but whatever can be automated eliminates human error (unless the automation process is errorneous :-D ) .
Anyway, I appreciate your and Geert's comments and will rethink my idea :-)
BR,
EAabecedarian



