<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Writing Passionate Requirements</title>
	<atom:link href="http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sun, 12 Feb 2012 19:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Fernando Garrido Vaz</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-652220</link>
		<dc:creator>Fernando Garrido Vaz</dc:creator>
		<pubDate>Thu, 11 Nov 2010 18:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-652220</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Writing Passionate Requirements http://bit.ly/bTbRjh #baot #requirements Congrats @sehlhorst, very inspirational post!&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Writing Passionate Requirements <a href="http://bit.ly/bTbRjh" rel="nofollow">http://bit.ly/bTbRjh</a> #baot #requirements Congrats @sehlhorst, very inspirational post!</span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyner Blain</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-378573</link>
		<dc:creator>Tyner Blain</dc:creator>
		<pubDate>Wed, 28 May 2008 02:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-378573</guid>
		<description>&lt;strong&gt;Defining Problems With Cause And Effect Diagrams...&lt;/strong&gt;


The Cause and Effect diagram is also known as a fish bone diagram, because it resembles the skeleton of a fish.  Using a cause and effect diagram can be the most effective way to define the problems that you intend to solve with your product.  Get you...</description>
		<content:encoded><![CDATA[<p><strong>Defining Problems With Cause And Effect Diagrams&#8230;</strong></p>
<p>The Cause and Effect diagram is also known as a fish bone diagram, because it resembles the skeleton of a fish.  Using a cause and effect diagram can be the most effective way to define the problems that you intend to solve with your product.  Get you&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yogi Amature</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-360084</link>
		<dc:creator>Yogi Amature</dc:creator>
		<pubDate>Tue, 29 Apr 2008 18:39:41 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-360084</guid>
		<description>Thanks Scott for your valuable feedback.</description>
		<content:encoded><![CDATA[<p>Thanks Scott for your valuable feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-355957</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 25 Apr 2008 02:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-355957</guid>
		<description>Yogi - 

Here&#039;s an article I wrote a while ago showing the differences between different requirements documents and how to use them together.

&lt;a href=&quot;http://tynerblain.com/blog/2006/01/20/document-proliferation/&quot; rel=&quot;nofollow&quot;&gt;Requirements Document Proliferation&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Yogi &#8211; </p>
<p>Here&#8217;s an article I wrote a while ago showing the differences between different requirements documents and how to use them together.</p>
<p><a href="http://tynerblain.com/blog/2006/01/20/document-proliferation/" rel="nofollow">Requirements Document Proliferation</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-355955</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 25 Apr 2008 02:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-355955</guid>
		<description>Yogi,

Welcome to Tyner Blain!  I think system analysts are a subset of, or specialized role within the community of, business analysts.

A systems analyst will often write an SRS.  When there is no systems analyst, it can be a BA or a product manager who writes it.  

Hope that helps.</description>
		<content:encoded><![CDATA[<p>Yogi,</p>
<p>Welcome to Tyner Blain!  I think system analysts are a subset of, or specialized role within the community of, business analysts.</p>
<p>A systems analyst will often write an SRS.  When there is no systems analyst, it can be a BA or a product manager who writes it.  </p>
<p>Hope that helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yogi Amature</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-353895</link>
		<dc:creator>Yogi Amature</dc:creator>
		<pubDate>Wed, 23 Apr 2008 05:27:00 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-353895</guid>
		<description>Is Business Analyst and System Analyst two different profiles.

The base of my above questions is as I believe that Business analyst and System analyst are different. If I am write who write the SRS with what contents. If Only Business Analyst write SRS then why system specification are there. 

Hope I will get answers from some experts here

Thanks</description>
		<content:encoded><![CDATA[<p>Is Business Analyst and System Analyst two different profiles.</p>
<p>The base of my above questions is as I believe that Business analyst and System analyst are different. If I am write who write the SRS with what contents. If Only Business Analyst write SRS then why system specification are there. </p>
<p>Hope I will get answers from some experts here</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yogi Amature</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-353445</link>
		<dc:creator>Yogi Amature</dc:creator>
		<pubDate>Tue, 22 Apr 2008 19:34:45 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-353445</guid>
		<description>Hello Guys

I know these question might be very basic but sometimes I really get confused in documenting requirements i.e. making SRS. 

Question 1: Do SRS document both business requirement and software requirement. 
Question 2: Is Software requirement specification and functional requirement specification same thing. 
Question 3: Can we consider desing specification in SRS?   
Question 4: Is documenting requirement for a website application different from other requirement gathering process. I guess if anyone can help me on this very simple example i.e. e.g. registration on a website. How do we document requirements for user registration on website. 

Do we document what fields are used for registration out of which are required and which are not along with what is the required number of the character in the field. do we mention what happens when user sucessfully registered on the site i.e. directed to home page of the site.

Is there any site where I can see a good written SRS with a sample project.

Really Need this information which can help me a lot.</description>
		<content:encoded><![CDATA[<p>Hello Guys</p>
<p>I know these question might be very basic but sometimes I really get confused in documenting requirements i.e. making SRS. </p>
<p>Question 1: Do SRS document both business requirement and software requirement.<br />
Question 2: Is Software requirement specification and functional requirement specification same thing.<br />
Question 3: Can we consider desing specification in SRS?<br />
Question 4: Is documenting requirement for a website application different from other requirement gathering process. I guess if anyone can help me on this very simple example i.e. e.g. registration on a website. How do we document requirements for user registration on website. </p>
<p>Do we document what fields are used for registration out of which are required and which are not along with what is the required number of the character in the field. do we mention what happens when user sucessfully registered on the site i.e. directed to home page of the site.</p>
<p>Is there any site where I can see a good written SRS with a sample project.</p>
<p>Really Need this information which can help me a lot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-85644</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 03 Apr 2007 15:40:05 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-85644</guid>
		<description>Thanks Rolf for reading and commenting!

I guess it is a bit of a stretch - the goal is to write passionately, from which the readers will gain a sense of excitement.

Good point about &quot;breaking the rules&quot; - the best entry-level writing advice I ever got was &quot;follow the rules.&quot;  The best advanced writing advice I ever got was &quot;break the rules, appropriately.&quot;

The crux is in defining &quot;appropriately&quot; - which makes it difficult to encourage.  

Thanks again,</description>
		<content:encoded><![CDATA[<p>Thanks Rolf for reading and commenting!</p>
<p>I guess it is a bit of a stretch &#8211; the goal is to write passionately, from which the readers will gain a sense of excitement.</p>
<p>Good point about &#8220;breaking the rules&#8221; &#8211; the best entry-level writing advice I ever got was &#8220;follow the rules.&#8221;  The best advanced writing advice I ever got was &#8220;break the rules, appropriately.&#8221;</p>
<p>The crux is in defining &#8220;appropriately&#8221; &#8211; which makes it difficult to encourage.  </p>
<p>Thanks again,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf</title>
		<link>http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/comment-page-1/#comment-84393</link>
		<dc:creator>Rolf</dc:creator>
		<pubDate>Fri, 30 Mar 2007 09:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/06/15/writing-passionate-requirements/#comment-84393</guid>
		<description>While I totally agree with this attribute of a good requirement I think it is not an attribute of a good requirement :-) it is an attribute of the requirements author. Suggestion for a new way to put it: passion on writing the requirements can be measured in number of justified breaks of rules concerning writing, and in number of suggestions to improve the writing practice rules.</description>
		<content:encoded><![CDATA[<p>While I totally agree with this attribute of a good requirement I think it is not an attribute of a good requirement :-) it is an attribute of the requirements author. Suggestion for a new way to put it: passion on writing the requirements can be measured in number of justified breaks of rules concerning writing, and in number of suggestions to improve the writing practice rules.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

