This depends on the project at hand; design diagrams could be found in the source tree, or on the project's website, or any number of places. There may not even be design diagrams at all -- they're not strictly necessary for software development.
The reality is that most industry strength software is written without design diagrams, class diagrams and/or other UML style documentation.
Why? Because most experienced developers (including me) do not see enough value/cost benefits from doing it.
Developers are relatively quick to adapt tools that are practical and helpful (test tools, source control, code analyzers, profilers etc.) so it is not a question of developers being "old dogs" and/or not wanting to improve the tools they use. If design diagrams etc. actually helped speed up development and/or improved product quality then it would be used a lot more than it is. However it doesn't so it isn't. And this is despite 30+ years of "guru" after "guru" trying to push yet another box/sphere/line tool down developers throat :-)
发布评论
评论（2）
这取决于手头的项目；设计图可以在源树、项目的网站或任何地方找到。甚至可能根本没有设计图——它们对于软件开发来说并不是绝对必要的。
This depends on the project at hand; design diagrams could be found in the source tree, or on the project's website, or any number of places. There may not even be design diagrams at all -- they're not strictly necessary for software development.
现实情况是，大多数行业实力软件都是在没有设计图、类图和/或其他 UML 样式文档的情况下编写的。
为什么？因为大多数有经验的开发人员（包括我）都没有看到这样做的足够价值/成本效益。
开发人员相对较快地适应实用且有用的工具（测试工具、源代码控制、代码分析器、分析器等），因此开发人员不是“老狗”和/或不想改进他们使用的工具的问题。如果设计图等确实有助于加快开发速度和/或提高产品质量，那么它的使用将会比现在更多。然而事实并非如此，所以事实并非如此。尽管 30 多年来“大师”不断地试图将另一个盒子/球体/线条工具推向开发人员:-)
The reality is that most industry strength software is written without design diagrams, class diagrams and/or other UML style documentation.
Why? Because most experienced developers (including me) do not see enough value/cost benefits from doing it.
Developers are relatively quick to adapt tools that are practical and helpful (test tools, source control, code analyzers, profilers etc.) so it is not a question of developers being "old dogs" and/or not wanting to improve the tools they use. If design diagrams etc. actually helped speed up development and/or improved product quality then it would be used a lot more than it is. However it doesn't so it isn't. And this is despite 30+ years of "guru" after "guru" trying to push yet another box/sphere/line tool down developers throat :-)