<p>The <a href="https://go-proverbs.github.io/">go proverb</a> in the title made me wonder:</p>
<p>1) Software: Which are your favorite tools to help you design the architecture of a system before you start coding?</p>
<p>2) Diagram: Are you using UML or something else?</p>
<p>3) Examples: Are you aware of any open source Go project that has published some architecture diagrams that name the components etc?</p>
<p>I understand that designing the architecture is not Go specific but I'd like to know what gophers prefer to use.</p>
<hr/>**评论:**<br/><br/>guenther_mit_haar: <pre><p>I'm interested in this topic too. Mid April is a hackathon in my town and i want to participate to build a tool for automatic UML generation from go source code. Basically lay out all structs with their respective methods and all interfaces they implictly implements as diagramm (because sometimes i wish such a tool if i inspect foreign libraries)</p></pre>ctcherry: <pre><p>I've read of people using really pragmatic (read: simple) tools, and those are also the ones I use:</p>
<p>1) Writing tool and compatible writing surface (whiteboard, paper, etc)</p>
<p>2) Nothing formal. Named boxed with arrows, state diagrams, tables, lists, etc.</p>
<p>3) I'm not aware of any but I haven't looked either.</p></pre>
这是一个分享于 的资源,其中的信息可能已经有所发展或是发生改变。
入群交流(和以上内容无关):加入Go大咖交流群,或添加微信:liuxiaoyan-s 备注:入群;或加QQ群:692541889
- 请尽量让自己的回复能够对别人有帮助
- 支持 Markdown 格式, **粗体**、~~删除线~~、
`单行代码`
- 支持 @ 本站用户;支持表情(输入 : 提示),见 Emoji cheat sheet
- 图片支持拖拽、截图粘贴等方式上传