TIOBE Quality Indicator (TQI) ↗
The full definition of the TiCS quality model: the indicators measured, their weighting and the A-to-F scale.
The in-depth articles published by TIOBE, the maker of TiCS, sorted by topic and summarized: what code quality is, how to measure it, how to keep it under control. The articles open in a new tab.
The definitions on which TiCS measurements are based.
The full definition of the TiCS quality model: the indicators measured, their weighting and the A-to-F scale.
The maintainability model defined by TIOBE and TÜViT, based on ISO/IEC 25010: five measures, one rating from A to F.
The languages, analyzers and integrations supported by TiCS.
What is measured, why, and how to turn it into a decision-making tool.
Reliability, maintainability, security: what code quality covers, and what its absence costs (failures, code that is hard to evolve, vulnerabilities).
Measure objectively and repeatedly, choose indicators that cover reliability, maintainability and security, then bring them together in a model such as the TQI.
Why comparing your code with other industrial projects gives more meaningful scores, and why that benchmark must rely on an independent model.
Technical debt, the future cost of quick fixes, grows like interest. When to accept it, and how to track it.
Maintenance can account for about 90% of a software product's life. An overview of the Trusted Product Maintainability model and its five measures.
Six maturity levels, from one-off measurements to quality managed across the company: where you stand, and the next step.
The cost of quality versus the cost of poor quality: finding the right balance for the domain and the product's lifetime. By Ger Cloudt, Software Quality Manager at ASML.
A series of articles on the indicator that weighs most on maintainability and testing effort.
Four ways to measure complexity (McCabe, NPath, cognitive complexity, Halstead difficulty), applied to the same function.
Harder maintenance, defects, costs, testing needs: what overly complex code leads to, and who benefits from measuring it.
Why TIOBE uses McCabe's cyclomatic complexity: simple to compute, widely recognized, useful for estimating testing effort.
The complexity of ten languages compared, across about 8,000 commercial projects: MATLAB and C at the top, Rust the least complex.
Keeping quality from slipping, without blocking the teams.
Automatic checks that stop delivery when quality falls below a threshold. Start with modest, relative goals.
Fast checks on pull requests, deeper analyses at night, goals on new violations only, and the indicators not to block on.
Sorting coding rules into about ten severity levels, to deal first with what matters most.
What the CRA changes for development teams. See also our page Software composition and CRA.
The CRA makes software security a legal obligation: security by design, vulnerability management for code and dependencies, monitoring after release to market.
Static security analysis for your code, composition analysis for your dependencies, and how to turn them into prioritized, traceable findings for an auditor.
Code quality in the organization, in the face of AI and alongside other tools. Customer case studies are gathered in the customer testimonials.
AI-generated code must meet the same requirements as hand-written code, and be checked by repeatable tools such as static analysis.
A large European semiconductor supplier, which found its defects after delivery, introduces quality gates and a coding standard fed by field defects.
Why agile transformations disappoint: business environment, architecture, team and code quality must progress together.
A lightweight analyzer for one team, or a framework that brings several analyzers under one measurement model: the comparison according to TIOBE.
A flowchart for choosing the language best suited to a project.
Articles published by TIOBE Software on tiobe.com/knowledge, summarized by Precilog.
A free proof of concept on a project of your choice: the indicators from these articles, applied to your code.