SoylentNews is people
SoylentNews
from the how-did-they-model-the-removal? dept.
Microsoft has decided to drop the UML (Unified Modeling Language) designer tools from Visual Studio 15, reports Paul Krill at IT World. MS sales and support teams confirmed that few customers were actually using the feature.
"Removing a feature is always a hard decision, but we want to ensure that our resources are invested in features that deliver the most customer value," said Microsoft's Jean-Marc Prieur, senior program manager for Visual Studio.
I've almost never had occasion to use UML professionally other than a few hand drawn designs on scrap paper that were thrown away. I did have a coworker who had a tool that generated UML from code that was sometimes helpful when he explained his work in review sessions. In school UML appeared to be a nightmare that was used for modelling everything but software, yet academics talked about UML one day becoming executable and replacing code.
Do you use UML? Are you going to miss this feature in Visual Studio?
(Score: 2) by DannyB on Friday October 21 2016, @01:51PM
Nothing new under the sun.
Back in the day, late 70's, early 80's, "flow charts" were all the rage.
And like UML, they were abused.
Even for the most trivial algorithm "where is your flow chart?" The flow chart was no more than a chart representation of the program. So what was the point? None, really.
After school, out in the real world, I was finally exposed to some useful flow charts on larger software systems that had many software components. Then I had the "ah ha" that flow charts could be useful to describe a larger system of component programs and their inter operation. Almost like you might describe some "big data" setups today.
Then I realized how completely wrong was the approach to how "flow charts" were being universally taught.
The lower I set my standards the more accomplishments I have.