Why is Quality Clouds Important for Monitoring Code/No-Code Developments in SaaS Platforms?

When it comes to code quality, Quality Clouds generates dozens of metrics to expand your quality KPIs.

The need for quality in SaaS programmes

Any product developed and launched is exposed to very exigent scrutiny. In a world with fierce competition for customers’ attention, quality plays a key role that can make the product succeed or fall into oblivion, lose customer trust or even worse damage your brand reputation.

However, measuring the software quality of a product is hard. The meaning of quality can change depending on the company, the business or even teams. It is a wide term that can be very subjective and seen from different perspectives:

  • Quality of the implementation from a functional point of view: Is the product in line with the requirements defined?
  • Quality from a customer satisfaction perspective or will the product meet customer needs?
  • Quality of the product offering Is the product correctly brought to the market?
  • Code Quality Number of bugs and complexity. Performance, scalability, security, and maintainability

So how do we measure the quality of a product? How can we ensure that our next product release will meet expectations in terms of quality?

  1. The possibilities are endless. So one could start by defining what quality means at a company level and the metrics to track and measure it. It is advisable to agree on monitoring just a few, rather than covering too many and potentially losing focus.
  2. Benchmarking helps understanding. By benchmarking these metrics, whether with industry-wide references or with internal goals, you will understand where you stand and apply the necessary corrective measures.

Code Quality, Metrics, and KPIs in SaaS

Quality Clouds inspects code and structure to produce metrics related to bugs and complexity. We also capture information about configuration changes done in the platform. Issues detected in configuration changes are especially useful to monitor the quality of low code/no-code developments in SaaS platforms, such as ServiceNow or Salesforce.

This can definitely help. It offers precise and reliable measurements for you to acquire new insights when tracking the quality of your SaaS platform.

For some of the relevant metrics, Quality Clouds is a calculating benchmark from other environments in our ecosystem.

Below you will find a few examples of quality metrics generated by Quality Clouds from your SaaS platforms.

The metrics are categorized into two main groups or types:

Code quality and configuration – Adherence to best practices

Quality Clouds raises issues searching for adherence or its lack to the Quality Clouds ruleset for both code and configuration changes. It categorizes the issues by severity and impact area – Security, Scalability, Manageability, and Performance.

All the issues related to metrics from both code and configuration fall in this category: number of issues, technical debt, code quality ratios, etc.

Code quality- Inventory and complexity

Quality Clouds provides a comprehensive group of metrics of your platform’s structure, such as the number of lines of code, number of code elements, number of integrations, etc.

These metrics will help understand and provide insight on the complexity of the product.

Metrics, Code Quality and Configuration at Platform Level

Quality of Cloud and breakdown by Impact Area

The Quality of Cloud shows an indication of the overall health of your instance. Healthy instances range between 80% and 100%. Those between 70% and 80% need close monitoring of further developments. A percentage below the 70% figure means that the cloud needs remediation work

Number of issues in the platform and its breakdown by severity, impact area and group

Issues detected by Quality Clouds scans according to non-compliance with a best practice/rule.

Technical Debt and breakdown by Impact Area

It represents the implied cost in hours of development effort needed to solve the issues/violations detected in the platform due to non-adherence to best practices.

Ratio of elements with Issues

The ratio of Configuration Elements (CEs) affected by one or more issues shows how easy it would be to do remediation. High ratio means that the issues are all over the code, which means it will be difficult to remediate. A low ratio means that issues are concentrated, which, in turn, makes them easy to rework

Code Quality

Code quality is defined as the number of issues for every 1000 lines of code.

Code quality- Inventory and complexity

Lines of code and number of elements

Total number of lines of code and configuration elements in the platform. The product offers multiple breakdowns for these metrics, allowing a more detailed analysis when inspecting changes inventory and complexity wise.

As an example, you might need to control the growth of lines of code of certain types of elements or avoid the creation of specific objects that from your view, could be a symptom of poor quality.

Number of Open Source libraries detected

This table shows the open-source JavaScript libraries detected in the instance. Losing visibility on installed libraries or not updating them properly exposes your instance to risks.

Number of integrations

It lets you understand how your platform is configured.

Tracing Quality Metrics through Environments

In an ideal world where a strict SDLC process is followed, the environments involved should be aligned from code versioning and components perspectives. The reality is that, quite often, we use shared environments for different projects and it is quite common that they diverge in some aspects.

Quality Clouds gives the ability to compare quality metrics between different environments easily, in order to mitigate and track these differences. As an example, any of the metrics mentioned above can be used when comparing environments:

Tracking Quality Metrics of a Specific Project in SaaS

Quality Clouds makes it possible to isolate a development for a particular project or release using the Quality Gates functionality.

Once Quality Gates is enabled, it will be possible to track the issues related metrics, such as number of issues, Technical Debt, and breakdowns. This works only for the developments started right after the activation.

These are very valuable and useful metrics if there is the need to track quality at these levels

Conclusions

These are just a few examples of the multiple metrics that Quality Clouds generates.

At Quality Clouds, we recommend benchmarking your quality. We suggest you start with the big quality metrics where the benchmarks are available in the product, so that you can compare with other similar platforms:

– Code Quality and configuration – Adherence to coding best practices

Quality of Cloud

Issues

Technical Debt

Ratio of configuration elements with issues

– Code Quality – Inventory and complexity

Lines of code

Number of configuration elements

If you’d like to hear more about how Quality Clouds can help track the quality of your platforms or developments, please get in touch with us or Drop us a line.

Want to learn more? Let's talk: