<?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>interaction design, neuroscience, innovation, socialpatterns | interaction design, neuroscience, innovation, social</title>
	<atom:link href="http://www.julius.com.br/tag/patterns/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.julius.com.br</link>
	<description>change perspectives</description>
	<lastBuildDate>Mon, 09 Jan 2012 19:31:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Writing Formal Use Cases</title>
		<link>http://www.julius.com.br/artigo/writing-formal-use-cases/#utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
		<comments>http://www.julius.com.br/artigo/writing-formal-use-cases/#comments</comments>
		<pubDate>Sun, 14 Mar 2010 02:45:41 +0000</pubDate>
		<dc:creator>julius</dc:creator>
				<category><![CDATA[artigo]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[actionscript]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[flash]]></category>
		<category><![CDATA[patterns]]></category>

		<guid isPermaLink="false">http://www.julius.com.br/?p=96</guid>
		<description><![CDATA[Typically you&#8217;ll want to create formal use cases for a functional requirements document. In this section we&#8217;ll look at how to create a formal use case. A formal use case can include the following sections: Primary actor: A description of the user who drives the operations outlined by the use case. The description of the primary actor can include things such as the role of the user (e.g. anonymous, basic, administrator, etc.) as well as characteristics of the user that may be relevant to how they interact with the application (e.g. age, disabilities, etc.) Preconditions: Those conditions that must be met for the use case to proceed. Main success scenario: A more granular, step-based description of the way the application works than is given in the basic or casual formats. Alternative scenarios: More granular, step-based descriptions of the ways the application will handle alternative uses than are given in the casual format. Special requirements: A list of requirements for the use case that don&#8217;t fit as part of the main or alternative scenarios. Open issues: A list of notes including questions that must be answered to fully implement a solution for the use case. Bibliograph: Advanced ActionScript 3 with Design [...]]]></description>
			<content:encoded><![CDATA[<p>Typically you&#8217;ll want to create formal use cases for a functional requirements document. In this section we&#8217;ll look at how to create a formal use case. A formal use case can include the following sections:</p>
<p><strong> Primary actor</strong>: A description of the user who drives the operations outlined by the use case. The description of the primary actor can include things such as the role of the user (e.g. anonymous, basic, administrator, etc.) as well as characteristics of the user that may be relevant to how they interact with the application (e.g. age, disabilities, etc.)</p>
<p><strong> Preconditions:</strong> Those conditions that must be met for the use case to proceed.</p>
<p><strong>Main success scenario:</strong> A more granular, step-based description of the way the application works than is given in the basic or casual formats.</p>
<p><strong> Alternative scenarios</strong>: More granular, step-based descriptions of the ways the application will handle alternative uses than are given in the casual format.</p>
<p><strong>Special requirements:</strong> A list of requirements for the use case that don&#8217;t fit as part of the main or alternative scenarios.</p>
<p><strong> Open issues: </strong>A list of notes including questions that must be answered to fully implement a solution for the use case.<br />
Bibliograph:</p>
<p><a href="http://my.safaribooksonline.com/0321426568" target="_blank">Advanced ActionScript 3 with Design Patterns</a>, By Joey Lott, Danny Patterson</p>
]]></content:encoded>
			<wfw:commentRss>http://www.julius.com.br/artigo/writing-formal-use-cases/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

