Geek Answers Handbook

General use of UML

In my experience, most of the architectural documentation was ad-hoc at best, and, in addition to the more structured types of dead trees, I still have not seen official UML in actual use, and I worked with several, if any developers who could clearly or to build UML diagrams correctly, this is apparently more used as a kind of "graphic psuedocode".

Given this, I'm curious if anyone has experience using UML in internal documentation and linking system functions between team members. Is this a tool / way of communication that people actually use in everyday life? Is it helpful, too much? Have you worked in environments where accurate UML mattered or was useful?

+5
source share
6 answers

At my workplace, we made extensive use of UML class diagrams when we write large enterprise-scale web applications. In some cases, we use sequence diagrams. But we in no way use the full set of UML diagrams or even get close. UML can only be effective by chewing meat and spitting out bones. It's a great communication tool, but using too many of its features can confuse people.

+1
source

UML (Unified Modeling Language) is flexible. No need to constantly use the "full" UML.

Yes, I used UML to link design. I used the Domain, Class, Activity, Use Case, Sequence, and Deployment charts for various purposes.

"" . , . Node UML, . , , . , Windows Server 2008, SQL Server, .

+3

UML . , Enterprise Architect XML . JAXB Java, , UML.

+1

, UML , .

, , , , . , , , UML.

0

, UML , . , (.. ) n-to-n. ER:)

alt text

0

More articles:


All Articles