ISO 25119 / EN 16590 — “Tractors and machinery for agriculture and forestry: safety-related parts of control systems” — replaces, in this field, IEC 61508, which was until now the reference as the generic functional safety standard.
The aim of the standard is to make agricultural vehicles and machinery safer and more reliable. Developing according to this standard gives the manufacturer a solid basis for providing evidence in case of damage — and the burden of proof generally lies with the manufacturer.
ISO 25119 has four parts; Part 3 covers hardware and software development, as well as testing. The V-model is the basis for development.
Like ISO 26262, it prescribes a functional safety concept, carrying the functional requirements of the system, and a technical safety concept, carrying the architecture and design.
For software component testing, the standard requires evidence of structural coverage of the source code — entry points, statement coverage and branch coverage — at levels SRL 2 and SRL 3 (Software Requirement Level).
This measurement is performed with Testwell CTC++, used successfully in many safety-critical software projects. The tool covers these levels and goes further: decision/condition, MC/DC, and up to multiple condition coverage.
ISO 25119 also requires checklists and static code analysis — control flow analysis and data flow analysis.
Testwell CTC++ is certified by TÜV SÜD for use in the development of safety-critical software, and ISO 25119 is explicitly within the scope of this certification.
A Safety Package is supplied with the tool, and a qualification kit simplifies its qualification in your projects: classification and qualification plans and reports, safety manual, test plan and a test suite you run in your own environment.
ISO 25119 is among the standards covered by the TÜV SÜD certificate of Testwell CTC++. The animation shows how this certificate and the Safety Package lighten the qualification of the tool.
The 13 Testwell CTC++ animations →
Like ISO 26262, from which it draws, ISO 25119-3 requires design and coding rules — language subset, complexity limits, conventions — and recommends static analysis, depending on the software requirement level (SRL). You then have to demonstrate, release after release, that the code complies with them.
TiCS supervises source code quality in multi-technology, multi-project and multi-site environments. It lets you:
From one release to the next, quality must not slip back. The animation shows how a quality gate checks every change before it enters the code.
The 14 TiCS animations →Developing and delivering safety-critical software requires up-to-date knowledge. Our webinars and in-house training courses support developers and quality managers on regulatory requirements and the associated testing practices.
The evaluation is free and supported: installation, configuration, integration into your build chain and reading the coverage reports.