3 ms·
> There’s something wrong about the fact that software engineering isn’t actually engineering. Well, the point is that UML isn't engineering, either. The visu
by zozbot234 6y ago
> There’s something wrong about the fact that software engineering isn’t actually engineering.
Well, the point is that UML isn't engineering, either. The visual syntaxes are overly baroque, and in many cases add little or nothing over just stating the exact same information in plain text (though there are of course exceptions, where "tracing" linkages visually, looking at containment etc. can actually help when surveying a design).
And the whole OOAD/RUP methodology of "just list plausible 'objects' from the overall problem domain and reflect them directly in the design and implementation" does not exactly help, either. It mistakes what "objects" in the OOP sense are supposed to be used for.
- dmitryminkovsky 6y agoYeah I agree with you. Clearly something was wrong with UML. I didn't mean something was lost with the abandonment of UML in particular. Just that nothing has come up to replace it and people just write the same code over and over again, poorly. And that there is no real "software engineering" discipline in the same way that civil engineering or electrical engineering exist. I guess it's still just too early in the history of software to really break it down into a discipline.
- jhgb 6y ago> and in many cases add little or nothing over just stating the exact same information in plain text That's presumably why there's a data model for UML, so that this "plain text" could be mapped into graphical objects and back again.