<?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"
	>

<channel>
	<title>Software Testing Interview Questions &#187; Metrics in Testing Tools</title>
	<atom:link href="http://www.bugtest.info/category/metrics-in-testing-tools/feed" rel="self" type="application/rss+xml" />
	<link>http://www.bugtest.info</link>
	<description>Software Testing Interview Question &#124; Test Director Interview question &#124; Load Runner interview questions &#124; QTP interview questions &#124; Silk Test Interview questions &#124; Win Runner  Interview questions &#124; Software Quality Assurance Interview Questions &#124; Automated Testing Interview Questions &#124; Manual Testing Interview Questions</description>
	<pubDate>Wed, 06 Aug 2008 18:53:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Metrics in Software Testing</title>
		<link>http://www.bugtest.info/metrics-in-software-testing/</link>
		<comments>http://www.bugtest.info/metrics-in-software-testing/#comments</comments>
		<pubDate>Fri, 10 Aug 2007 14:27:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
		
		<category><![CDATA[Foundation in Software Testing]]></category>

		<category><![CDATA[Metrics in Testing Tools]]></category>

		<guid isPermaLink="false">http://www.bugtest.info/2007/metrics-in-software-testing.html</guid>
		<description><![CDATA[1) Schedule variance = (Actual time taken - Planned time) / Planned time * 100
2) Effort variance = (Actual effort - Planned Effort)/Planned effort * 100
3) Defect unearthing efficiency = 100 * STRs found  in pass 1/ ( STRs found in pass 1 + STRs found  in pass 2 but existing in pass [...]]]></description>
			<content:encoded><![CDATA[<p>1) Schedule variance = (Actual time taken - Planned time) / Planned time * 100</p>
<p>2) Effort variance = (Actual effort - Planned Effort)/Planned effort * 100</p>
<p>3) Defect unearthing efficiency = 100 * STRs found  in pass 1/ ( STRs found in pass 1 + STRs found  in pass 2 but existing in pass 1)  = Defect unearthing efficiency for pass 1.<br />
Thus defect unearthing efficiency can be found for all passes.</p>
<p>Also defect unearthing efficiency in terms of field STRs could be found as follows:</p>
<p>= 100 * Total STRs found in Polaris for a release/ (Total STRs found in Polaris for a release + Field STRs for that release)</p>
<p>4) Test case efficiency = (Total STRs - STRs not mapped)/Total STRs * 100<br />
5) Test case coverage = (Total Test cases - STRs that cannot be mapped to test cases)/ Total Test Cases * 100</p>
<p>PRODUCTIVITY METRICS</p>
<p>1.	OUTPUT / INPUT OR VALUE OF MATERIAL / COST OF PRODUCTION</p>
<p>Eg: Non Commented Software Source (NCSS) Per Engineer Per Month<br />
	NCSS per Person Month<br />
	NCSS per Function Point<br />
	NCSS can also be replaced by KLOC (Kilo Lines of Code)</p>
<p>QUALITY METRICS</p>
<p>1.	DEFECTS PER KLOC<br />
2.	DEFECTS PER FUNCTION POINT<br />
3.	% OF MAINTENANCE / PROJECT EFFORT<br />
4.	POST RELEASE STABILITY<br />
5.	PREDELIVERY DEFECT REMOVAL EFFICIENCY<br />
6.	DELIVERED DEFECTS PER KLOC<br />
7.	(COST OF REWORK / TOTAL COST ) X 100</p>
<p>PROCESS IMPROVEMENT METRICS</p>
<p>1.	PROCESS IMPROVEMENT OR OVERALL EFFICIENCY = RETURN ON INVESTMENT<br />
2.	% OF RECYCYLED CODE<br />
3.	% OF CALENDER TIME / PHASE<br />
4.	INCREASED RETURNS / INCREASED COST<br />
5.	% OF DEFECTS IN PHASE OF THIS YEAR / % OF DEFECTS IN PHASE OF LAST YEAR<br />
6.	DIFFICULTY COMPLEXITY = McCABE  COMPLEXITY<br />
7.	TOTAL RECORDED PRE-DELIVERY DEFECTS / TOTAL FOUND DURING UAT<br />
8.	POST RELEASE DISCOVERED DEFECTS DENSITY OVER PERIOD</p>
<p>OTHERS</p>
<p>1.	TEST COMPLETION CRITERIA = NO. OF HOURS OF TEST WITHOUT BUGS<br />
2.	DEFECTS PER WEEK<br />
3.	% BRANCH COVERAGE BY TEST<br />
4.	MAINTAINABILITY = MEAN TIME TO CORRECT<br />
5.	INTEGRITY = Σ ( 1 – THREAT X (1 – SECURITY) )<br />
6.	USABILITY = NET INCREASE  IN PRODUCTION OVER EARLIER SYSTEM<br />
7.	CUSTOMER BEHAVIOR = VOLATALITY INDEX<br />
8.	CUSOMER BEHAVIOR = NO OF CHANGES IN REQUIREMENTS OVER A PERIOD<br />
9.	PRODUCTIVITY =   $ PER KLOC<br />
                                  KLOC PER MONTH<br />
                                  MONTHS PER KLOC</p>
<p>10.	DOCUMENTATION = PAGES PER KLOC  PAGES PER PERSOM MONTHS  $ PER PAGE<br />
11.	QUALITY = ERRORS PER KLOC  $ PER ERROR<br />
12.	FUNCTIONALITY = FUNCTION POINT PER PROGRAM, FUNCTION POINT PER KLOC MAINTAINED<br />
13.	CUSTOMER SATISFACTION = NO. OF COMPLAINTS / PERIOD OF TIME<br />
     1 / NO. OF COMPLAINTS</p>
<p>PREVENTIVE CONTROLS</p>
<p>Controls that are designed to prevent an error, omission  or malicious act from occurring.</p>
<p>1.	DATA DICTIONARY<br />
2.	STRUCTURED TECHNIQUES<br />
3.	PROGRAMMING STANDARDS<br />
4.	DOCUMENTATION STANDARDS<br />
5.	PROCESSING PARAMETERS<br />
6.	ON-LINE PROMPTING<br />
7.	SELF-HELP FEATURES<br />
8.	DEFAULT OPTIONS<br />
9.	GOOD SCREEN DESIGN<br />
10.	FIELD HIGHLIGHTS<br />
11.	SCREEN DIAGNOSTIC MESSAGES<br />
12.	PRE NUMBERED FORMS<br />
13.	SYSTEM ASSIGNED NUMBERS<br />
14.	PRE-CODED FORMS / SCREENS<br />
15.	TURN AROUND DOCUMENTS<br />
16.	DATA OWNERSHIP<br />
17.	DATA CLASSIFICATION<br />
18.	REFERENCE VALUES OR CODE KEPT OUTSIDE THE PROGRAM<br />
19.	PASSWORDS TO FUNCTIONS<br />
20.	TRANSACTION CANCELLATION<br />
21.	DATA ENCRYPTION<br />
22.	MANAGEMENT APPROVALS<br />
23.	CONCURRENT ACCESS CONTROLS</p>
<p>DEFECTIVE CONTROLS </p>
<p>Controls that reflect that an error, omission or malicious act has occurred, and reports the occurrence.<br />
	Access Violation Log</p>
<p>1.	BATCH CONTROL TOTALS<br />
2.	HASH TOTALS<br />
3.	LIMIT CHECKS<br />
4.	REASONABLENESS TEST<br />
5.	CHECK DIGITS<br />
6.	OVERFLOW CHECKS<br />
7.	FORMAT CHECKS<br />
8.	DATA CHECKS<br />
9.	LABEL CHECKS<br />
10.	COMPLETENESS TESTS<br />
11.	RANGE TESTS<br />
12.	RECORD COUNTS<br />
13.	SIGN TEST<br />
14.	SIZE TEST<br />
15.	SEQUENTIAL CHECKS<br />
16.	DUPLICATION CHECKS<br />
17.	CROSS RECORD EDITING<br />
18.	SYSTEM MATCHING<br />
19.	FIELD COMBINATION TEST<br />
20.	VALIDITY CHECKS<br />
21.	RUN-TO-RUN TOTALS<br />
22.	SUSPENSE FILES<br />
23.	HEAD AND TRAILER RECORD VERIFICATION<br />
24.	BALANCE CONTROL<br />
25.	SYSTEM LOGGING OF TRANSACTIONS (LOG OFF)</p>
<p>COMPARISON TOTALS</p>
<p>1.	COMPUTATION CONTROLS<br />
2.	RATIO TEST<br />
3.	ROUNDING TECHNIQUE<br />
4.	DESCRIPTIVE READ BACK<br />
5.	SYSTEM WALKTHROUGH<br />
6.	DATA CHECK<br />
7.	KEY VERIFICATION<br />
8.	ONE FOR ONE CHECK (MANUAL)</p>
<p>CORRECTION CONTROL</p>
<p>Controls that correct errors, omissions, or malicious acts one they are detected in future date.</p>
<p>1.	PROGRAM COMMENTS<br />
2.	JOB CONTROL COMMENTS<br />
3.	AUTOMATIC ERROR CORRECTIONS<br />
4.	OVERRIDE BY SUPERVISOR<br />
5.	AUDIT TRAIL REPORTS<br />
6.	CONTROL REPORTS<br />
7.	EXCEPTION REPORTS<br />
8.	PRODUCTIVITY REPORTS<br />
9.	AGING REPORTS<br />
10.	ERROR REPORTS<br />
11.	BEFORE / AFTER IMAGE RECORD REPORTING FOR FILE MAINTENANCE<br />
12.	ERROR TOTALS<br />
13.	DOCUMENTATION</p>
<p>RECOVERY CONTROLS</p>
<p>1.	AUTOMATIC BACKUP AND RECOVERY<br />
2.	JOURNALIZING<br />
3.	DATA RETENTION YEARS<br />
4.	CHECK POINT CONTROLS<br />
5.	TRANSACTION BACK OUT<br />
6.	RECOVERY LOGGING<br />
7.	FALL BACK PROCEDURE</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bugtest.info/metrics-in-software-testing/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
