<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>IT'S BROKEN - software development</title>
    <link>http://2wtx.com/itsbroken/</link>
    <description>Things in everyday life that annoy us</description>
    <dc:language>en</dc:language>
    <generator>Serendipity 1.4.1 - http://www.s9y.org/</generator>
    
    

<item>
    <title>Software development, QA and QC</title>
    <link>http://2wtx.com/itsbroken/archives/27-Software-development,-QA-and-QC.html</link>
            <category>software development</category>
    
    <comments>http://2wtx.com/itsbroken/archives/27-Software-development,-QA-and-QC.html#comments</comments>
    <wfw:comment>http://2wtx.com/itsbroken/wfwcomment.php?cid=27</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://2wtx.com/itsbroken/rss.php?version=2.0&amp;type=comments&amp;cid=27</wfw:commentRss>
    

    <author>nospam@example.com (Jeff Howell)</author>
    <content:encoded>
    &lt;!-- s9ymdb:23 --&gt;&lt;img class=&quot;serendipity_image_left&quot; width=&quot;80&quot; height=&quot;80&quot; style=&quot;float: left; border: 0px; padding-left: 5px; padding-right: 10px; margin-bottom: 10px;&quot; src=&quot;http://2wtx.com/itsbroken/uploads/jeff.png&quot; alt=&quot;&quot; /&gt;I’ve been working in software development for a while, but I’m still getting used to the usage of the term QA.  The activities of the software QA groups that I have seen are centered around proving, with some level of confidence, that a software &lt;em&gt;works&lt;/em&gt;, where works means &lt;em&gt;it-does-what-the-requirement-says-it-should-do&lt;/em&gt;.  &lt;br /&gt;
&lt;br /&gt;
While this is important, it does not embrace the more important aspects in my understanding of Quality Assurance. So here’s my take on defining QA &amp;amp; QC based on experience in Software &amp;amp; Hardware development as well as Manufacturing management and engineering:&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;QA -&lt;/strong&gt; Provides information to upper management regarding the likelihood that the marketplace will accept (buy) the product; and analyzes and improves the process that produce the products.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;QC -&lt;/strong&gt; Measures the outcomes of the process through testing and inspection and passes the results to QA for analysis.&lt;br /&gt;
&lt;br /&gt;
To give this some practical sense, consider a company which designs and manufactures bicycle sprockets.  At a high level the product life cycle follows a path like:&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://2wtx.com/itsbroken/archives/27-Software-development,-QA-and-QC.html#extended&quot;&gt;Continue reading &quot;Software development, QA and QC&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 20 Aug 2009 09:24:49 -0500</pubDate>
    <guid isPermaLink="false">http://2wtx.com/itsbroken/archives/27-guid.html</guid>
    
</item>

</channel>
</rss>