What is Software Quality?

“Why do we never have the time to do it right the first time, but always have time to do it over and over after the first time?” – Anonymous 

Quality is something that happens at every stage of Software Development!

When I talk about Software Quality, almost everyone in the Information Technology world thinks about “Software Testing”. Unfortunately, this is a myopic view of Quality as a specific team effort and not as something, that should be embedded and part of the complete Software Development Life Cycle!

Quality can be defined and need not be an “ambiguous term” for an organization.

For any software, quality is more aptly seen from a view of what the customers considers as ‘Quality’. Although, this is not the only way to consider ‘Quality’.

Quality must be seen from the viewpoint of ALL stakeholders involved with the product. Apart from this, ‘Quality’ should be considered as everybody’s responsibility. From an operational standpoint, we do consider “Quality / Testing Teams” to take ownership. Although, testing teams can be made more relevant and productive, if the organization culture promotes a very high-degree of collaboration between the Quality / Testing Team and all the other teams involved in developing the product or providing services.

Quality can be defined with two perspectives –

1. Quantitatively: A quantitative representation of software quality is very easy and directly refers to using metrics (or “measurements”), such as – “If ALL the customer requirements are met, we have achieved quality” . Here, the underlying assumption is, that the software development team (includes all sub-teams) have documented each and every stated or unstated customer requirements as part of a requirements management document / software.

2. Qualitatively: A qualitative representation of software quality is very complex and directly refers to understanding the “perspectives” of various stakeholders (i.e. customers, business analysts, sales team etc…). For example, “If the ‘Product Usability’ is very high, the product shall be of very high-quality” . This may be true, for products with few but very important features! Some of these can be measured, although these are still subjective, such as by understanding the “Customer Satisfaction Scores”, “Customer Usability Exercises”, “UAT Feedback” etc…

 

It is very important for every product / project stakeholder to understand the above perspective. Only such an understanding can promote a healthy organization culture amongst various teams to work together and come up with revolutionary software products, that can change this world.

- Written by Anand Nanavati (SupraDigit Solutions)