﻿<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Software Engineering</title>
    <description>Software Engineering</description>
    <link>http://web.iotap.com/Blogs/tabid/277/BlogId/39/Default.aspx</link>
    <language>en-US</language>
    <webMaster>kkumar@iotap.com</webMaster>
    <pubDate>Fri, 12 Mar 2010 00:18:40 GMT</pubDate>
    <lastBuildDate>Fri, 12 Mar 2010 00:18:40 GMT</lastBuildDate>
    <docs>http://backend.userland.com/rss</docs>
    <generator>Blog RSS Generator Version 3.5.1.19887</generator>
    <item>
      <title>Top 10 Estimation best practices in Agile</title>
      <description>&lt;p&gt;&lt;span style="font-family: 'Calibri','sans-serif'; font-size: 11pt; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin"&gt; By engaging the team in the estimation process we gain the benefits of additional insights and consensus building. Additional people bring different perspectives to estimating and spot things individuals may miss.&lt;/span&gt;&lt;/p&gt;&lt;a href=http://www.iotap.com/Blogs/tabid/277/EntryId/153/Top-10-Estimation-best-practices-in-Agile.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.iotap.com/Blogs/tabid/277/EntryId/153/Top-10-Estimation-best-practices-in-Agile.aspx</link>
      <comments>http://www.iotap.com/Blogs/tabid/277/EntryId/153/Top-10-Estimation-best-practices-in-Agile.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.iotap.com/Blogs/tabid/277/EntryId/153/Top-10-Estimation-best-practices-in-Agile.aspx</guid>
      <pubDate>Tue, 24 Nov 2009 07:17:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://web.iotap.com/DesktopModules/Blog/Trackback.aspx?id=153</trackback:ping>
    </item>
    <item>
      <title>Advantages &amp; Disadvantage of Prototyping process model</title>
      <description>&lt;div style="margin: 0in 0in 0pt"&gt;&lt;span style="color: black; font-size: 10pt"&gt;The Prototyping Model is a systems development method (SDM) in which a&lt;/span&gt; &lt;span style="color: black; font-size: 10pt"&gt;prototype&lt;/span&gt; &lt;span style="color: black; font-size: 10pt"&gt;(an early approximation of a final system or product) is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed. This model works best in scenarios where not all of the project requirements are known in detail ahead of time. It is an iterative, trial-and-error process that takes place between the developers and the users.&lt;/span&gt;&lt;/div&gt;&lt;a href=http://www.iotap.com/Blogs/tabid/277/EntryId/152/Advantages-Disadvantage-of-Prototyping-process-model.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.iotap.com/Blogs/tabid/277/EntryId/152/Advantages-Disadvantage-of-Prototyping-process-model.aspx</link>
      <comments>http://www.iotap.com/Blogs/tabid/277/EntryId/152/Advantages-Disadvantage-of-Prototyping-process-model.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.iotap.com/Blogs/tabid/277/EntryId/152/Advantages-Disadvantage-of-Prototyping-process-model.aspx</guid>
      <pubDate>Tue, 24 Nov 2009 07:13:00 GMT</pubDate>
      <slash:comments>1</slash:comments>
      <trackback:ping>http://web.iotap.com/DesktopModules/Blog/Trackback.aspx?id=152</trackback:ping>
    </item>
    <item>
      <title>Characteristics of a good software design </title>
      <description>&lt;p&gt;&lt;span style="font-family: "Calibri","sans-serif"; font-size: 13.5pt; mso-fareast-font-family: 'Times New Roman'; mso-bidi-font-family: 'Times New Roman'; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;The definition of “a good software design” can vary depending on the application being designed. For example, the memory size used by a program may be an important issue to characterize a good solution for embedded software development ..&lt;/span&gt;&lt;/p&gt;&lt;a href=http://www.iotap.com/Blogs/tabid/277/EntryId/151/Characteristics-of-a-good-software-design.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.iotap.com/Blogs/tabid/277/EntryId/151/Characteristics-of-a-good-software-design.aspx</link>
      <comments>http://www.iotap.com/Blogs/tabid/277/EntryId/151/Characteristics-of-a-good-software-design.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.iotap.com/Blogs/tabid/277/EntryId/151/Characteristics-of-a-good-software-design.aspx</guid>
      <pubDate>Tue, 24 Nov 2009 07:10:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://web.iotap.com/DesktopModules/Blog/Trackback.aspx?id=151</trackback:ping>
    </item>
    <item>
      <title>10 Requirements Traps to Avoid</title>
      <description>&lt;p&gt;&lt;span class="apple-style-span"&gt;&lt;span style="line-height: 115%; font-family: "Times","serif"; color: black; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"&gt;The path to quality software begins with excellent requirements. Slighting the processes of requirements development and management is a common cause of software project frustration and failure. &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;a href=http://www.iotap.com/Blogs/tabid/277/EntryId/150/10-Requirements-Traps-to-Avoid.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.iotap.com/Blogs/tabid/277/EntryId/150/10-Requirements-Traps-to-Avoid.aspx</link>
      <comments>http://www.iotap.com/Blogs/tabid/277/EntryId/150/10-Requirements-Traps-to-Avoid.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.iotap.com/Blogs/tabid/277/EntryId/150/10-Requirements-Traps-to-Avoid.aspx</guid>
      <pubDate>Tue, 24 Nov 2009 06:56:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://web.iotap.com/DesktopModules/Blog/Trackback.aspx?id=150</trackback:ping>
    </item>
    <item>
      <title>What is SRS (Software Requirements Specification)?</title>
      <description>&lt;div style="text-align: justify; line-height: 13.5pt; margin: 0in 0in 6pt"&gt;&lt;span style="font-size: 10.5pt"&gt;
&lt;div style="text-align: justify; line-height: 13.5pt; margin: 0in 0in 6pt"&gt;&lt;span style="color: black; font-size: 10.5pt"&gt;An SRS is basically an organization's understanding (in writing) or blueprint of a customer or client's system requirements and dependencies&lt;/span&gt; &lt;em&gt;&lt;span style="color: black; font-size: 10.5pt"&gt;at a particular point of time&lt;/span&gt;&lt;/em&gt; &lt;span style="color: black; font-size: 10.5pt"&gt;(usually) prior to any actual design or development work. It's a two-way document that assures that both the client and the organization understand the other's requirements from that perspective at a given point of time.&lt;/span&gt;&lt;/div&gt;
&lt;/span&gt;&lt;/div&gt;&lt;a href=http://www.iotap.com/Blogs/tabid/277/EntryId/149/What-is-SRS-Software-Requirements-Specification.aspx&gt;More...&lt;/a&gt;</description>
      <link>http://www.iotap.com/Blogs/tabid/277/EntryId/149/What-is-SRS-Software-Requirements-Specification.aspx</link>
      <comments>http://www.iotap.com/Blogs/tabid/277/EntryId/149/What-is-SRS-Software-Requirements-Specification.aspx#Comments</comments>
      <guid isPermaLink="true">http://www.iotap.com/Blogs/tabid/277/EntryId/149/What-is-SRS-Software-Requirements-Specification.aspx</guid>
      <pubDate>Tue, 24 Nov 2009 06:53:00 GMT</pubDate>
      <slash:comments>0</slash:comments>
      <trackback:ping>http://web.iotap.com/DesktopModules/Blog/Trackback.aspx?id=149</trackback:ping>
    </item>
  </channel>
</rss>