
<?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>QA Evangelist &#187; SQA &#8211; Advice Center</title>
	<atom:link href="http://blog.qaevangelist.com/?feed=rss2&#038;cat=7" rel="self" type="application/rss+xml" />
	<link>http://blog.qaevangelist.com</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Thu, 29 Jul 2010 14:55:06 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Brief Introduction of Perl</title>
		<link>http://blog.qaevangelist.com/?p=263</link>
		<comments>http://blog.qaevangelist.com/?p=263#comments</comments>
		<pubDate>Thu, 29 Jul 2010 14:55:06 +0000</pubDate>
		<dc:creator>Tim Hsueh</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=263</guid>
		<description><![CDATA[In this blog, one of the most used web languages Perl will be discussed in detail including the features, code samples and the well known companies who are using it.

Perl


Perl is a high-level, general-purpose, interpreted, dynamic programming language. Perl was originally developed by Larry Wall in 1987 as a general-purpose Unix scripting language to make [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=263</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clash of the Titans</title>
		<link>http://blog.qaevangelist.com/?p=240</link>
		<comments>http://blog.qaevangelist.com/?p=240#comments</comments>
		<pubDate>Wed, 07 Jul 2010 18:56:53 +0000</pubDate>
		<dc:creator>Eric Ocequeda</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<category><![CDATA[advice]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=240</guid>
		<description><![CDATA[Now most of you know that programmers and QA tester do not get along too well. Programmers believe QA is under minding them, while QA believes that programmers are a bunch of prima donnas that will give more then they take. I am here to sort of mend broken bridges, in a ways to improve [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=240</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>5 Common Problems with Software Development Process and Solutions</title>
		<link>http://blog.qaevangelist.com/?p=183</link>
		<comments>http://blog.qaevangelist.com/?p=183#comments</comments>
		<pubDate>Fri, 07 May 2010 22:14:48 +0000</pubDate>
		<dc:creator>JeremyM</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=183</guid>
		<description><![CDATA[ What are 5 common problems in the software development process? 

poor requirements &#8211; if requirements are unclear, incomplete,  too general, and not testable, there may be problems.


unrealistic schedule &#8211; if too much work is crammed in too little   time, problems are inevitable.


inadequate testing &#8211; no one will know whether or not [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=183</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What kinds of testing should be considered?</title>
		<link>http://blog.qaevangelist.com/?p=178</link>
		<comments>http://blog.qaevangelist.com/?p=178#comments</comments>
		<pubDate>Fri, 07 May 2010 22:10:15 +0000</pubDate>
		<dc:creator>JeremyM</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=178</guid>
		<description><![CDATA[
Black box testing
- not based on any knowledge of internal design  or code.  Tests are based on requirements and functionality.


White box testing
- based on knowledge of the internal logic  of an application&#8217;s code.  Tests are based on coverage of code  statements, branches, paths, conditions.


Unit testing
- the most &#8216;micro&#8217; scale of [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=178</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How can new Software QA processes be introduced in an existing organization?</title>
		<link>http://blog.qaevangelist.com/?p=175</link>
		<comments>http://blog.qaevangelist.com/?p=175#comments</comments>
		<pubDate>Fri, 07 May 2010 22:03:16 +0000</pubDate>
		<dc:creator>JeremyM</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<category><![CDATA[SQA - How to...]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=175</guid>
		<description><![CDATA[A lot depends on the size of the organization and the risks involved.

For large organizations with high-risk (in terms of lives or property)  projects, serious management buy-in is required and a formalized QA process is necessary.


Where the risk is lower, management and organizational buy-in and QA implementation may be a slower, step-at-a-time process.  [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=175</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Software Engineering Methods, Standards and Tools</title>
		<link>http://blog.qaevangelist.com/?p=31</link>
		<comments>http://blog.qaevangelist.com/?p=31#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:10:09 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=31</guid>
		<description><![CDATA[SQA methods, standards and tools are a strict subset of 										software engineering methods, standards and tools. There are 										no unique SQA methods. Simply, SQA is interested in the 										enforcement of methods, standards and tools that contribute 										to product quality. Certain hardware reliability methods 										such as redundant fault tolerant software or fault tree 										analysis of critical [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=31</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Roles of a SQA Person</title>
		<link>http://blog.qaevangelist.com/?p=29</link>
		<comments>http://blog.qaevangelist.com/?p=29#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:09:20 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=29</guid>
		<description><![CDATA[Fletcher Buckley [7] gives three roles for a SQA person: 										Information-Gatherer, Policeman and Helper. The 										Information-Gatherer role can covered by the minimal 										conformance and audit profiles. The same @applies to the 										Policeman role. The SQA role as helper or even as advisor is 										rejected by the author. Helping and giving advice are the 										responsibility of [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=29</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Contractual, Legislative and Liability Aspects</title>
		<link>http://blog.qaevangelist.com/?p=27</link>
		<comments>http://blog.qaevangelist.com/?p=27#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:08:22 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=27</guid>
		<description><![CDATA[SQA is by definition responsible for product conformance to 										REQUIREMENTS. SQA cannot undertake such a responsibility 										unless it participates in the contractual phase. SQA has to 										approve both cost and technical proposals in the request for 										proposal phase. SQA approval of the cost proposal is 										important to ensure that SQA is properly budgeted to uphold [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=27</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQA and Software Configuration Management</title>
		<link>http://blog.qaevangelist.com/?p=25</link>
		<comments>http://blog.qaevangelist.com/?p=25#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:06:57 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=25</guid>
		<description><![CDATA[SQA must function in an identified and controlled software 										engineering process. Both ANSI/IEEE Std 730-1984 and 										MIL-S-52779A require SQA to ascertain that SCM plan complies 										to certain standards, but do not require SQA to write the 										SCM plan. In the author&#8217;s opinion SQA shall be responsible 										for the SCM auditing function and SQA shall participate [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=25</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQA TASK PROFILES</title>
		<link>http://blog.qaevangelist.com/?p=21</link>
		<comments>http://blog.qaevangelist.com/?p=21#comments</comments>
		<pubDate>Wed, 31 Dec 2008 22:04:18 +0000</pubDate>
		<dc:creator>author</dc:creator>
				<category><![CDATA[SQA - Advice Center]]></category>
		<guid isPermaLink="false">http://blog.qaevangelist.com/?p=21</guid>
		<description><![CDATA[SQA Definition: A planned and systematic pattern of all 										actions necessary to provide adequate confidence that the 										item or product conforms to established technical 										REQUIREMENTS. (ANSI/IEEE Std 730-1984)
The SQA task definition leads to three possible task 										profiles: 										1 &#8211; Minimal Conformance Profile top 										SQA task is limited to verifying the conformance of 										deliverable items to [...]]]></description>
		<wfw:commentRss>http://blog.qaevangelist.com/?feed=rss2&amp;p=21</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
