IQ, OQ, and PQ constitute the 3Q’s of Software Validation Process.
As testers we all know that the Software Development Team develops the software in-house as per the Software Requirements Specification (SRS), Functional Specification and later the Testing Team verifies the implementation at different levels of testing at various testing environments, from simplest to the high end, which thereby replicates the production environment. Continue reading →
New trainees came on board and we had a training class to learn software testing concepts. After seeing those enthusiastic faces with their almost blank-slate minds (professionally), I decided to take a detour to my routine training.
After a brief introduction, instead of talking about software testing like I normally do, I threw a question at the fresh minds – ‘Can anyone explain me what a wireframe is? ’
The answer was a pause and thus, we decided to discuss it. And that is how it started – Wireframe/Prototype Testing :) Continue reading →
Personal Note: It’s a great opportunity for any QA/Tester to be a CMMI Appraisal Team Member (ATM). ATM gets an extensive exposure of a complete CMMI model. If your organization is going for appraisal and if you get an opportunity to be an ATM, grab it. It’s an achievement that you will like to add on to your resume.
To Readers: Appraisal is a complex and time taking process. However, I have tried to describe it as simple as possible. This article will give you a brief idea about CMMI Appraisal. It’s not about CMMI model but it will explain what happens during appraisal! There may be understanding problems initially (If you are not familiar with CMMI terminology) but, until you arrive at an example below, Please keep reading until then.Continue reading →
Failure mode and effects analysis (FMEA) is a risk management technique. If implemented properly this can be a great addition to the best quality assurance processes to be followed. In this article, our goal is to introduce you to this risk analysis technique which in the end, is very useful for improving the software quality.
FMEA is mostly used by the upper management or stakeholders. In practice, the testers get little insights into this technique. But now the trend is changing and I feel if the testers understand this concept properly, they can drive their thought process of Continue reading →
We want to wish a Happy and Healthy New Year 2014 to all our readers!
2013 has been a wonderful year for STH – why wouldn’t it be? We had the best of the readers and followers behind us.
Back in December 2006, I started this blog with an intention to help software testers and today – after 7 years – it is helping thousands of software testing and quality assurance professionals worldwide!
By now, we all know that for a tester, documentation is an integral part of his daily life. There is an overload of testing artifacts that are created, reviewed, approved, used, maintained and distributed. We always have clear-cut processes laid out for how to create a document, how to use it, who should it go to, etc.
Through this article, we are going to shed some light on the small but important topic – Reviews.
Reviewing is a form of testing too – the verification part of the V&V also called static testing.
Software Process Engineering Software Engineering is a discipline that aims at producing high-quality software through systematic, well-planned approach to software development. It contains many good practices, following the standards to achieve the quality product. The three main phases of Software Development are Analysis – Design – Implementation. To accomplish high-quality software is essential to produce the defect-free product.
The defect is the unexpected or undesired behaviour that occurs in the product. Anything related to defect is a continual process, not a particular state.
Defect Management Finding and fixing the defect in the early stage of the software development reduces time, rework and money. Finding the defect in later stages always costs multiple times than early stages. It enhances the quality by adding reliability, portability, maintainability etc. Hence it is advisable every company should go with defect management system and defect management team at every stage of the development to attain the good quality in products and to gain the customer confidence.
This article explains what are CMM levels and how to achieve these CMM levels for QA processes – explained with best examples.
For any process, whether it is a QA process, development process or any non-technical process, there are levels of its maturity. By levels of maturity, we mean that the level of formality and processes improvement, like ad-hoc processes – to formally defined steps – to managed result metrics – to optimization of the processes.
CMM (Capability Maturity Model) is a process-based model which is used to assess the maturity of an organization for different domains. The concept of CMM was introduced by Software Engineering Institute (SEI) in the USA.