<?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"
	>

<channel>
	<title>Agile Cases &#187; &#187; Modeling</title>
	<atom:link href="http://www.agilecases.com/tag/modeling/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agilecases.com</link>
	<description>a web of sketches, resources and comments</description>
	<pubDate>Wed, 13 Aug 2008 02:13:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
	<language>en</language>
			<item>
		<title>Separation of design and requirements may have destroyed more software projects than waterfall&#8230;</title>
		<link>http://www.agilecases.com/2008/03/25/separation-of-design-and-requirements-may-have-destroyed-more-software-projects-than-waterfall/</link>
		<comments>http://www.agilecases.com/2008/03/25/separation-of-design-and-requirements-may-have-destroyed-more-software-projects-than-waterfall/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 12:51:47 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Agent]]></category>

		<category><![CDATA[Lesson]]></category>

		<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/2008/03/25/separation-of-design-and-requirements-may-have-destroyed-more-software-projects-than-waterfall/</guid>
		<description><![CDATA[Vasco Duarte of the Software Development Today weblog sums up why separation of design and requirements may have destroyed more software projects than waterfall&#8230; ]]></description>
			<content:encoded><![CDATA[<p>Vasco Duarte of the Software Development Today weblog sums up why <a href="http://softwaredevelopmenttoday.blogspot.com/2008/03/separation-of-design-and-requirements.html">separation of design and requirements may have destroyed more software projects than waterfall&#8230;</a> </p>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/2008/03/25/separation-of-design-and-requirements-may-have-destroyed-more-software-projects-than-waterfall/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Check out the business motivation model: &#8230;</title>
		<link>http://www.agilecases.com/2008/03/06/check-out-the-business-motivation-model/</link>
		<comments>http://www.agilecases.com/2008/03/06/check-out-the-business-motivation-model/#comments</comments>
		<pubDate>Thu, 06 Mar 2008 22:44:42 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Ability]]></category>

		<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/2008/03/06/check-out-the-business-motivation-model/</guid>
		<description><![CDATA[Check out version 1.3 of the business motivation model.]]></description>
			<content:encoded><![CDATA[<p>Check out version 1.3 of the <a href="http://www.businessrulesgroup.org/second_paper/BRG-BMM.pdf">business motivation model</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/2008/03/06/check-out-the-business-motivation-model/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Oxford English Dictionary defines a  &#8230;</title>
		<link>http://www.agilecases.com/2008/03/06/the-oxford-english-dictionary-defines-a/</link>
		<comments>http://www.agilecases.com/2008/03/06/the-oxford-english-dictionary-defines-a/#comments</comments>
		<pubDate>Thu, 06 Mar 2008 21:14:55 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Lesson]]></category>

		<category><![CDATA[Glossary]]></category>

		<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/2008/03/06/the-oxford-english-dictionary-defines-a/</guid>
		<description><![CDATA[The Oxford English Dictionary defines a sketch as a brief description or outline ‘to give the essential facts or points of, without going into details.’ Sketches are mostly reflections of brief thoughts.]]></description>
			<content:encoded><![CDATA[<p>The Oxford English Dictionary defines a sketch as a brief description or outline ‘to give the essential facts or points of, without going into details.’ Sketches are mostly reflections of brief thoughts.</p>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/2008/03/06/the-oxford-english-dictionary-defines-a/feed/</wfw:commentRss>
		</item>
		<item>
		<title>View</title>
		<link>http://www.agilecases.com/view/</link>
		<comments>http://www.agilecases.com/view/#comments</comments>
		<pubDate>Wed, 05 Mar 2008 21:09:39 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Lesson]]></category>

		<category><![CDATA[Architecture]]></category>

		<category><![CDATA[Glossary]]></category>

		<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/view/</guid>
		<description><![CDATA[A view is a representation of the system from a particular viewpoint.]]></description>
			<content:encoded><![CDATA[<p>A view is a representation of the system from a particular <a href="http://www.agilecases.com/viewpoint/" class="thickbox" >viewpoint</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/view/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Viewpoint</title>
		<link>http://www.agilecases.com/viewpoint/</link>
		<comments>http://www.agilecases.com/viewpoint/#comments</comments>
		<pubDate>Wed, 05 Mar 2008 21:08:17 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Lesson]]></category>

		<category><![CDATA[Architecture]]></category>

		<category><![CDATA[Glossary]]></category>

		<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/viewpoint/</guid>
		<description><![CDATA[A viewpoint defines the perspective from which a view is taken. It is a specification of rules for constructing a view to address a (set of) stakeholder concern(s).
Attributes

Set of stakeholders
The interest of the stakeholders
The purpose addresses the stakeholder issues
The pattern used to construct the viewpoint
]]></description>
			<content:encoded><![CDATA[<p>A <strong>viewpoint</strong> defines the perspective from which a <a href="http://www.agilecases.com/view/" class="thickbox" >view</a> is taken. It is a specification of rules for constructing a view to address a (set of) stakeholder concern(s).</p>
<h3><strong>Attributes</strong></h3>
<ul>
<li>Set of stakeholders</li>
<li>The interest of the stakeholders</li>
<li>The purpose addresses the stakeholder issues</li>
<li>The pattern used to construct the viewpoint</li>
</ul>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/viewpoint/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
