如果我独自在一个项目中工作，UML 有多大用处
在大多数情况下，我们在项目中一起工作，但我们大多数人都有一些单独工作的项目。
在这样的项目中，使用 UML 是一个好主意吗？为什么？
先感谢您
In most cases we work together in projects but most of us have some projects which working on it alone.
In such projects, is it a good idea to use UML or not? and Why?
Thank you in advance
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
即使您独自工作，UML也会帮助您记录项目。
如果您还订阅了模型驱动开发和代码生成，那么如果您随后修改模型（包括保持上述文档为最新），工具支持可能会让您的生活变得更轻松。
Even if you are working alone, UML will help you to document your project.
If you also subscribe to Model-driven development and code generation, then the tool support may make your life easier if you subsequently revise your model (incl. keeping the documentation above up-to-date).
这取决于您处于开发的哪个阶段以及您是否已经了解 UML。如果您已经在编码，那么只需创建您认为对理解代码很重要的类图和序列图以及与其他项目的共同点。
你用什么语言来编码？
如果是 java，那么我会推荐 EclipseUML Omondo，因为您可以从多个项目创建模型。例如，我有 12 个项目，最终它们联合起来创建了一个非常大的项目。记录一切确实很困难。我确实反转了每个项目，然后通过合并所有 12 个项目来创建一个模型项目。最后，我创建了类图视图来解释我的项目的静态结构，并创建了序列图以了解方法正在做什么。该工具的优点在于您可以混合 .java 和 .class 类，并且序列图的逆向工程可以跟踪不同项目的类之间的反向工程。
我还添加了图形注释来解释我认为重要的内容，从大模型中创建了大约 100 个视图，并且我的项目确实有很好的文档记录。
工作完成了快乐的人:-)
It depends at which stage of the development you are and if you already know UML. If you are already codding then just create class and sequence diagrams of what you think is important to understand the code and what is in common with the other projects.
What language do you use to code ?
If java then I would recommend EclipseUML Omondo because you can create a model from more than one project. For example I had 12 projects which at tne end were united to create a very large project. It was really difficult to document everything. I did reversed every project then create a model project by merging all my 12 project. Finally I created class diagrams views to explain the static structure of my project and sequence diagram for understand what methods were doing. What is great with this tool is that you can mix .java and .class classes and that reverse engineering of sequence diagram can trace the reverse between classes from different projects.
I also added graphical comments to explain what I was considering important, created about 100 views from the big model and my project was really very well documented.
Job done Happy man :-)
如果几个月后你再看自己的代码，你会觉得它是另一个人写的。因此，即使对于单独的项目，文档通常也是一件好事。您可以使用更简单的 UML 图，但我确实相信它们很有用。实际上，在我目前的工作中，我们以类似的方式工作，并且 UML 图对我自己的项目有所帮助。
If you look at your own code some months later, you will feel like another person wrote it. So documentation usually is a good thing even on solo projects. You can use simpler UML diagrams, but I do believe that they can be useful. Actually, on my current job, we work in a similar way and the UML diagrams had helped me on my own projects.