<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Clint Modien</title>
    <link>http://www.boxesandarrows.com/person/379</link>
    <pubDate>Fri, 26 Jan 2007 14:52:24 GMT</pubDate>
    <description>Comments by Clint Modien</description>
    <item>
      <description>&lt;quote&gt;While this example is fairly trivial, more complex interactions can be built. In addition multiple storyboards can be used to represent different use cases. This is important for showing error conditions as well as different edge-cases.&lt;/quote&gt;&lt;br /&gt;
	&lt;p&gt;Why not just a visio uml diagram to illustrate the different use cases?  What&amp;#8217;s the advantage?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/storyboarding_rich_internet_applications_with_visio#content_2462</link>
      <guid>http://www.boxesandarrows.com/view/storyboarding_rich_internet_applications_with_visio#content_2462</guid>
      <pubDate>Fri, 26 Jan 2007 14:52:24 GMT</pubDate>
      <author>Clint Modien</author>
    </item>
    <item>
      <description>&lt;p&gt;&amp;gt;&amp;gt;&amp;#8221;While this example is fairly trivial, more complex interactions can be built. In addition multiple storyboards can be used to represent different use cases. This is important for showing error conditions as well as different edge-cases.&amp;#8221; &amp;gt;&amp;gt;&lt;/p&gt;

	&lt;p&gt;Why not just a visio uml diagram to illustrate the different use cases? What&amp;#8217;s the advantage?&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/storyboarding_rich_internet_applications_with_visio#content_2463</link>
      <guid>http://www.boxesandarrows.com/view/storyboarding_rich_internet_applications_with_visio#content_2463</guid>
      <pubDate>Fri, 26 Jan 2007 14:52:25 GMT</pubDate>
      <author>Clint Modien</author>
    </item>
  </channel>
</rss>
