<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Userxp &#187; usecase</title>
	<atom:link href="http://www.userxp.co.uk/tag/usecase/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.userxp.co.uk</link>
	<description>User experience design</description>
	<lastBuildDate>Tue, 02 Mar 2010 14:08:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Interface description documentation</title>
		<link>http://www.userxp.co.uk/2008/01/interface-description-documentation/</link>
		<comments>http://www.userxp.co.uk/2008/01/interface-description-documentation/#comments</comments>
		<pubDate>Wed, 30 Jan 2008 14:15:49 +0000</pubDate>
		<dc:creator>Neil</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[information architecture]]></category>
		<category><![CDATA[Interaction design]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[usecase]]></category>
		<category><![CDATA[wireframe]]></category>

		<guid isPermaLink="false">http://www.userxp.org/blog/?p=21</guid>
		<description><![CDATA[While browsing the archives at thinkvitamin.com I came across an article by Robert Hoekman Jr called Deliverables That Work: Design Description Documents.  In it he suggests combining use cases and wireframes or screenshot to make single design document.  I generally provided detailed notes about the behaviour of the interface as part of my wireframes, however [...]]]></description>
			<content:encoded><![CDATA[<p><img style="border: 0pt none; margin-left: 8px; margin-right: 8px;" src="http://www.userxp.co.uk/wp-content/wireframe.jpg" border="0" alt="Wireframe" hspace="8" align="left" />While browsing the archives at <a title="Thinkvitamin webdesign articles" href="http://www.thinkvitamin.com">thinkvitamin.com</a> I came across an article by <span><span style="color: #34350a;">Robert Hoekman Jr</span></span> called <a title="Permanent Link: Deliverables That Work: Design Description Documents" href="http://www.thinkvitamin.com/features/design/deliverables-that-work-design-description-documents">Deliverables That Work: Design Description Documents</a>.  In it he suggests combining use cases and wireframes or screenshot to make single design document.  I generally provided detailed notes about the behaviour of the interface as part of my wireframes, however I like his suggest of using usecases.</p>
<p>One of the advantages of usecases is that they detail the exceptions to the normal flow.  this is something that sometimes is missed when creating wireframes and results in the developer having to decide what to do as they come across issues.</p>
<p>The only issue I can see with this suggestion is that some times use cases can use multiple screens.  In these instances I would suggest integrating the use case with a flow diagram and linking from the diagram to the appropriate pages.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.userxp.co.uk/2008/01/interface-description-documentation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

