KGRKJGETMRETU895U-589TY5MIGM5JGB5SDFESFREWTGR54TY
Server : Apache/2.4.62
System : FreeBSD fbsdweb2.web.rcn.net 14.1-RELEASE FreeBSD 14.1-RELEASE releng/14.1-n267679-10e31f0946d8 GENERIC amd64
User : www ( 80)
PHP Version : 8.3.8
Disable Function : NONE
Directory :  /domains/srakitin/OLD/articles/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : /domains/srakitin/OLD/articles/role.html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>profession</title>
</head>
<body bgcolor="#FFFFFF">

<!--- Logo and Page Title -->

 <p align="center"> <img src="../gif/sqc.GIF" width="328" height="39"></p>

<center>
<table width=690>
<tr>
	<td width=20%>

	</td>

	<td width=60%>
	<font size=3 color=Red face="Comic Sans MS">
	<center>
	<P>Role of a Software Quality Assurance Group</font>
	</center></P>

	<font size=2 face="Comic Sans MS">
	<P>In working with dozens of companies, I've had the opportunity to see
	how different organizations view the role of Software Quality Assurance
	(SQA). At one end of the spectrum is the SQA Group that has both the
	authority and reputation for not letting anything out the door that isn't
	as close to perfect as possible - even though customers are willing to
	accept something less.
	<p>
	At the other end of the spectrun is the organization that uses its
	Technical Support Group as a surrogate SQA group. The support staff are
	responsible for testing the software prior to release but yet have not
	had the benefit of any training in how to test. As a result, many bugs
	slip through causing undue frustration for both customers and the
	Technical Support staff. And there are many variations between these two
	extremes.</P>

	<p>
	The one thing that these two extremes have in common though, is that in
	both groups, the staff is focused solely on testing. What we should have
	learned by now is that the sooner we find a problem, the easier and less
	expensive it is to fix. We should also know that inspections are much
	more effective at finding defects than testing. Organizations need to be
	performing inspections of requirements, designs, code, and tests
	throughout the development process in order to help find problems sooner
	rather than later. Clearly, this is an area where SQA can play an active
	role.

	<P>
	As a result of the lack of consistency in how SQA is performed,
	Software Quality professionals frequently find themselves faced with the
	dilemma of "How good is good enough and when should the product be
	released?" Frequently, requirements for quality are not specified and SQA
	may not be aware of what customers were promised or are willing to
	accept. As a result, SQA is often caught between rock and a hard
	place. Do we release a product with known defects or do we continue
	testing...</P>

	<P>In my opinion, it's not reasonable to put SQA in the position of
	making the release decision. I've found from years of experience, that
	SQA should provide information to Management so that <I>they</I> can make
	the release decision. Sometimes Management will agree with SQA, sometimes
	they won't - and that's perfectly reasonable. As professionals, SQA
	people need to recognize that this is a better role to play.</P>
	</FONT>
	</td>

	<td width=20%>
	
	</td>
</tr>
</table>
<br><br>
<table width=690>
<tr>
	<td width=33%>
	<center>
		<a href="../articles/summary.html">
		<img src="../gif/button3.JPG" width=30 height=15 border=0>
		<font size="2" face="Comic Sans MS">Articles</font></a></p>	
	</center>
	</td>

	<td width=33%>
	<center>
		<a href="../company/summary.html">
		<img src="../gif/button3.JPG" width=30 height=15 border=0>
		<font size="2" face="Comic Sans MS">Company</font></a></p>
	</center>
	</td>

	<td width=33%>
	<center>
		<a href="../index.html">
		<img src="../gif/button3.JPG" width=30 height=15 border=0>
		<font size="2" face="Comic Sans MS">Home</font></a></p>
	</center>
	</td>
</tr>
</table>

</center>
<br>
<hr>
<br>
<!--- logo --->
		<p align="center"><font size="4" face="PalmSprings"><em>
		To request a copy of any of these papers or presentations,
        please </em></font></p>
    	<p align="center"><font size="5" face="PalmSprings">
		<em>Contact</em></font></p>
   	 	<p align="center"><font size="5" face="PalmSprings"><em>
		<img src="../gif/sqc.GIF" width="328" height="39"></em></font></p>
    	<p align="center"><font size="4" face="PalmSprings"><b>Phone:</b>
    	508.529.4282</font></p>
		<p align="center"><font size="4" face="PalmSprings"><b>Fax:</b>
    	508.529.7799</font></p>
    	<p align="center"><font size="4" face="PalmSprings"><b>E-mail:</b>
    	</font><a href="mailto:[email protected]"><font size="4"
    	face="PalmSprings">[email protected]</font></a><font
    	size="4" face="PalmSprings"> </font></p>

<!-- Link back to Home page -->
		</font></p>
        <p align="center"><a href="../index.html"><font size="4"
        face="PalmSprings"><img src="../gif/home.GIF" border="0"
        width="82" height="121" "width="82"></font></a></p>
        <p align="center"><a href="../index.html"><font size="4"
        face="PalmSprings">Back Home</font></a></p>
        <p><font size="4" face="PalmSprings">

<!-- Copyright notice --> </font></p>
        <p align="left"><font size="2" face="PalmSprings">
		
		Copyright �2000 Software Quality Consulting</font></p>
        <p align="left"><font size="1" face="PalmSprings">
		May 2000</font></p>
    </li>
</ul>
</body>
</html>

Anon7 - 2021