EA is for making models - more functional than "pretty", so it sounds like you are using the wrong tool for the job. However, I've been in the same boat - so I know exactly what you're talking about!
I try and keep my diagrams as clean and presentable as possible - there's no doubt it contributes to making them more accessible. This tends to work well for me.
Other possibilities.....
Make dedicated "pretty" diagrams where necessary, and leave the more "serious" ones for the "real" work. this might not be so viable depending on the size and complexity of the models (and the rate of change).
Get a better tool.
Give the raw diagram to someone like a designer and get them to do you a new "pretty" one.
That said, I often have to present diagrams to a larger audience using PowerPoint or Keynote slide decks. In presentations it is very important to keep in mind what the public you are presenting to already know about the architecture and technology and what to you want them to understand.
If you present to a group of executives the message has to be abstracted and probably your diagrams should use a very simple notation of boxes and arrows. If you are presenting at your local user group you probably can use more semantic constructs in your diagrams --like aggregations and inheritance-- but you probably will need to abstract-out most of the things that are specific to your company and people from outside don't know about (e.g. replace a module called "XPTO 1.0" with "Legacy Billing System").
Once you know what level of detail you should use you can get a tool. i'd recommend simple diagram tools like OmniGraffle or Visio. If you want more UML features than those tools provide you may try JudeUML, it creates quite clean diagrams that can be easily edited in a proper graphic editor.
I also recommend Dan Roam's "The Back of the Napkin" ( http://amzn.to/c5khDx ). It's a very interesting book on how simpler graphic models can be effective.
Apologies that this is a bit off tangent, but I've always wondered what percentage of EA like modelling tools get used properly through a project.
Of the instances I've used it was difficult to keep full round-tripping going and it was more used as a conceptual architecture tool to get the message across to the team. So a diagram tool with organized files normally work fine and gets my pretty diagrams.
发布评论
评论（3）
EA 用于制作模型 - 功能性多于“美观性”，因此听起来您使用了错误的工具来完成这项工作。然而，我也曾经历过同样的事情——所以我完全知道你在说什么！
其他可能性......
在必要时制作专门的“漂亮”图表，并将更“严肃”的图表留给“真正”的工作。根据模型的大小和复杂性（以及变化率），这可能不太可行。
获取更好的工具。
将原始图表交给设计师之类的人，让他们为您做一个新的“漂亮”图表。
EA is for making models - more functional than "pretty", so it sounds like you are using the wrong tool for the job. However, I've been in the same boat - so I know exactly what you're talking about!
Other possibilities.....
Make dedicated "pretty" diagrams where necessary, and leave the more "serious" ones for the "real" work. this might not be so viable depending on the size and complexity of the models (and the rate of change).
Get a better tool.
Give the raw diagram to someone like a designer and get them to do you a new "pretty" one.
我强烈建议使用图表/UML 作为通信工具，而不是规范（请参阅http://martinfowler.com/bliki/UmlMode.html 和 http://fragmental.tw/2008/11/07/trying-to-write-architecture-specs-that-dont -suck-much-part-i-the-spec/）。
也就是说，我经常需要使用 PowerPoint 或 Keynote 幻灯片向更多观众展示图表。在演示中，记住您向公众演示的有关架构和技术的知识以及您希望他们理解的内容非常重要。
如果您向一组高管展示信息，则必须对信息进行抽象，并且您的图表可能应该使用非常简单的方框和箭头符号。如果您在本地用户组中进行演示，您可能可以在图表中使用更多语义结构（例如聚合和继承），但您可能需要抽象出大多数特定于您的公司和外部人员的内容不知道（例如，用“旧版计费系统”替换名为“XPTO 1.0”的模块）。
一旦您知道应该使用什么级别的详细信息，您就可以获得一个工具。我推荐简单的图表工具，例如 OmniGraffle 或 Visio。如果您想要比这些工具提供的更多 UML 功能，您可以尝试 JudeUML，它创建非常干净的图表，可以在适当的图形编辑器中轻松编辑。
我还推荐 Dan Roam 的《餐巾背面》( http://amzn.to/c5khDx )。这是一本非常有趣的书，讲述了简单的图形模型如何发挥作用。
I strongly recommend the use of diagrams/UML as a communication tool as opposed to specifications (see http://martinfowler.com/bliki/UmlMode.html and http://fragmental.tw/2008/11/07/trying-to-write-architecture-specs-that-dont-suck-much-part-i-the-spec/).
That said, I often have to present diagrams to a larger audience using PowerPoint or Keynote slide decks. In presentations it is very important to keep in mind what the public you are presenting to already know about the architecture and technology and what to you want them to understand.
If you present to a group of executives the message has to be abstracted and probably your diagrams should use a very simple notation of boxes and arrows. If you are presenting at your local user group you probably can use more semantic constructs in your diagrams --like aggregations and inheritance-- but you probably will need to abstract-out most of the things that are specific to your company and people from outside don't know about (e.g. replace a module called "XPTO 1.0" with "Legacy Billing System").
Once you know what level of detail you should use you can get a tool. i'd recommend simple diagram tools like OmniGraffle or Visio. If you want more UML features than those tools provide you may try JudeUML, it creates quite clean diagrams that can be easily edited in a proper graphic editor.
I also recommend Dan Roam's "The Back of the Napkin" ( http://amzn.to/c5khDx ). It's a very interesting book on how simpler graphic models can be effective.
抱歉，这有点离题，但我一直想知道 EA 之类的建模工具在项目中得到正确使用的比例是多少。
在我使用过的实例中，很难保持完整的往返，它更多地用作概念架构工具来向团队传达消息。因此，具有组织文件的图表工具通常可以正常工作并获得漂亮的图表。
@Adrian 你认为这里的“真正”工作是什么？
Apologies that this is a bit off tangent, but I've always wondered what percentage of EA like modelling tools get used properly through a project.
Of the instances I've used it was difficult to keep full round-tripping going and it was more used as a conceptual architecture tool to get the message across to the team. So a diagram tool with organized files normally work fine and gets my pretty diagrams.
@Adrian what do you term as 'real' work here?