TiCS · Maintainability certification

Get the maintainability of your software certified

The Trusted Product Maintainability model, defined by TIOBE and TÜViT on the basis of the ISO/IEC 25010 standard, rates the maintainability of code from A to F. From a C rating, your software can receive a certificate from TÜViT.

Why a certificate

Independent proof, rather than a promise

Software that is easy to maintain costs less to evolve, and is fixed faster. The certificate shows it to those who do not read your code.

◆

For your customers

Your customers and prime contractors see the maintainability of your software attested by a third party, for a specific version.

◆

For tenders

A verifiable argument, with a public rating and method, rather than a mere statement.

◆

For a sale or a takeover

The value of software also depends on what its maintenance will cost: the certificate gives a measure of it.

◆

For your teams

A clear, shared goal: reach C, then B. Progress is measured at every version.

The model in brief

Five measurements, one score, one rating

The model breaks down the maintainability of ISO/IEC 25010 (modularity, reusability, analysability, modifiability, testability) into five code measurements. Each is scored from 0 to 100% and counts for one fifth of the score.

MeasurementWhat is measured
Cyclomatic complexityThe average complexity of functions.
Compiler warningsThe warnings issued at the highest level, for all the compilers of the project.
Coding standard complianceThe automatically checkable rules of a recognized coding standard for each language, excluding naming and layout rules.
Code duplicationThe share of duplicated code, in sequences of 100 tokens, excluding comments and whitespace.
Coupling (“fan out”)The average number of dependencies per file; internal dependencies weigh more.

What is assessed

The hand-written code of the product, in all its languages: the scores of the languages are combined into one. Generated code, third-party code and test code do not count. A measurement that cannot be made on part of the code reduces the score accordingly.

Where the industry stands

Across more than a billion lines of industrial code, some 5,000 projects, the average score is 66%, a D rating, according to TIOBE. Reaching a C rating means doing better than average.

The full definition of the model (PDF) ↗

The process

From the first measurement to the certificate

Precilog is your point of contact in France, at every step.

01

Measure

TiCS measures the five indicators of the model, which are also part of the TQI. A first measurement gives your starting rating: through a proof of concept or a TQI quality audit.

TiCS
02

Improve

Below a C rating, TiCS shows what weighs most on the score, down to the file and the function: your teams know where to start, and track their progress at every build.

Teams
03

Get evaluated

The product is evaluated by TIOBE, a testing laboratory approved by TÜViT for evaluations of software products. You specify the name of the product, its version and the files concerned.

TIOBE
04

Obtain the certificate

If the score reaches a C rating, TÜViT's certification body issues the certificate, for that version of the product and for a limited period.

TÜViT
Scope

What the certificate attests, and what it does not

◆

It attests

The maintainability of your software, measured according to the Trusted Product Maintainability model.

  • For a specific version of the product
  • On the hand-written code, in all its languages
  • With a rating from A to C
◆

It does not attest

The certificate covers maintainability only.

  • Not functional safety (ISO 26262, IEC 61508, DO-178C…)
  • Not the reliability or the cybersecurity of the software
  • Not later versions: each one is evaluated again
◆

It is your software that is certified

TiCS is the measuring tool; the certificate is issued to your product, not to the tool.

Aim for the certificate

Tell us about the software concerned and where you stand: we will review your code and the process with you.

Submit a request →

TiCS  ·  TQI quality audit  ·  Customer testimonials  ·  Proof of concept