本文介绍了你还在使用UML吗?怎么样?做什么的?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

几年前,我们店里的每一个人都对UML感到疯狂。现在大家似乎已经冷却了。



如果在软件项目中仍然广泛使用UML,我很好奇。



如果是这样,这个用法限于白板?您是否将其用于文档?您是否使用工具来生成代码?



相关:




解决方案

我更喜欢通过瀑布适应的UML(例如白板草图)的敏捷 UML(例如在Visio中绘制的精细图表的过多文档)。



UML仍然有助于向其他人解释设计。例如。复合设计模式很容易用简单的类图解释(即在完成了这些有趣的类比之后)。



几个手绘的类和序列图在面对一个新的或旧的项目时,可以方便快捷地开始课程,并且没有足够的文档。



我的团队也成功地使用生成数据库模式的类图。也许有更好的方法,但这是另一个问题。


Few years back everybody in our shop was crazy with UML. Now everybody seems to have cooled off.

I am curious if there is still widespread use of UML in software projects.

If so, is this usage limited to whiteboarding? Do you use it for documentation? Do you use tools to generate code from it?

Related:

解决方案

I prefer the agile adoptation of UML (e.g. white board sketches) over the waterfall adaptation of UML (e.g. excessive documents of elaborate diagrams drawn in Visio).

UML is still useful for explaining a design to someone else. E.g. the composite design pattern is easy to explain with simple class diagrams (that is, after you are done with those interesting analogies).

A few hand-drawn class and sequence diagrams are handy to get a quick start when faced with a new or old project with classes littered all over the place and with no good enough documentation.

My team is also successfully using class diagrams for generating database schemas. Perhaps there are better ways, but that's another question.

这篇关于你还在使用UML吗?怎么样?做什么的?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-03 07:36