即使对于非常小的项目来说，UML 图也是绝对必要的吗？
UML 为我们提供了许多不同类型的图表。但在许多情况下，只有一小部分是真正必要的，您如何看待最有用的 UML 图，即使对于非常小的项目？
UML provides us with many different kinds of diagrams. but in many situations only small set of them is really necessary, what do you think about the most usefull UML diagrams, even for very small projects?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
嗯，这确实取决于项目。我认为仅仅创建任何 UML 图作为规则而不评估它是否真正有用是错误的。
然而，在一些明显的情况下它们是有用的：
如果您的项目在 OO 结构方面非常大，那么创建类图通常很有用。这样您就可以处理抽象，直到需要深入细节为止。
如果您的项目主要是 UI 驱动的，那么创建用例图作为定义需求的方式会非常有用。如果您可以让客户接受此方法，这将特别有用。
如果您的系统在对象之间有很多交互，那么创建序列图对于理解交互很有用。 ，我认为序列图对于开发人员来说是最直观的，因为我注意到很多开发人员本能地用简单的 powerpoint\visio 图表来绘制这样的交互图 - 即使他们对 UML 不熟悉。
如果您的系统将使用多种技术并需要大量硬件，部署图显然很有用。
我认为关键点是仅当软件变得复杂到我们需要抽象思考时才使用 UML - UML 有助于可视化和记录这些抽象。
Well, it really depends on the project. I think it is wrong to just create any UML diagram as a rule without assessing if it will be really usefull.
However there are some obvious situations when they're usefull:
If your project will be any way large in terms of OO structure then it is usually usefull to create a class diagram. That way you can deal in abstractions until it is time to get stuck into details.
If you project will be mostly UI driven then it can be quite useful to create a Use Case diagram as a way of defining requirements. This is especially useful if you can get your customer to buy into this method.
If it looks like your system will have many interactions between objects then creating a sequence diagram can be usefull for understanding interactions. Also, I think sequence diagrams are the most intuitive for developers as I notice a lot of developers instinctively diagram there interactions like this - even if they're not familiar in UML - in simple powerpoint\visio diagrams.
Deplyoment Diagrams are obviously usefull if your system will use many technolegies and require a lot of HW.
I think key point is that only use UML when the software becomes complicated to the point where we need to think in abstractions - UML helps visualise and document these abstractions.
我不认为 UML 图是项目文档的重要组成部分，无论我们谈论的是大项目还是小项目。
周围的良好评论比复杂的图表更有价值。
我个人的印象是UML是学术界的一个玩具。这是我唯一听到和看到人们使用 UML、SOA 等的地方。
在我的工作实践中，我几乎没有见过 UML。好吧，也许有一次在我的学期项目和我目前的工作中，我们在内部 FTP 服务器上的某个地方有几个八年前的（并且同样已弃用的）图表。
I do not think UML diagrams are essential part of a project documentation whether we're talking about big or small projects.
Good comments around provide much more value than sophisticated diagrams.
I personally have an impression UML is a toy of the academia world. It's the only place I was hearing and seeing people running around with UML, SOA and so on.
In my working practice I've barely seen UML at all. Well, maybe once during my term project and at my current job where we've got a couple of eight-years-old (and just the same deprecated) diagrams somewhere on the internal FTP server.
通常，正式的 UML 对于小型项目来说太多了。只需坚持基本的类图和简单的用例图即可。
小型项目（根据我的经验）更容易发生变化，因此您的图表经常会过时。您更有可能使不太正式的图表保持最新状态，而不是重做所有花哨的 UML 内容。
Usually formal UML is too much for small projects. Just stick to basic class diagrams and simple use-case diagrams.
Small projects are (in my experience) more often subject to change so your diagrams will be out-of-date very often. You are much more likely to keep a less formal diagram up-to-date than redo all the fancy UML stuff.
UML 已经死了，没有人使用它。
唯一使用 UML 的人是顾问类型，他们写的文章试图变得正式、花哨，但缺乏实质内容。
如果 UML 如此出色，为什么我找不到 Google 在 googlecode 上发布的任何项目？
Ruby、Python、DOT NET 或 Java 的 UML 在哪里？
UML is dead, nobody who matters uses it.
The only people that use UML are consultant types who write articles and are trying to be formal and fancy and lack substance.
If UML is so great why cant i find any for any of the projects that Google publishes on googlecode ?
Where is the UML for Ruby or Python or DOT NET or Java ?
UML 已经死了，因为使用了开源蹩脚工具！许多公司使用免费工具，只创建一些图表，根本没有进行任何培训，然后他们说这没有用。
这是非专业的，而且对 UML 的使用非常有限，这对项目来说是一场真正的灾难！
UML is dead because the use of open source crapy tools !! Many companies take free tools and just create few diagrams, no training at all then they say that this is not useful.
This is non professional and very limited use of UML is a real disaster for projects !!