您是否在敏捷开发实践中使用UML？ [英] Do you use UML in Agile development practices?

问题描述

感觉像早期的文物，但是UML确实有它的用途。然而，像极限编程那样的敏捷过程主张拥抱变化，这也意味着我应该减少文档和UML模型呢？因为他们给人的印象是设置一些石头。

It feels like an artifacts of an earlier days, but UML sure does have its use. However, agile processes like Extreme Programming advocates "embracing changes", does that also means I should make less documents and UML models as well? Since they gives the impression of setting something in stone.

UML在敏捷开发实践中属于哪里？除了初步规范文件外，我应该使用它吗？

Where does UML belongs in an Agile development practice? Other than the preliminary spec documents, should I use it at all?

编辑：找到这个：敏捷建模的潜在工件

推荐答案

Breeze通过罗伯特·马丁的敏捷原则，模式和实践

• 建议使用UML来沟通团队内的设计 ..共享语言;看看图表的人可以理解解决方案（比谈论更快），并且更快地做出贡献。


• 如果你发现团队一遍又一遍地制作相同的图表，有人会做出一个很好的版本，并将其存储在wiki /源代码控件上。加班更有用的图表将开始整理在该地方。


• 不要花太多时间 ...你不需要太多的细节。模型建立在建筑/建筑领域，因为建立一个房屋来验证设计是昂贵的/不可行的。软件不是这样的 - 您可以通过在您制作未经验证的设计的UML模型（具有所有铃声和口哨）的时间对其进行编码来验证您的设计。

• The suggestion is to use UML to communicate designs within the team.. a shared language ; anyone taking a look at the diagram can understand the solution (faster than talking about it) and contribute quicker.
• If you find the team making the same diagrams over and over again, someone will make a good version and store it on the wiki / source control. Overtime the more useful diagrams will start to collate in that place.
• Don't spend too much time on it... you don't need too much detail. Models are built in the architectural / construction realms because building a house to validate-test the design is expensive/infeasible. Software is not like that - you could validate your design by just coding it up in the time you make a UML model of your untested design (with all the bells and whistles).

所以说，UncleBob ...我同意。

So says UncleBob... I concur.

这篇关于您是否在敏捷开发实践中使用UML？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！