离散文氏图_使用海报和流程图代替散文来记录文档-Visio是否值得一千个字？

离散文氏图

We've got fairly powerful (but some say, complicated) Code Generation process that uses XML Schema along with (with thing) an interesting use of WSDL with an alternate binding.  Voyager is our flagship snazzy eFinance Server and using standard modelling tools (XMLSpy, VS.NET, etc) one (business person, computer wonk, whoever) can sit down and model all their Domain Objects, Request and Response Messages in XSD (nouns) and associate them with actual Voyager Operations (verbs) in WSDL.  Then rather than using a SOAP binding (if they were to talk to a Web Service with these messages) they can use a Voyager Binding in WSDL.  Then we run a Code Generation process on the WSDL/XSD and generate all the C# objects, messages, proxy layers, Word Documentation, yada yada yada. 

我们已经拥有了相当强大(但有些人说是复杂的)的代码生成过程，该过程使用XML Schema以及(带有东西)有趣的WSDL和备用绑定的使用。 Voyager是我们的旗舰级时髦eFinance服务器，使用标准建模工具(XMLSpy，VS.NET等)，一个人(商务人士，计算机工作者，无论谁)都可以坐下来并以XSD(名词)对所有域对象，请求和响应消息进行建模并将它们与WSDL中的实际旅行者操作(动词)相关联。 然后，可以使用WSDL中的Voyager绑定，而不是使用SOAP绑定(如果他们要通过这些消息与Web Service进行通信)。 然后，我们在WSDL / XSD上运行代码生成过程，并生成所有C＃对象，消息，代理层，Word文档，yada yada yada。

All this is built into our Continuous Integration Process so when one checks in an XSD into the Version Control System those artifacts are automatically built and made available to others.

所有这些都是内置于我们的持续集成过程中的，因此当一个人将XSD检入版本控制系统时，这些构件将自动构建并提供给其他人。

Since this is a fairly complex experience to the non-XML initiated, a lot of prose has been written and a lot of hand waving happens to explain this process.

由于这对于非XML发起的用户而言是相当复杂的体验，因此已经撰写了许多散文，并且发生了很多挥舞手法来解释这一过程。

Some users though felt the prose was, well, too prose-y, and wanted a quicker way to grok the material. 

但是，有些用户认为散文实在是太散文了，他们想要一种更快的方式来制作材料。

So, I spent two days in Visio creating a 44" by 34" poster (FOUR 11" by 17" pages or one big Plotter plot) that has the source of the XSDs, the source of the generated objects and stacks, as well as diagrams describing the relationships between objects when they exist in a running process. 

因此，我花了两天的时间在Visio中创建了一个44英寸乘34英寸的海报(四幅11英寸乘17英寸的页面或一个大的Plotter图)，其中包含XSD的源，生成的对象和堆栈的源以及描述对象在运行过程中存在时的关系的示意图。

People can look at the code generation progression as well as the composition of elements:

人们可以查看代码生成的进度以及元素的组成：

• Declarative XSDs (multiple ones, lots of imports, namespaces and custom attributes)
  声明性XSD(多个，多个导入，名称空间和自定义属性)
• Generated C# code
  生成的C＃代码
• Assembly names, class names, .NET namespace names
  程序集名称，类名称，.NET名称空间名称
• Resulting compiled assemblies
  生成的汇编程序集
• How those final build artifacts exist in a running system
  这些最终的构建工件如何在运行的系统中存在

I've finished the first draft (this screen shot is to give you an idea of the scope and size of this poster) and will share it with the team tomorrow. 

我已经完成了初稿(此屏幕快照是为了让您了解此海报的范围和大小)，并将于明天与团队分享。

How often do you or your groups create one large diagram instead of writing one or more large documents?  When are architecture & design posters useful and when are just trouble?

您或您的小组多久创建一张大图而不是编写一个或多个大文档？ 建筑和设计海报什么时候有用，什么时候麻烦？

翻译自: https://www.hanselman.com/blog/use-of-posters-and-flow-charts-in-lieu-of-prose-for-documentation-is-a-visio-is-worth-a-thousand-words

离散文氏图