Apr 10, 2011

How important is QA to the software development life cycle?


6 days ago
Software development, like any complex development activity, is a process full of risks. The risks are both technical and programmatic; that is, risks that the software or website will not perform as intended or will be too difficult to operate/browse, modify, or maintain are technical risks, whereas risks that the project will overrun cost or schedule are programmatic risks.
The goal of QA is to reduce these risks. For example, coding standards are established to ensure the delivery of quality code.

If no standards are set, there exists a risk that the code will not meet the usability requirements, and that the code will need to be reworked.
If standards are set but there is no explicit process for assuring that all code meets the standards, then there is a risk that the code base will not meet the standards. Similarly, the lack of an Error Management and Defect Life Cycle workflow increases the risk that problems in the software will be forgotten and not corrected, or that important problems will not get priority attention.

The QA process is mandatory in a software development cycle to reduce these risks, and to assure quality in both the workflow and the final product. To have no QA activity is to increase the risk that unacceptable code will be released.

Really? QA is everything. 


Check out Top-5 misconceptions about testing. And don't forget to add yours 'An importance of QA is questionable'. :)



Software Quality assurance is the process, in which whole software development activities will strict follow some rules or regulations. The rules or regulations are called as Standards that is followed in Software development life cycle. If this standard is not followed then there is chance for errors in many ways. These standard will assure the development process bug free.


The quality assurance standards is set by organization and it is followed the all team members of the project. This Quality assurance specialist will monitor every one.


Simply this assurance enables 100 % bug free software.


Domains Whether you are looking to purchase a few domain names or liquidate your entire portfolio, these articles offer useful tips and techniques for finding potential buyers and negotiating domain purchase. You will also gain insight into the importance of managing, evaluating and marketing your domains for purchase.

Though I am not an expert on this subject, I did some research and come up with this answer and have included some resources I think will help.

Simply put, QA is pretty important. Quality Assurance testing is employed to reduce possible defects in every stage of the software development life cycle. The 2003 book "Managing Software Engineering Knowledge" states "the focus of [Software Quality Assurance] is to monitor continuously throughout the Software Development Life Cycle to ensure the quality of the delivered products. This requires monitoring both the processes and the products. In process assurance, SQA provides management with objective feedback regarding compliance to approved plans, procedures, standards, and analyses. Product assurance activities focus on the changing level of product quality within each phase of the life cycle, such as the requirements, design, code, and test plan. The objective is to identify and eliminate defects throughout the life cycle as early as possible, thus reducing test and maintenance costs."

A recent article on Bhakti Satalkar on Buzzle.com corroborates this, stating that the main goals of QA during software development are to develop error free software, to determine if there is any variation from software requirements, to use the software in a real time environment, and to provide confidence in the software, among other things. The bottom line seems to be that QA is important, and that customers would prefer to wait slightly longer for a quality product then receive a potentially flawed one sooner. You are better off taking the time to complete it than not.

To find an excerpt from "Managing Software Engineering Knowledge" go here

Answer this