blocks|key|2017935|text|在我的工作场所，我们在编写大型企业级web应用程序时广泛使用UML类图。在某些情况下，我们使用序列图。但是，我们绝不会使用完整的UML图套件，甚至不会接近。UML只有通过嚼碎肉和吐出骨头才能有效。它是一个很棒的交流工具，但是过多的使用它的功能会让人感到困惑。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2017936|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my workplace, we have used UML class diagrams extensively as we write large enterprise-scale web applications. On some occasions we use sequence diagrams. But, by no means do we use the full UML suite of diagrams or even come close. UML can only be effective by chewing the meat and spitting out the bones. It is a great communication tool, but using too much of its functionality can confuse people.

blocks|key|717789|text|UML+(统一建模语言)是灵活的。没有必要一直使用“完整的”UML。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|717790|是的，我曾经使用UML来传达设计。我已经将域、类、活动、用例、序列和部署图用于各种目的。|717791|其中一些目的超出了图表的“明显”用途。例如，我使用部署图来记录多组虚拟机。因为Node元素是一个UML“分类器”，所以它可以与继承一起使用。我用它来展示基础虚拟机是如何专门化的。例如，基础只是Windows+server+2008，但它的一个专用版安装了SQL+Server，并且该专用版被用作数据库服务器。|717792|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The UML (The Unified Modeling Language) is flexible. It's not necessary to use "full" UML all the time.

Yes, I've used UML to communicate design. I've used Domain, Class, Activity, Use Case, Sequence and Deployment diagrams for various purposes.

Some of these purposes were beyond the "obvious" use of the diagram. For instance, I've used deployment diagrams to document sets of virtual machines. Since the Node element is a UML "classifier", it can be used with inheritance. I've used this to show how a base virtual machine is specialized. For instance, the base is just Windows Server 2008, but a specialization of that has SQL Server installed, and a specialization of that one is being used as the database server.

blocks|key|717144|text|我见过使用UML类图自动生成代码。流程是这样的，Enterprise+Architect被用来从类图中生成一个XML+schema。该模式随后被用作JAXB的输入，以生成Java类，这些类提供对UML模型中表示的数据的编程访问。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|717145|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sparxsystems.com.au/|1|http://jaxb.java.net/^0|O|K|0|22|4|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

I have seen usage of UML Class diagrams for automatic code generation. The flow was something like this, <a href="http://www.sparxsystems.com.au/" rel="nofollow noreferrer">Enterprise Architect</a> was used to generate an XML schema out of the class diagram. This schema was then used as an input for <a href="http://jaxb.java.net" rel="nofollow noreferrer">JAXB</a> to generate generate Java classes which provide programmatic access to the data represented in the UML model.

blocks|key|2018041|text|UML图对于捕获和传达需求并确保系统满足这些需求非常有用。它们可以在规划、设计、开发和测试的不同阶段迭代使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2018042|来自主题:在http://msdn.microsoft.com/en-us/library/dd409423%2528VS.100%2529.aspx的开发过程中使用模型的|offset|length|2018043|2018044|模型可以帮助您可视化系统的工作环境，明确用户的需求，定义系统的体系结构，分析代码，并确保代码满足要求。|blockquote|style|BOLD|2018045|2018046|2018047|如果您不想从头开始创建UML关系图，则可以从代码创建序列关系图、依赖关系图和层关系图，并使用层验证来确保代码中的更改不会与指定的设计冲突。我在下面的帖子中对此进行了更详细的描述：|2018048|如何学习“良好的软件设计/体系结构”？https://stackoverflow.com/questions/268231/how-to-learn-good-software-design-architecture/2293489#2293489上的|2018049|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/dd409423%2528VS.100%2529.aspx|1|https://stackoverflow.com/questions/268231/how-to-learn-good-software-design-architecture/2293489#2293489^0|0|6|1T|0|0|0|0|1F|0|0|0|0|2H|0|0|3I|J|2X|1|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@]|9|@$D|13|E|14|1|15]]|A|$]]|$1|F|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|17|8|@$D|18|E|19|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@$D|1D|E|1E|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@$D|1G|E|1H|J|K]]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|R|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]|Z|$5|U|V|W|A|$X|10]]]]

UML diagrams are useful for capturing and communicating requirements and ensuring that the system meets those requirements. They can be used iteratively and during various stages of planning, design, development, and testing.

From the topic: Using Models within the Development Process at <a href="http://msdn.microsoft.com/en-us/library/dd409423%28VS.100%29.aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/dd409423%28VS.100%29.aspx</a> 

<blockquote>
 A model can help you visualize the world in which your system works, clarify users' needs, define the
 architecture of your system, analyze the code, and ensure that your code meets the requirements.
</blockquote>

If you do not want to create UML diagrams from scratch, you can create sequence diagrams, dependency graphs, and layer diagrams from code, and use layer validation to ensure that changes in the code do not conflict with the specified design. I describe this with more detail in the following post: 

How to learn “good software design/architecture”? at <a href="https://stackoverflow.com/questions/268231/how-to-learn-good-software-design-architecture/2293489#2293489">https://stackoverflow.com/questions/268231/how-to-learn-good-software-design-architecture/2293489#2293489</a>

blocks|key|2311280|text|根据我的经验，我发现UML序列图对于试图理解系统或系统的特定过程的人来说是最有用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2311281|最有可能的原因是，它显示了各种组件如何协作，并间接地显示了每个组件的责任。垂直维度显示时间，图表非常直观地理解，即使对于没有UML知识的人也是如此。|2311282|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

In my experience I've found the UML Sequence diagrams to be the most useful for people trying to understand a system or a particular process of the system.

The reason most likely is that it shows how various components co-operate and indirectly what the responsibility of each of them have. The vertical dimension shows time and the diagram is very intuitive to understand, even for people with no knowledge of UML.

blocks|key|902970|text|我发现UML类图比实体-关系图更有助于建立逻辑数据模型或域模型。它更具表现力，具有泛化(即继承)和特定的n对n关系。尝试在ER图中对此进行建模:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|902971|​|902972|📷|atomic|offset|length|902973|902974|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://lh3.ggpht.com/_iOSSgpmzHfc/S1Weyc4gWiI/AAAAAAAADek/vRDup_yh3KQ/s800/UMLDiagram.jpg|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

I have found the UML class diagram to be much more helpful for doing a logical data model or domain model than an Entity-Relationship Diagram. It is more expressive, having generalization (ie inheritance) and specific n-to-n relationships. Try to model this in an ER Diagram :)

<img src="https://lh3.ggpht.com/_iOSSgpmzHfc/S1Weyc4gWiI/AAAAAAAADek/vRDup_yh3KQ/s800/UMLDiagram.jpg" alt="alt text">

In my experience most architectural documentation has been ad-hoc at best,and, aside from more structured dead-tree kinds of writing I've yet to see formal UML in actual use, and I've worked with few, if any developers who'd be able to clearly or correctly build UML diagrams - it seems to be used more as a kind of "graphical psuedocode".

Given that, I'm curious as to whether anyone has experience using UML in internal documentation and communicating system function between team members. Is this a tool/mode of communication people really use in the day-to-day? Is it helpful, overspecified? Have you worked in environments where precise UML mattered or was useful?

Common use of UML

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在我的经验中，大多数架构文档充其量都是特别的，除了更结构化的死树类型的写作之外，我还没有看到正式的UML在实际使用中，我几乎没有接触过能够清楚或正确地构建UML图的开发人员-它似乎更多地被用作一种“图形伪代码”。鉴于此，我很好奇是否有人有在内部文档和团队成员之间交流系统功能方面使用UML的经验。这是人们在日常生活中真正使用的一种工具/沟通方式吗？它是否有帮助，是否被过度指定了？您是否曾在精确的UM

问UML的常见用法
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML的常见用法EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML的常见用法
EN