When I started developing Software applications, I used to think that it is the work of the QA team to analyze bugs in the software. As I continued the job, I understood that it’s not the QA team alone who is responsible for refining the software before it is sent to the client. It has to be done by everybody associated with the project that is the whole team members of a project.

I learned that the main role in doing quality assurance is of the developers, QA engineer, project manager, and the client. These personnel are responsible to assure that the software product is of good quality. By ‘quality’ it means that there are no errors in the software and it can be conveniently accessed by the users. Thus, the QA engineers use ‘quality model’ for testing the Software Application.

The quality model is a part of International quality standard ISO/IEC 9126. This standard is used to determine the software quality before it is deployed in the client’s environment. The reason to use this standard is that it helps the testers to know whether the application is feasible to use.

Consistency is required in the software application so that it can run on the system of the client smoothly. This model helps to know whether the developed software application is the complete solution or not. It helps to check the performance and other related aspects.

The Quality Model for doing the Software Quality Assurance is divided into categories and sub-categories that are as follows:-

• Functionality-accuracy, security, interoperability, and suitability

• Reliability-fault tolerance, recoverability

• Usability-understandability, attractiveness, and operability

• Efficiency-time behavior, resource utilization

• Maintainability-stability, testability

• Portability-adaptability, installability

The cost of committing mistakes while writing a code can lead to adverse effects on the reputation of the brand and affects the businesses process of the other departments. Thus, using a quality model can help you to create successful software products. It’s not possible that every time you writing the code that is free from errors, at least you can follow a relevant pattern to do the coding part that you can do by using ISO/IEC 9126 standard for doing Software Quality Assurance.

The above-described categories and subcategories help the Quality Assurance Team to analyze the location of the errors in the software application and to resolve them as soon as possible.