News for hackers. Stuff that matters.
Re:UML diagram for the DDD example in Evans' book by riffraff on Friday April 18, 2025 @04:46PM (#43731725)
UML as a methodology seems to have disappeared, but bits of it (e.g. sequence diagrams) seem to have been absorbed by the profession at large.
Re:UML diagram for the DDD example in Evans' book by SanjayMehta on Friday April 18, 2025 @08:49PM (#43733252)
Sequence diagrams existed prior to UML. They were extensively used in telecom: “message sequence charts.”

They were part of a telecom language called SDL. There were tools to “compile” to various languages such as C. If you followed their rules, you were supposed to be able to go back and forth between C and SDL.

I only remember this because the biggest tool provider at that time was a French company called Verilog. They preceded the HDL by a few years, I guess.

Re:UML diagram for the DDD example in Evans' book by leoc on Friday April 18, 2025 @10:42PM (#43733784)
IIRC sequence diagrams were invented by one of Carl Hewitt’s PhD students during Hewitt’s earlyish work on the Actor model?
Re:UML diagram for the DDD example in Evans' book by SanjayMehta on Saturday April 19, 2025 @01:23AM (#43734400)
Gul Agha?
Re:UML diagram for the DDD example in Evans' book by SuiGenerous on Wednesday April 23, 2025 @09:09AM (#43771733)
Ra's al Ghul.
Re:UML diagram for the DDD example in Evans' book by leoc on Wednesday April 23, 2025 @02:30PM (#43775208)
Maybe! Or maybe Henry Baker ...?
Re:UML diagram for the DDD example in Evans' book by dilyevsky on Saturday April 19, 2025 @12:22AM (#43734189)
I used to work for Motorola's telecom division and we used IBM Rational Suite to generate C++ classes from the SDL. Merges (and we used very long-lived release branches) were pure hell...
Re:UML diagram for the DDD example in Evans' book by billfruit on Saturday April 19, 2025 @04:22AM (#43735025)
I think the UML statecharts are a much more useful diagrams than sequence diagrams. It can convey a lot more of the behaviour especially if you use the entire 'Harel' formalisms.

Too bad, they aren't that popular to document behaviour, because sequence diagrams really don't convey that much.

For example timeouts are very neatly described in a harel state chart. How will one describe timeout and timeout handling in sequence diagrams.