Nearly six months after the release, the jury seems to still be out as to how, or even if, UML 2.5 is doing what it’s intended to. The goal of the update wasn’t to change the language, but to simplify documentation and make life easier for developers.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Ed Seidewitz, chief technology officer for the Americas, said many people outside of the Object Management Group (OMG, which adopted UML in the 1990s) are just starting to dapple with the latest UML version. “UML 2.4 is still the most prominent out there,” he said, noting that feedback has been positive from those who have begun working with UML 2.5.
What users see and use UML for didn’t change for the most part, notes Cory Casanave, CEO of Model Driven Solutions, but it “really puts a maturity level into UML.”
A big gripe with UML among developers was that tools failed to work well with one another and models didn’t transfer well. One of the main goals of UML was to improve interoperability between tools and models. “It’s too early to know if that will have a significant effect in practice because most vendors have not implemented UML 2.5 yet,” said Steve Cook, Architect at Microsoft.
That being said, from what Casanave has seen so far, “UML 2.5 has largely made that problem a thing of the past.”
Have you started working with UML 2.5? What do you think of the revision?