<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Comments on Automating Diagrams with Visio</title>
    <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio</link>
    <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
    <description>By doing the demanding intellectual work first and then forcing the tools to succumb to need to produce seemingly speedy deliverables, you can get around the difficulty of choosing between "Good, Fast and Cheap." Here's one approach using Excel and Visio.
</description>
    <item>
      <description>&lt;p&gt;Thank you, thank you, thank you to Benjamin Bennett &amp;#8211; you&amp;#8217;ve made my life SO much easier!&lt;/p&gt;

	&lt;p&gt;I read this article the day I was starting to map a huge web-based application site for a client. Using Visio. My first reaction was, &amp;#8220;Is the author nuts? How is using two applications automating anything?&amp;#8221; (This is still my reaction.)&lt;/p&gt;

	&lt;p&gt;But I read through the comments, and came across Bennett&amp;#8217;s mention of Inspiration. I immediately downloaded the trial copy and used it to map a third of the app in just one afternoon &amp;#8211; a feat that would&amp;#8217;ve taken at least a couple of long days using Visio (the longer MS has owned this app, the more bloated and harder to use it&amp;#8217;s gotten). It&amp;#8217;s a good-looking map, too, just using the defaults. The learning curve is practically non-existent, especially compared with Visio (let alone adding Excel into the mix).&lt;/p&gt;

	&lt;p&gt;I bought the software &amp;#8211; the biz version, which has more useful templates than the school version &amp;#8211; and I&amp;#8217;m happy to say that I&amp;#8217;m abandoning Visio.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_251</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_251</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Lee Fleming</author>
    </item>
    <item>
      <description>&lt;p&gt;With my process, I&amp;#8217;m exporting Excel files as .csv (comma separated values). In Visio 5, you can do&amp;#8230;&lt;/p&gt;

	&lt;p&gt;File &amp;gt; Open (open dialog window appears)&lt;br /&gt;&#160;&#160;&#160;&#160;Files of type: Text Files (*.txt,*.csv)&lt;br /&gt;&#160;&#160;&#160;&#160;Select file &amp;#8220;ex1_visio_import.csv&amp;#8221; &lt;br /&gt;&#160;&#160;&#160;&#160;Click Open (File Converter dialog window appears)&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;ve heard that you can work with Excel files directly in Visio 200x, but can&amp;#8217;t verify how you do that, since I work with Visio 5 (haven&amp;#8217;t upgraded yet).&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_250</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_250</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Michael</author>
    </item>
    <item>
      <description>&lt;p&gt;I&amp;#8217;m running Visio 2002, but i can&amp;#8217;t find the option to open Excel files&amp;#8230; when you click on &amp;#8220;Open File&amp;#8221; the Excel option is not included into the &amp;#8220;file type&amp;#8221; dropdown. Is it an optional filter or plug-in?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_249</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_249</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Joaquin Marquez</author>
    </item>
    <item>
      <description>&lt;p&gt;I&amp;#8217;ve run up against a limitation of the csv import in Visio. I thought the readers of this article would like to know about it.&lt;/p&gt;

	&lt;p&gt;I get an error if I try to give a shape a name longer than 31 characters. Of course, the error message doesn&amp;#8217;t tell you that.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_248</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_248</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Todd Barlow</author>
    </item>
    <item>
      <description>&lt;p&gt;Better yet: use the built-in outlining features of word&amp;#8230; works like a charm. We&#180;ve done this integrated with &lt;span class="caps"&gt;FLASH&lt;/span&gt;/XML to create 3d site maps that were really cool! Cheers&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_247</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_247</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Danilo Medeiros</author>
    </item>
    <item>
      <description>&lt;p&gt;To answer Christopher Fahey&amp;#8217;s question:&lt;/p&gt;

	&lt;p&gt;&amp;gt; Do you really make your flowcharts in Excel before putting them into Visio? You find this *easy*?&lt;/p&gt;

	&lt;p&gt;I said this in the article:&lt;/p&gt;

	&lt;p&gt;&amp;gt; The best approach is probably to first draw your flowchart on paper and number the shapes in the chart.&lt;/p&gt;

	&lt;p&gt;That&amp;#8217;s what I have done in the past&amp;#8212;draw flow charts on paper and then number and put into Excel. I worked with some software development teams where the flow charts were created to document offline processes/work flow to understand how a program that we were working on could mimick these steps. After going through the process with users, we diagrammed on paper what we thought we were hearing and flowed that into Excel/Visio. As we went through the flow charts, we found inconsistencies I made modifications via the spreadsheets, and was able to automate the changes.&lt;/p&gt;

	&lt;p&gt;Do I find the process easy? Yes and no. I found that it made it quicker to make changes. I did &lt;span class="caps"&gt;NOT&lt;/span&gt; worry so much about how pretty these charts turned out, and it helped that individual aspects of interaction were broken up into many use cases. Each case was diagrammed on 11&amp;#8221;x17&amp;#8221; paper, so I didn&amp;#8217;t worry much about having to continue across multiple pages.&lt;/p&gt;

	&lt;p&gt;In any case, the process is one that I used in the past, but not every time. I only used it for large scale projects. For smaller projects, I actually have been trying to use OmniGraffle more. I admit, after trying Inspiration for a few days, that I&amp;#8217;m going to consider using that for my next project. I&amp;#8217;m not really married to any tool, but really love when I can use a tool to do my work a little more efficiently.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_246</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_246</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Michael</author>
    </item>
    <item>
      <description>&lt;p&gt;Anything that could potentially squash two steps (1. create the content outline; 2. create the flow chart) into 1 would be great. The clean-up as George mentioned is the rub.&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;ve been playing with the text import in Visio for a while and have not been able to create a chart that is &lt;span class="caps"&gt;NOT&lt;/span&gt; radial (probably the layout least able to be cleaned up easily). There is a placementstyle field that can be used, but doesn&amp;#8217;t seem to work. Anyone else run into this? Granted I&amp;#8217;m running Visio2000 which may have a bearing.&lt;/p&gt;

	&lt;p&gt;Inspiration is a wonderful tool simply on account of its built-in outliner. It&amp;#8217;s limitation is it&amp;#8217;s unprecise page controls for multipage documents.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_245</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_245</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Chas</author>
    </item>
    <item>
      <description>&lt;p&gt;For flowcharting an interaction, I&amp;#8217;m not sure it&amp;#8217;s that efficient, but for site maps it could be quite useful. It&amp;#8217;s not really creating your flowcharts in Excel as much as creating a flowchart based on your content matrix, which you&amp;#8217;re doing anyway.&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;m currently working on a project involving three global sites, each with hundreds of pages (the content matrix takes up 20+ tabloid pages). Having to hand-draw site maps that large is a real pain&amp;#8212;particularly when all-too-often revisions occur.&lt;/p&gt;

	&lt;p&gt;Visio 2002 gives you more control over how the diagram gets laid out, so I&amp;#8217;m experimenting with that to see if I can avoid the sort of clean-up Michael talks about&amp;#8212;since that&amp;#8217;s the major obstacle to this being useful for me.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_244</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_244</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>George Olsen</author>
    </item>
    <item>
      <description>&lt;p&gt;Do you really make your flowcharts in Excel before putting them into Visio? You find this *easy*?&lt;/p&gt;

	&lt;p&gt;To me, Visio&amp;#8217;s core strength is not in its ability to render easy-to-understand diagrams (although that is clearly a plus). Rather, it is useful because it allows you to &lt;span class="caps"&gt;QUICKLY&lt;/span&gt; translate abstract ideas about cause-effect relationships, information structures, etc. into concrete documentation. It seems to me that designing the flowchart for, say, a simple registration process might take me about 10 or 20 times longer if I did it in Excel first.&lt;/p&gt;

	&lt;p&gt;I&amp;#8217;ve often heard of the benefits of using the Visio/Excel connection to translate graphic information into spreadsheet data (for example to convert a graphical site map into a tabular content inventory). But this is the first time I&amp;#8217;ve ever heard anyone suggest going in the other direction.&lt;/p&gt;

	&lt;p&gt;Am I missing something about the benefits of this?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_243</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_243</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Christopher Fahey</author>
    </item>
    <item>
      <description>&lt;p&gt;Has anyone used (or is using) NetObjects Fusion to do site architectures and wireframes?&lt;/p&gt;

	&lt;p&gt;I was forced to switch over from Visio in the middle of a project. I can&amp;#8217;t tell if I hate it for the right reasons, or if I&amp;#8217;m just too used to Visio, but I&amp;#8217;d love any comments on using either.&lt;/p&gt;

	&lt;p&gt;Sorry for getting a little OT. Meanwhile&amp;#8212;I&amp;#8217;ll sneak back into Visio to implement Michael&amp;#8217;s solutions (thanks, by the way!)....&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_242</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_242</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:59 GMT</pubDate>
      <author>Melissa Bradley</author>
    </item>
    <item>
      <description>&lt;p&gt;Thanks, Benjamin. I had heard of Inspiration, but hadn&amp;#8217;t used it&amp;#8212;my team uses Visio 5 because it&amp;#8217;s one of our corporate standard applications. I&amp;#8217;ve actually been using OmniGraffle more, however, and exporting to &lt;span class="caps"&gt;PDF&lt;/span&gt;, but OG can&amp;#8217;t import data like Visio does. I will definitely try Inspiration, though, because I&amp;#8217;m much more comfortable using my PowerBook than my PC laptop.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_241</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_241</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:58 GMT</pubDate>
      <author>Michael</author>
    </item>
    <item>
      <description>&lt;p&gt;Ever hear of a piece of software called &amp;#8220;Inspiration&amp;#8221;?&lt;/p&gt;

	&lt;p&gt;It&amp;#8217;s another great tool for creating &amp;#8220;quick and dirty&amp;#8221; site maps.  Basically it allows you to import your Excel document (or enter your information directly) into its &amp;#8220;outline&amp;#8221; view&amp;#8230;&lt;/p&gt;

	&lt;p&gt;Providing a hierarchy as you described:&lt;br /&gt;1.0 Home&lt;br /&gt;   1.1 Section&lt;br /&gt;   1.2 etc&amp;#8230;.&lt;/p&gt;

	&lt;p&gt;Then it allows you to dynamically switch from that &amp;#8220;outline&amp;#8221; view to what it calls the &amp;#8220;diagram&amp;#8221; view.  Basically it automatically converts your hierarchical listing into a site map.  The default diagram is definitely better than that default Visio import, but still has plenty of room for improvement.  And to accomodate that, it does have basic tools to allow you to change shaps, colors, fonts, etc&amp;#8230;  The tools are not quite as nice as Visio (nor anywhere near as flexible as Illustrator) but they are definitely good enough to get the job done.&lt;/p&gt;

	&lt;p&gt;And perhaps one of the best features of Inpiration is that unlike Visio it work on Macintosh as well as Windows!!!&lt;/p&gt;

	&lt;p&gt;Anyway I&amp;#8217;m starting to feel like a salesman (which I&amp;#8217;m not) so I&amp;#8217;ll leave you with a link to their site&amp;#8230;&lt;br /&gt;&lt;a href="http://www.inspiration.com/productinfo/Inspiration/index.cfm" rel="nofollow"&gt;http://www.inspiration.com/productinfo/Inspiration/index.&amp;hellip;&lt;/a&gt;&lt;/p&gt;

	&lt;p&gt;And a &amp;#8220;down and dirty&amp;#8221; example of what the software can do&amp;#8230;  These are 140 pages of unpolished site maps that were literally produced in a matter of hours&amp;#8230;&lt;br /&gt;&lt;a href="http://bcbennett.com/b/portfolio/USBank_SiteMaps.pdf" rel="nofollow"&gt;http://bcbennett.com/b/portfolio/USBank_SiteMaps.pdf&lt;/a&gt; [1MB]&lt;br /&gt;(Caution: I&amp;#8217;ve heard this download is painfully slow, so be patient.)&lt;/p&gt;

	&lt;p&gt;Enjoy!&lt;br /&gt;_B&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_240</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_240</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:58 GMT</pubDate>
      <author>Benjamin Bennett</author>
    </item>
    <item>
      <description>&lt;p&gt;Efficiency rocks, great article!&lt;/p&gt;

	&lt;p&gt;I also found having some stencils in Visio really increases my efficiency. The only drawback with being efficient is managing expectations. At my previous job, I would often be able to do a simple but yummie looking sitemap (that didn&amp;#8217;t require much thinking) in 10 minutes, but if asked for one, I always delivered it a few hours later (when possible).&lt;/p&gt;

	&lt;p&gt;I did that because I noticed that the project managers where starting to look at sitemaps as something &amp;#8220;Peter can quickly throw together&amp;#8221;. It&amp;#8217;s harder to explain the thinking time some maps need, than to let them think sitemaps just take time.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_239</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_239</guid>
      <pubDate>Tue, 28 Aug 2007 00:31:00 GMT</pubDate>
      <author>PeterV  </author>
    </item>
    <item>
      <description>&lt;p&gt;Thanks, Jess. Yes, it really helps to use some numbering or lettering scheme to identify each node. We do this with our team for stuff like page identification in content inventories, for taxonomy identification, and such. Working with Perl, it&amp;#8217;s easy to manipulate data on a server if nodes are identified this way.&lt;/p&gt;

	&lt;p&gt;Glad you mentioned that Visio 2002 deals with Excel natively&amp;#8212;should reduce the steps for people.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_238</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_238</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:58 GMT</pubDate>
      <author>Michael</author>
    </item>
    <item>
      <description>&lt;p&gt;Great article! It&amp;#8217;s great if you can get your team to organize functional specs with hierarchical numbering too&amp;#8230;it can become a precursor to this.&lt;/p&gt;

	&lt;p&gt;btw, Visio 2002 has native Excel support &amp;#8211; no need to export to a comma-separated text file&amp;#8230;&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_237</link>
      <guid>http://www.boxesandarrows.com/view/automating_diagrams_with_visio#content_237</guid>
      <pubDate>Fri, 26 Jan 2007 14:49:58 GMT</pubDate>
      <author>Jess</author>
    </item>
  </channel>
</rss>
