blocks|key|889014|text|UML蒸馏+(马丁·福勒)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|889015|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321193687^0|0|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="https://rads.stackoverflow.com/amzn/click/com/0321193687" rel="noreferrer" rel="nofollow noreferrer">UML Distilled</a> by Martin Fowler

blocks|key|253768|text|和保罗C一样，我推荐UML蒸馏。它主要是关于UML的，但是它包含了很多关于总体设计的洞察力(虽然它在索引卡上坚持的太多了，海事组织)，它是简短的，令人愉快的阅读，而且切中要害。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|253769|我强烈建议反对+简单地说UML。这是我所拥有的最糟糕的O‘’Reilly的书:疯狂的稠密，难以阅读和蜿蜒。不值得把它印在纸上。|style|BOLD|253770|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/244457/uml-standards-guide-best-practices#244537|1|https://rads.stackoverflow.com/amzn/click/com/0321193687|2|http://oreilly.com/catalog/9781565924482/^0|1|3|0|A|5|1|0|5|2|8|7|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]|$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@$A|11|B|12|F|G]]|9|@$A|13|B|14|1|15]]|C|$]]|$1|H|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

Like <a href="https://stackoverflow.com/questions/244457/uml-standards-guide-best-practices#244537">Paul C</a>, I recommend <a href="https://rads.stackoverflow.com/amzn/click/com/0321193687" rel="nofollow noreferrer" rel="nofollow noreferrer">UML Distilled</a>. It is primarily about UML, but it contains a lot of insight about design in general (although it insists a bit too much on index cards IMO), it is short, pleasant to read, and to the point.

I strongly recommend against <a href="http://oreilly.com/catalog/9781565924482/" rel="nofollow noreferrer">UML in a Nutshell</a>. It is the worst O'Reilly book I have: insanely dense, hard to read and meandering. Not worth the paper it is printed on.

blocks|key|253864|text|给每个人买一份UML2.0风格的元素。工作完成了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|253865|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ambysoft.com/books/elementsUMLStyle.html^0|7|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Buy everyone a copy of <a href="http://www.ambysoft.com/books/elementsUMLStyle.html" rel="nofollow noreferrer">The Elements of UML 2.0 Style</a>. Job done.

blocks|key|253919|text|为了快速了解如何构建单独的UML图，我衷心推荐UML样式2.0的元素，并将我的建议放在我的建议所在，购买第二版以取代我的第一版。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|253920|除了这条建议之外，我认为在公司推出任何风格指南时，最重要的是要有一个本地反馈机制()，人们可以在该机制中对样式指南的哪些方面进行评论，特别是当您使用官方印刷指南时。wiki或类似的临时存储库应该就足够了。|style|BOLD|253921|我还建议高亮的图表是特别好的例子(或坏的例子，如果团队的幽默可以接受)。考虑一周的框架图表，就像你在这么多商店看到的员工一样。这给了一个温和的提醒，图表可读性被认真对待，但希望有足够的乐趣，以获得更多的认同的概念。|253922|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ambysoft.com/books/elementsUMLStyle.html^0|N|B|0|0|Y|7|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@$A|W|B|X|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

For a quick reference on how to compose individual UML diagrams, I heartily recommend <a href="http://www.ambysoft.com/books/elementsUMLStyle.html" rel="nofollow noreferrer">The Elements of UML Style 2.0</a> and I put my money where my recommendation lies by purchasing the 2nd edition to replace my 1st ed.

Apart from this recommendation, I think the most important thing in a company when introducing any style guide is to have a local feedback mechanism where people can post comments on which aspects of the style guide work for them, especially when you're using an official printed guide. A wiki or similar casual repository should suffice for this. 

I also suggest highlighting diagrams which were particularly good examples (or bad ones, if the team humor could take it). Consider a framed Diagram of the Week like the Employee of the Week you see in so many stores. That gives a gentle reminder that diagram readability is taken seriously but hopefully with enough fun to get more buy-in to the concept.

blocks|key|253712|text|我知道您可能想要一本容易阅读的书，但从您所描述的情况来看，我建议您使用在OMG上找到的规范。它们读起来有点多，但会像你所希望的那样完整。他们也有伦敦的文章和教程，可能是有帮助的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|253713|就书籍而言，我发现使用UML非常好，因为它处理软件开发过程以及UML和方法。|253714|entityMap|0|LINK|mutability|MUTABLE|url|http://www.uml.org/|1|https://rads.stackoverflow.com/amzn/click/com/0321269675^0|10|3|0|0|9|5|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

I know you probably want an easy to read book for this but from what you are describing I would suggest going with the specs found on <a href="http://www.uml.org/" rel="nofollow noreferrer">OMG</a> itself. They are a bit much to read but would be as complete as you could hope for. They also have lonks to articles and tutorials that may be helpful.

As far as books go I have found that <a href="https://rads.stackoverflow.com/amzn/click/com/0321269675" rel="nofollow noreferrer" rel="nofollow noreferrer">Using UML</a> is quite good since it tackles the software development process as well as the UML tools and methods.

Does anyone know of a decent UML standards guide?

My company currently relies on UML 2.0 (rightly or wrongly) to do the majority (read all) of their design work. I have been asked to come up with a draft 'best practice' guide to help other developers develop better models. The main problem I face is that Im slightly biased against UML... I feel that: if a diagram takes more than 5 mins to draw then its too complicated! Im looking for advice predominantly on what sort of standards I should be looking at. Also Im looking for an external source of information that can be used to balence out my irrational loathing of UML-heavy design and act as a 'sanitizer' for my suggestions.

Most of all Im looking to write a useful document rather than one that will sit moulding away in some obscure network directory.

Any ideas?

UML standards guide / Best Practices

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

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

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

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

社区新版编辑器体验调研

有人知道一个体面的UML标准指南吗？我的公司目前依赖于UML2.0(正确或错误)来完成他们的大部分设计工作(阅读全部)。我被要求提出一份“最佳实践”指南草案，以帮助其他开发人员开发更好的模型。我面临的主要问题是我对UML略有偏见.我觉得:如果一张图要花5分钟以上才能画出来，那就太复杂了！我主要是寻求关于我应该看什么样的标准的建议。此外，我正在寻找一个外部的信息来源，可以用来平衡我对UML重设计的不

问UML标准指南/最佳实践
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML标准指南/最佳实践EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML标准指南/最佳实践
EN