<?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>SachinKRaj weBLOG &#187; learn-srs</title>
	<atom:link href="http://blog.sachinkraj.com/tag/learn-srs/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sachinkraj.com</link>
	<description>Web Development Tutorials, How-To&#039;s and Design Tips</description>
	<lastBuildDate>Fri, 03 Feb 2012 18:07:32 +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>Software Requirements Specification (SRS) Template – Start Writing SRS For Your Project</title>
		<link>http://blog.sachinkraj.com/software-requirement-specification-srs-template/</link>
		<comments>http://blog.sachinkraj.com/software-requirement-specification-srs-template/#comments</comments>
		<pubDate>Thu, 04 Oct 2007 06:02:22 +0000</pubDate>
		<dc:creator>SachinKRaj</dc:creator>
				<category><![CDATA[Project Management]]></category>
		<category><![CDATA[good srs]]></category>
		<category><![CDATA[learn-srs]]></category>
		<category><![CDATA[project]]></category>
		<category><![CDATA[requirement]]></category>
		<category><![CDATA[Software Requirement Specification]]></category>
		<category><![CDATA[SRS]]></category>
		<category><![CDATA[srs-template]]></category>
		<category><![CDATA[write srs]]></category>

		<guid isPermaLink="false">http://blog.sachinkraj.com/?p=1226</guid>
		<description><![CDATA[<p style="float:right; margin:0 0 10px 15px; width:240px;">
		<img src="http://blog.sachinkraj.com/wp-content/uploads/2007/10/SRS.png" width="240" />
		</p>What is SRS? A SRS is basically an organization’s understanding (in writing) of a customer or potential client’s system requirements and dependencies at a particular point of time (usually) prior to any actual design or development work. It’s a two-way insurance policy that assures that both the client and the organization understand each other’s requirements from every [...]]]></description>
		<wfw:commentRss>http://blog.sachinkraj.com/software-requirement-specification-srs-template/feed/</wfw:commentRss>
		<slash:comments>204</slash:comments>
		</item>
	</channel>
</rss>

