<?xml version='1.0' encoding='UTF-8'?><rss xmlns:atom='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0' version='2.0'><channel><atom:id>tag:blogger.com,1999:blog-9119679600526036070</atom:id><lastBuildDate>Fri, 27 Jan 2012 11:12:43 +0000</lastBuildDate><category>high severity</category><category>features not be tested</category><category>test coverage</category><category>improve</category><category>Visual SourceSafe</category><category>Identifier</category><category>development creteria</category><category>tools</category><category>Appraisel cost</category><category>bugs</category><category>integration test paln</category><category>measurement</category><category>actual measure</category><category>ethods</category><category>QC</category><category>measure</category><category>ensure</category><category>branching and merging</category><category>deliverables</category><category>Expose errors</category><category>Interpretation</category><category>Repeatable</category><category>Integrity</category><category>Testing</category><category>signed off</category><category>First time testing</category><category>goodness</category><category>BD</category><category>Operations</category><category>sane</category><category>resuability</category><category>Rational ClearcaseTortoise SVN Subversion</category><category>scenario</category><category>reliability</category><category>staffing</category><category>Rational Clearcase</category><category>unit test plan</category><category>EA</category><category>set of tasks</category><category>training</category><category>data collection</category><category>SCM</category><category>system</category><category>section</category><category>dimensions</category><category>IEEE</category><category>Time and Effort PPM</category><category>Cost</category><category>effective mechanism</category><category>Implementation</category><category>Subversion</category><category>schedule</category><category>walkthrough</category><category>Value</category><category>volume</category><category>Business Logic</category><category>adhoc testing</category><category>Trancendent</category><category>Tracking</category><category>test design</category><category>record</category><category>Reduced Cost of Development</category><category>pass</category><category>testing strategy</category><category>Interfaces</category><category>business objective</category><category>Sqa plan</category><category>compatibility</category><category>white box testing</category><category>scope of testing</category><category>Prevent Defects</category><category>Test Log</category><category>check point</category><category>design</category><category>release criteria</category><category>elegance</category><category>Software Quality</category><category>Item</category><category>inspection</category><category>system test plan</category><category>project</category><category>Testing PPM</category><category>Sequence</category><category>program cope</category><category>Project Summary</category><category>metric collection</category><category>activity</category><category>support</category><category>business goals</category><category>Consistent</category><category>metrics and measurement</category><category>test plan</category><category>flexibility</category><category>state transition diagram</category><category>turn over</category><category>Difference V and V</category><category>ISO</category><category>functional  specifications</category><category>efficiency</category><category>Replication</category><category>Simple</category><category>solutions</category><category>length</category><category>scenario based testing</category><category>test case types</category><category>testing team</category><category>subsystem</category><category>results</category><category>manipulate</category><category>implicit requirements</category><category>Functional</category><category>Purpose of SQA</category><category>quality providing reviews</category><category>previous path</category><category>temporary suspension</category><category>schedule pressure</category><category>effort to execute</category><category>Achieve</category><category>Crosby</category><category>retain customers</category><category>minor</category><category>Quality in Past</category><category>eRMS</category><category>lack of conformance</category><category>insufficient defect removal</category><category>SEG</category><category>hardware</category><category>PVCS</category><category>Quality Assurance</category><category>fault types</category><category>test planning</category><category>accuracy SQA</category><category>review worth</category><category>smoke testing</category><category>counter affects</category><category>completeness</category><category>flawed test cases</category><category>Sanity Testing</category><category>QE</category><category>External failure</category><category>size</category><category>line function</category><category>defect identify</category><category>quality audit</category><category>predict</category><category>Testing Tasks</category><category>Component</category><category>quantitative</category><category>Improved Customer Satisfaction</category><category>current path</category><category>employee esitmation index</category><category>helpdesk</category><category>fault</category><category>contents</category><category>Cost of quality</category><category>regression testing</category><category>structured testing</category><category>test  documents</category><category>Authentication</category><category>Configuration identification</category><category>Track</category><category>Configuration contro</category><category>specifcation  based testing</category><category>SQA</category><category>Reliable</category><category>master</category><category>suspension creteria</category><category>Tested</category><category>Root Cause Analysis</category><category>exploratory testing</category><category>Software Engineering Methods</category><category>ambigous requirements</category><category>Microsoft Visual SourceSafe</category><category>state machine</category><category>relationship</category><category>Functionality</category><category>ripple affects</category><category>Standards</category><category>Efforts expended</category><category>fitness for use</category><category>explicit requirements</category><category>test deliverable</category><category>find defects</category><category>conditions</category><category>Procedures</category><category>methodology</category><category>interoperabilty</category><category>Test Summary Report</category><category>compititive issue</category><category>features to be test</category><category>test environment</category><category>Managing changes</category><category>validation</category><category>Quality</category><category>medium</category><category>test</category><category>One time testing</category><category>decision</category><category>statistical analysis</category><category>Test Incident Report</category><category>defect reports</category><category>progammable</category><category>test procedure specifications</category><category>metric</category><category>Tester</category><category>performance</category><category>maintainability</category><category>System testing</category><category>Look</category><category>Creteria</category><category>main cause categories</category><category>execution time</category><category>review</category><category>Testing effort</category><category>Usability Testing</category><category>Failure cost</category><category>changes</category><category>SCM Management</category><category>reporting</category><category>Fast</category><category>out put dependent</category><category>story</category><category>replicate</category><category>estimate</category><category>units</category><category>abstract</category><category>prevention cost</category><category>test execution</category><category>statistic</category><category>identify task</category><category>verification</category><category>market strength</category><category>QA</category><category>Item Fail</category><category>transition</category><category>critical</category><category>automated test</category><category>defined interval</category><category>scope</category><category>Juran</category><category>Quality in present</category><category>measurement. principles</category><category>cost effective</category><category>PPM</category><category>Feel</category><category>Item pass</category><category>severities</category><category>state</category><category>Staff function</category><category>identify tests</category><category>Requirements</category><category>specifcation</category><category>Source code</category><category>resume</category><category>defect test cases</category><category>Development</category><category>portability</category><category>test items</category><category>computable</category><category>plan</category><category>estimation accuracy</category><category>experienced based</category><category>Analysis Reports</category><category>Product</category><category>testability</category><category>resumption requirements</category><category>Effort Estimation Model</category><category>Process</category><category>conformance</category><category>components</category><category>suspend</category><category>automation</category><category>inadequate training</category><category>enhance quality</category><category>PA</category><category>profitable organization</category><category>test approach</category><category>correctness</category><category>standard documentation</category><category>adhoc</category><category>Activities</category><category>Internal failure</category><category>testing types</category><category>Usability</category><category>test case</category><category>review activity</category><category>Formulation</category><category>documents</category><category>revisions</category><category>Logical</category><category>Monitor</category><category>load</category><category>priority feature</category><category>Authorization</category><category>Field Validation</category><category>Security</category><category>Important areas</category><category>ESI</category><category>User</category><category>Proactive</category><category>Release Management PPM</category><category>estimated</category><category>types</category><category>inputs</category><category>Test Case Specification</category><category>Requirements List</category><category>hypothetical situation</category><category>error guessing</category><category>approach</category><category>feedback</category><category>decision table</category><category>metrics</category><category>analysis</category><category>issues</category><category>high complexity</category><category>Software Engineering work</category><category>Planning</category><category>Programming language independent</category><category>software solutions</category><category>defect prevention</category><category>reactive</category><category>Software</category><category>what stage</category><category>Severity</category><category>testing proces</category><category>fatal</category><category>ad hoc</category><category>Reviews</category><category>Defect Estimation Model</category><category>Quality levels</category><category>User manuals</category><category>acceptance</category><category>organization metrics files</category><category>releases</category><category>steps</category><category>Basic needs</category><category>problamatic situations</category><category>database level</category><category>bad fixes</category><category>Recoverability</category><category>high risk</category><category>major</category><category>configuration management</category><category>Confidentiality</category><category>order qualifiers. order winners</category><category>items</category><category>FS</category><category>risk and contengecies</category><category>Intersolv PVCS Version Manager</category><category>tests</category><category>Reduced Cost of Maintenance</category><category>Application level</category><category>peer reviews</category><category>TPPM</category><category>SRS</category><category>test case size</category><category>phases</category><category>serious litigation</category><category>model</category><category>out puts</category><category>software testing</category><category>Programming knowledge</category><category>VV</category><category>estimation</category><category>SFS</category><title>SQA ,Software Quality Assurance,Software Testing and SQA interview Questions and Answers</title><description>Its all about Software Quality Assurance(SQA),  Testing Types, Testing Methods,Testing Levels, Test Cases, Test Planning, SQA planning,Reviews,Walk Throughs ,SQA Interview questions and answers, ISO Standards, Software Testing Strategies, Testing Approaches,  Metrics and Measurement, Automated Testing,Software Configuration Management,SCM, FAQs</description><link>http://s-qa.blogspot.com/</link><managingEditor>noreply@blogger.com (Hafeez)</managingEditor><generator>Blogger</generator><openSearch:totalResults>189</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-8347731535011912212</guid><pubDate>Sat, 20 Aug 2011 20:12:00 +0000</pubDate><atom:updated>2011-08-20T13:12:59.484-07:00</atom:updated><title>What is SQA Process or SQA Process Steps?</title><atom:summary type='text'>These are nine steps of SQA processInitiate SQA Process
Planning
Tracking
Training
Reviews
Issue Resolution
Testing
Audit
Process Improvement 
</atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-process-or-sqa-process.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-4041401236130994843</guid><pubDate>Sat, 20 Aug 2011 20:11:00 +0000</pubDate><atom:updated>2011-08-20T13:11:09.150-07:00</atom:updated><title>What is SQA Process's 9th step and Process Improvement?</title><atom:summary type='text'>Process ImprovementCritical function of SQA is Process Improvement.
This sub-process includes research and development need of SQA which results into improved processes, checklist and guidelines.
Personals Involved at this stage are:
QA Manager
QA Engineers
Quality Engineering
Tasks perform at this stage are:
SQA periodically review Software process and improvement activities.
QAE / Dev / </atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-9th-step-and.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-3648017618021727842</guid><pubDate>Sat, 20 Aug 2011 20:09:00 +0000</pubDate><atom:updated>2011-08-20T13:09:24.831-07:00</atom:updated><title>What is SQA Process's 8th step and Audit?</title><atom:summary type='text'>AuditThe sub-process is a fundamental quality assurance technique. 
Audit will be conducted for all software engineering activities to verify compliance against:
Standards
Processes
Procedures
Conformance of development processes to procedures and conformance of product to standards.
Also examines conformance of actual status to reported status.
AUDIT TYPES
Organizational based audits (</atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-8th-step-and-audit.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-2446997545964112380</guid><pubDate>Sat, 20 Aug 2011 20:07:00 +0000</pubDate><atom:updated>2011-08-20T13:07:57.749-07:00</atom:updated><title>What is SQA Process's 7th step and Software Testing?</title><atom:summary type='text'>Software TestingSQA assures that formal software testing is done in accordance with plans and procedures. 
SQA reviews testing documentation for completeness and adherence to standards.
By test monitoring, SQA assures software completeness and readiness for delivery by executing shipment assurance testing.

Personals Involved at this stage are:QA Manager
QA Engineers
Project Manager
Project </atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-7th-step-and.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-3157036985403030665</guid><pubDate>Sat, 20 Aug 2011 20:06:00 +0000</pubDate><atom:updated>2011-08-20T13:06:27.594-07:00</atom:updated><title>What is SQA Process's 6th step and Issue Resolution?</title><atom:summary type='text'>Issue ResolutionThe sub process will help to resolve issues  that can come across while performing SQA activities; these issues will  be escalated or resolved.

Is nonconformity or a deviation against standards, resolution of which  cannot be agreed upon between SQA team and affected group while  performing different SQA activities like Planning, Reviews, Audits and  Testing.
Personals Involved </atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-6th-step-and-issue.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-3156759042973023812</guid><pubDate>Sat, 20 Aug 2011 20:05:00 +0000</pubDate><atom:updated>2011-08-20T13:05:11.688-07:00</atom:updated><title>What is SQA Process's 5th step and Reviews?</title><atom:summary type='text'>ReviewsThe sub-process performs Peer reviews and Reviews at the project-level.
Peer Reviews will be performed for software related work products i.e. (SQA Plan, Test Plan, Test Cases and Code (Optional)). 
The objective of peer reviews is to remove defects from the products  early and efficiently. The results of the peer review are recorded and  passed on to the author or person responsible for </atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-5th-step-and.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-803326406098678648</guid><pubDate>Sat, 20 Aug 2011 20:03:00 +0000</pubDate><atom:updated>2011-08-20T13:03:59.893-07:00</atom:updated><title>What is SQA Process's 4th step and Training?</title><atom:summary type='text'>TrainingThis sub-process includes Project specific and QA specific training. 

Project specific training can be an orientation / training of a specific design tool for a specific project. 
QA specific training can be an introduction to expertise that is required to perform activities beyond the existing skill set.

Tasks Perform at this stage are:
Request for Training is placed or training </atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-4th-step-and.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-2916826569230329435</guid><pubDate>Sat, 20 Aug 2011 20:02:00 +0000</pubDate><atom:updated>2011-08-20T13:02:27.326-07:00</atom:updated><title>What is SQA Process's Third Step  and Tracking?</title><atom:summary type='text'>Tracking 
This sub-process is used to track deviations and monitor progress  against different plans, which can result into updating the timelines,  reassignment of tasks.

Tasks Perform at this stage are:Tracking activities for SQA and Test Plan.
Progress Review Meeting is conducted.
Progress Review Report is prepared and stored in VSS.
If status meeting is postponed then give reason.
</atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-third-step-and.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-4996704498772210078</guid><pubDate>Sat, 20 Aug 2011 20:01:00 +0000</pubDate><atom:updated>2011-08-20T13:01:07.175-07:00</atom:updated><title>What is SQA Process's Second step and SQA Planning?</title><atom:summary type='text'>PlanningThe sub-process enables planning for SQA activities. 
SQA group selects the activities for which to develop Plan(s),  according to project and departmental needs. 
Is made at the initial stage of SDLC
Define an organization, task and responsibilities within SQA process
 Following Tasks will be performed at this stage
Estimation of SQA activities will be done by the SQA Team.
The cost</atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-second-step-and.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-5746459675201196649</guid><pubDate>Sat, 20 Aug 2011 19:56:00 +0000</pubDate><atom:updated>2011-08-20T13:16:32.418-07:00</atom:updated><title>What is SQA Process's First Step or intiate SQA process?</title><atom:summary type='text'>Initiate SQA Process

QA manager to initiate SQA process for a project, once a P&amp;C is signed off and a formal request is received from Director IT.

This sub process covers the initiation of SQA process for complete SDLC. An estimation file is made to estimate SQA resources.

Following Tasks will be performed at this stage

Director IT will send a formal request to QA Manager through email for </atom:summary><link>http://s-qa.blogspot.com/2011/08/what-is-sqa-processs-first-step-or.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-2806982818139277232</guid><pubDate>Sun, 01 Aug 2010 14:30:00 +0000</pubDate><atom:updated>2010-08-01T07:30:29.626-07:00</atom:updated><title>What-is-SQA-process-(softwae-quality-assurance-process)-and-what-are-SQA-process-activites-or-what-do-you-know-about-SQA-process-and-what-are-main-activites-of-SQA-prcoes-why-sqa-process-is-used?</title><atom:summary type='text'>SQA Process:Process for providing adequate assurance that the software products and processes in the project life cycle conform to their specified requirements and adhere to their established plans

Why SQA Process:

There are reasons that sqa process
Provides management with appropriate visibility into the process being used and the products being built.
Verifies compliance with project </atom:summary><link>http://s-qa.blogspot.com/2010/08/what-is-sqa-process-softwae-quality.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>2</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-5670919607874695972</guid><pubDate>Mon, 15 Jun 2009 10:13:00 +0000</pubDate><atom:updated>2010-05-01T03:37:04.193-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Usability</category><category domain='http://www.blogger.com/atom/ns#'>adhoc</category><category domain='http://www.blogger.com/atom/ns#'>One time testing</category><title>Which test case should  not be automated?</title><atom:summary type='text'>These types of test cases should not be automated

One Time testing. (Non Repeatable)
Ad-hoc Testing (As soon As possible results required)
Usability Testing.
</atom:summary><link>http://s-qa.blogspot.com/2009/06/which-test-case-should-not-be-automated.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>2</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-3642927649083222581</guid><pubDate>Mon, 15 Jun 2009 10:12:00 +0000</pubDate><atom:updated>2010-05-01T03:43:22.828-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>performance</category><category domain='http://www.blogger.com/atom/ns#'>critical</category><category domain='http://www.blogger.com/atom/ns#'>automated test</category><title>Which test case should be automated?</title><atom:summary type='text'>Following test case should be automated
Test case need to be run for every build of the application 
(Sanity Testing)

Test that use multiple data values for the same actions. 
(Data Driven Testing)

Critical Application functionality.
Business functionality which won’t be change in short time period.
Performance testing 
(Load &amp; Stress)

</atom:summary><link>http://s-qa.blogspot.com/2009/06/which-test-case-should-be-automated.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-1933685932573184466</guid><pubDate>Mon, 15 Jun 2009 10:07:00 +0000</pubDate><atom:updated>2010-06-29T13:53:56.869-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Usability Testing</category><category domain='http://www.blogger.com/atom/ns#'>Cost</category><category domain='http://www.blogger.com/atom/ns#'>Programming knowledge</category><title>What are disadvantages of automated testing tools?</title><atom:summary type='text'>Automated tools have following disadvantages. 

Usability Testing:
Usability of software can not be automated so automated tools cannot rate the usability of an application.

Cost:

 Usually these are licensed so automated tools are quite expensive

Programming knowledge required:
 To customize test scripts according to test requirement.
Test maintenance is costly: In case of playback methods.
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-are-disadvatges-of-auutomated.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-5245100773032312646</guid><pubDate>Mon, 15 Jun 2009 10:05:00 +0000</pubDate><atom:updated>2010-06-29T13:56:23.907-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>progammable</category><category domain='http://www.blogger.com/atom/ns#'>Fast</category><category domain='http://www.blogger.com/atom/ns#'>Repeatable</category><category domain='http://www.blogger.com/atom/ns#'>Reliable</category><category domain='http://www.blogger.com/atom/ns#'>resuability</category><title>What-are-benefits-or-advantages-of-automated-testing?</title><atom:summary type='text'> Following are the benefits for using automated tools

Fast: Human be slow but Automated Testing Tool runs tests significantly faster than human users.

Reliable: Tests perform precisely the same operations each time they are run, thereby eliminating human error.

Repeatable: You can test how the software reacts under repeated execution of the same operations.

Programmable: You can program </atom:summary><link>http://s-qa.blogspot.com/2009/06/what-are-benefits-of-automated-testing.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-7938685770105794458</guid><pubDate>Mon, 15 Jun 2009 09:57:00 +0000</pubDate><atom:updated>2010-06-29T13:59:57.646-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>PA</category><category domain='http://www.blogger.com/atom/ns#'>main cause categories</category><category domain='http://www.blogger.com/atom/ns#'>solutions</category><category domain='http://www.blogger.com/atom/ns#'>Root Cause Analysis</category><title>How-is-Statistical-Analysis-is-in-TPPM-Activity?</title><atom:summary type='text'>Statistical AnalysisPerform Problem Root Cause Analysis.
Mention root cause from different main cause categories
Identify different solution
Select best solution
Mention C&amp;PA to avoid problem in future
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-are-statistical-analysis-in-tppm.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-5599054997571361774</guid><pubDate>Mon, 15 Jun 2009 09:56:00 +0000</pubDate><atom:updated>2010-06-30T11:34:23.442-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>Efforts expended</category><category domain='http://www.blogger.com/atom/ns#'>defect identify</category><category domain='http://www.blogger.com/atom/ns#'>size</category><title>How-is-Actual-Measurements-Entry- in-TPPM-Activity?</title><atom:summary type='text'>Take measurement of following attributes/Variables and enter in Testing PPM
Actual size of code (LOC/AFPs)
Actual Defects Identified by each test case
Actual efforts expended to execute each test case
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-are-actual-measurements-entry-in.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-7939839114410218257</guid><pubDate>Mon, 15 Jun 2009 09:54:00 +0000</pubDate><atom:updated>2010-06-30T11:37:59.561-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>TPPM</category><category domain='http://www.blogger.com/atom/ns#'>test case size</category><category domain='http://www.blogger.com/atom/ns#'>effort to execute</category><category domain='http://www.blogger.com/atom/ns#'>activity</category><category domain='http://www.blogger.com/atom/ns#'>estimation</category><category domain='http://www.blogger.com/atom/ns#'>length</category><category domain='http://www.blogger.com/atom/ns#'>defect test cases</category><category domain='http://www.blogger.com/atom/ns#'>estimated</category><category domain='http://www.blogger.com/atom/ns#'>estimate</category><title>How-estimation-in-TPPM-(-testing-process-performance-model- activity?</title><atom:summary type='text'>In testing PPM first of all estimate following things step by step
Size of each Test Case (over all size and lenght of the every  test case is estimated)
Defects of each Test Case(defects of the test cases are estimated)
Efforts to execute each test case (Efforts are also are part of the estimates)
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-are-estimation-in-tppm.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-3950373456412951071</guid><pubDate>Mon, 15 Jun 2009 09:52:00 +0000</pubDate><atom:updated>2010-06-30T11:48:21.868-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>TPPM</category><category domain='http://www.blogger.com/atom/ns#'>performance</category><category domain='http://www.blogger.com/atom/ns#'>statistical analysis</category><category domain='http://www.blogger.com/atom/ns#'>metrics and measurement</category><category domain='http://www.blogger.com/atom/ns#'>statistic</category><category domain='http://www.blogger.com/atom/ns#'>activity</category><category domain='http://www.blogger.com/atom/ns#'>actual measure</category><category domain='http://www.blogger.com/atom/ns#'>model</category><category domain='http://www.blogger.com/atom/ns#'>estimation</category><category domain='http://www.blogger.com/atom/ns#'>estimated</category><category domain='http://www.blogger.com/atom/ns#'>Process</category><category domain='http://www.blogger.com/atom/ns#'>estimate</category><title>What-is-Testing-Process-Performance-Model-(TPPM)-activity?</title><atom:summary type='text'>Testing PPM activityTesting PPM activity can be logically divided into following Sub-Activities.

Estimations-here estimations are done
Actual Measurement Entry - here we come with actual measures
Statistical Analysis - we are doing analysis for the estimations and measure in this activity
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-is-testing-ppm-activity.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-3997684090706198094</guid><pubDate>Mon, 15 Jun 2009 09:48:00 +0000</pubDate><atom:updated>2010-06-30T11:41:20.690-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>TPPM</category><category domain='http://www.blogger.com/atom/ns#'>Sequence</category><category domain='http://www.blogger.com/atom/ns#'>execution time</category><category domain='http://www.blogger.com/atom/ns#'>PPM</category><category domain='http://www.blogger.com/atom/ns#'>Product</category><category domain='http://www.blogger.com/atom/ns#'>estimation</category><category domain='http://www.blogger.com/atom/ns#'>releases</category><category domain='http://www.blogger.com/atom/ns#'>defined interval</category><category domain='http://www.blogger.com/atom/ns#'>project</category><category domain='http://www.blogger.com/atom/ns#'>Process</category><category domain='http://www.blogger.com/atom/ns#'>estimate</category><title>What-is-the-sequence-of-testing-process-performance-model-TPPM?</title><atom:summary type='text'>Sequence of TPPM
Testing Process Performance model is prepared for each Release testing activity of Project/Product .
After test designing of each release, TPPM estimation is completed.
While  test execution, TPPM is updated on daily basis or after some defined interval based on release test execution time.
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-is-sequence-of-testing-ppm.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-7896281684426936601</guid><pubDate>Mon, 15 Jun 2009 09:47:00 +0000</pubDate><atom:updated>2010-06-30T11:50:41.143-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>TPPM</category><category domain='http://www.blogger.com/atom/ns#'>predict</category><category domain='http://www.blogger.com/atom/ns#'>performance</category><category domain='http://www.blogger.com/atom/ns#'>Tracking</category><category domain='http://www.blogger.com/atom/ns#'>Testing</category><category domain='http://www.blogger.com/atom/ns#'>testing proces</category><category domain='http://www.blogger.com/atom/ns#'>PPM</category><category domain='http://www.blogger.com/atom/ns#'>model</category><category domain='http://www.blogger.com/atom/ns#'>Process</category><category domain='http://www.blogger.com/atom/ns#'>Monitor</category><category domain='http://www.blogger.com/atom/ns#'>efficiency</category><title>What-is-testing-process-performance-model-or-TPPM?</title><atom:summary type='text'>Testing Process Performance Model
Testing Process Performance model is to predict the important attributes of testing process and monitor the efficiency and performance of testing process by tracking and analyzing the actual data.</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-is-testing-ppm.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-2267553262732050184</guid><pubDate>Mon, 15 Jun 2009 09:45:00 +0000</pubDate><atom:updated>2010-06-30T11:45:47.780-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>predict</category><category domain='http://www.blogger.com/atom/ns#'>performance</category><category domain='http://www.blogger.com/atom/ns#'>Track</category><category domain='http://www.blogger.com/atom/ns#'>manipulate</category><category domain='http://www.blogger.com/atom/ns#'>PPM</category><category domain='http://www.blogger.com/atom/ns#'>model</category><category domain='http://www.blogger.com/atom/ns#'>project</category><category domain='http://www.blogger.com/atom/ns#'>Process</category><category domain='http://www.blogger.com/atom/ns#'>estimate</category><title>What-is-use-of-process-performance-models-PPMs?</title><atom:summary type='text'>Use Of PPMsProcess Performance models are used to estimate the project activities for different critical sub processes which are important to achieve the project and business objectives.

Mainly PPM are to :

Predict 
Track 
Manipulate
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-is-use-of-ppms.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-8409275697531961825</guid><pubDate>Mon, 15 Jun 2009 09:39:00 +0000</pubDate><atom:updated>2010-06-30T11:52:46.475-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>predict</category><category domain='http://www.blogger.com/atom/ns#'>Effort Estimation Model</category><category domain='http://www.blogger.com/atom/ns#'>Release Management PPM</category><category domain='http://www.blogger.com/atom/ns#'>effort to execute</category><category domain='http://www.blogger.com/atom/ns#'>Defect Estimation Model</category><category domain='http://www.blogger.com/atom/ns#'>Testing PPM</category><category domain='http://www.blogger.com/atom/ns#'>PPM</category><category domain='http://www.blogger.com/atom/ns#'>Time and Effort PPM</category><category domain='http://www.blogger.com/atom/ns#'>estimate</category><title>What-are-PPM-(process-performance-models)?</title><atom:summary type='text'>PPMProcess Performance Models are used to estimate and predict results to be achieved by following a process.

There are following process performance models.

Effort Estimation Model
Defect Estimation Model
Time and Effort PPM
Release Management PPM
Patch Release PPM
Testing PPM
</atom:summary><link>http://s-qa.blogspot.com/2009/06/what-are-ppmprocess-performance-models.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>1</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-8434945090463230093</guid><pubDate>Mon, 15 Jun 2009 09:31:00 +0000</pubDate><atom:updated>2010-06-10T12:04:33.011-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>statistical analysis</category><category domain='http://www.blogger.com/atom/ns#'>data collection</category><category domain='http://www.blogger.com/atom/ns#'>analysis</category><category domain='http://www.blogger.com/atom/ns#'>Analysis Reports</category><category domain='http://www.blogger.com/atom/ns#'>review</category><category domain='http://www.blogger.com/atom/ns#'>quantitative</category><category domain='http://www.blogger.com/atom/ns#'>Project Summary</category><category domain='http://www.blogger.com/atom/ns#'>reporting</category><title>How analysis and reporting after data collection?</title><atom:summary type='text'>There are a few steps for analysis and reporting.
Periodically review the actual results 
Apply quantitative and statistical techniques
Determine and document actions needed to address the deficiencies
The results of data analysis are reviewed with affected groups &amp; individuals

Project Summary 
Analysis Reports
</atom:summary><link>http://s-qa.blogspot.com/2009/06/how-analysis-and-reporting-after-data.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item><item><guid isPermaLink='false'>tag:blogger.com,1999:blog-9119679600526036070.post-8735265204102728147</guid><pubDate>Mon, 15 Jun 2009 09:28:00 +0000</pubDate><atom:updated>2010-06-11T13:06:02.532-07:00</atom:updated><category domain='http://www.blogger.com/atom/ns#'>QE</category><category domain='http://www.blogger.com/atom/ns#'>verification</category><category domain='http://www.blogger.com/atom/ns#'>measurement</category><category domain='http://www.blogger.com/atom/ns#'>eRMS</category><category domain='http://www.blogger.com/atom/ns#'>Integrity</category><category domain='http://www.blogger.com/atom/ns#'>organization metrics files</category><category domain='http://www.blogger.com/atom/ns#'>Project Summary</category><category domain='http://www.blogger.com/atom/ns#'>completeness</category><category domain='http://www.blogger.com/atom/ns#'>measure</category><category domain='http://www.blogger.com/atom/ns#'>peer reviews</category><category domain='http://www.blogger.com/atom/ns#'>helpdesk</category><category domain='http://www.blogger.com/atom/ns#'>accuracy SQA</category><category domain='http://www.blogger.com/atom/ns#'>metric</category><category domain='http://www.blogger.com/atom/ns#'>SEG</category><category domain='http://www.blogger.com/atom/ns#'>metrics</category><category domain='http://www.blogger.com/atom/ns#'>Analysis Reports</category><title>How data is collected for metrics and measurements?</title><atom:summary type='text'>There are some ways for metrics and measurements for data
Measurements are collected as per their definition at defined points as mentioned in Organization Metrics File
Data is collected and compiled by using Project Summary, Help Desk, eRMS, Analysis Reports, Peer Review Analysis Reports etc 
Verification of the measurement data is done independently to check completeness, integrity, accuracy by</atom:summary><link>http://s-qa.blogspot.com/2009/06/how-data-ic-collected-for-metrics-and.html</link><author>noreply@blogger.com (Hafeez)</author><thr:total>0</thr:total></item></channel></rss>
