Skip to main content Skip to footer

UML too complex ?

Does the UML standard seem complex to you? Due to the wide variety of artifacts, what implementation strategy should be applied? The standard does not address this subject, which seems to confine UML to simple documentation? Ultimately, what value can you get from UML? Is any value envisaged? And if so, how can this be formalized?

At Acceliance, we "rewound" or "rebooted" UML in a Bottom-Up vision then we validated the strategy by driving Data Platforms in a Top-Down vision.

As part of our Modelio partnership, we have reduced the range of UML artifacts:

  • Business Objects

  • Attributes

  • Association relationships and cardinalities

  • Specialization relationships (or inheritance according to geeks)

Each of these UML artifacts participates in an automatic and industrial value chain in the following application areas:

  • Datavault Modeling

  • Apis

  • Structured SQL

About the author

Page LinkedIn

José has been a Data expert and more particularly Modeling for around ten years. Previously, he was a software architect, API, SOAP and even Calculation Grid. He is passionate about building an industrialized value chain around the Enterprise Data Model.

Translation in English under works