Summary: Software Quality Assurance

Software quality results from the whole process of specifying and building software, not just the formal quality and testing disciplines, as noted here:

https://www.blackliszt.com/2011/07/software-quality-theory-and-reality.html

This summary is focused “just” on what is called Software Quality Assurance.

Software quality, with some exceptions, is bad. People just accept it as a fact of life, though the people who use the software usually make it clear that they’re not happy.

https://www.blackliszt.com/2023/05/summary-software-quality-problems.html

There are groups of software people who use proven, decades-old methods to build high quality software quickly and well, methods that violate the regulations and professional methods that dominate the field.

Here is an introduction to the winning method of software QA.

https://www.blackliszt.com/2021/07/the-revolutionary-championchallenger-method-of-software-qa.html

The typical methods of QA lead to endless work, added to already-long development.

https://www.blackliszt.com/2015/12/speed-optimized-software-qa-or-cancer.html

Good QA recognizes that one method should be used for getting software to do what you want and a different method for keeping it right, a.k.a. “regression testing.”

https://www.blackliszt.com/2012/04/a-simple-framework-for-software-quality-assurance.html

A remarkable thing about traditional QA is that it’s all built and run in the lab, while good QA is focused on the only environment users care about, essentially field-testing.

https://www.blackliszt.com/2012/04/field-tested-software.html

Here’s an overview of the book on the subject.

https://www.blackliszt.com/2012/10/software-quality-assurance-book.html