Software Quality Insights

On "Software Testing", in recent years, the industry discussed more. But few people mention "software quality"!

Software testing is just a means of software quality assurance. However, it is often easy to use software testing as the only means of software quality assurance, even for "functional test/Validation testing" or user-based scenario testing. This does not make a better software quality assurance.

So what is software quality? As for the definition of software quality, many books are defined, but so far there is no standard definition. However, I agree with TQM: The core of TQM is to assign the responsibility of process quality to the owner of the process.

Consumer (end-user) is the product, the consumer encounters any product use problem, will become the product quality problem.

However, the product is produced through a number of process results. In each process, it will be possible to elicit quality problems, and these quality issues are caused by the work of practitioners in different skills and fields, quality types are different, such as demand problems (unwanted functions or unacceptable functions), design problems (bad design not only may affect the actual use of the product effect, There is also the possibility of economic loss to the consumer), the realization of the problem (not in accordance with the design of production), etc...

The above questions, in fact, I would like to express that: the quality of software products are different types, and these quality types often require different skills and knowledge background of people to confirm and guarantee.

So, when we want to make sure that the quality of an upcoming product reaches a certain level, we first need to evaluate what is the quality type of the product? Do these quality types have the right people to confirm and test?

For ease of understanding, for example:

Activity name-------quality type-------warranty means

========================================

Demand analysis-------Requirements quality-------Research, review

Software design-------Design quality-------Review and test

Code authoring-------Code quality-------Review and testing

Documenting the documentation-------document quality-------Review

Release-------release quality-------validation and testing

Software Quality Insights