Software requirements are the foundation of any critical system. Functional safety standards—including IEC 61508, ISO 26262, EN 50128, IEC 62304, and DO-178C—do not just expect complete and consistent requirements: they mandate traceability between requirements, design, implementation, and verification artifacts.
Despite this, many organizations still rely on ad hoc tools like Word or Excel to manage their requirements, which are unsuitable for safety-related software:
No support for structured traceability
No enforcement of processes
Difficult and time-consuming reporting
Error-prone configuration management
ECLAIR brings automation, structure, and reliability to requirements management, making traceability a first-class, continuously verifiable property of your development process.
The ECLAIR Software Verification Platform provides comprehensive support for requirements traceability, fully integrated into its static analysis and reporting infrastructure.
Annotate your code with lightweight markers (e.g., @implements REQ-42) to map implementation artifacts to requirements.
@implements REQ-42
ECLAIR checks for:
Unlike most tools that stop at MISRA C’s “all code shall be traceable to requirements”, ECLAIR goes further, supporting bidirectional traceability between:
ECLAIR embeds StrictDoc, a lightweight open-source tool to author and manage technical specifications:
Fully supports the bidirectional linking of test code to implementation and requirements, as mandated by:
ECLAIR’s requirements management tools are designed for compliance and qualification:
Highly configurable to reflect your organization’s requirement formats and identifiers
Fully auditable through versioned, human-readable files
Integrated in CI/CD workflows, enabling traceability verification with each build
Supports requirement-to-test, requirement-to-code, and design-to-code links, out-of-the-box
Whether you are seeking compliance with a specific standard or building a future-proof requirements infrastructure, ECLAIR provides the automation and assurance you need.
/*! Emergency brake logic. * * @implements SAF-RQ-3.5 * @tests SAF-TC-3.5 */ void engage_emergency_brake(void) { // ... }
ECLAIR will check that:
SAF-RQ-3.5 is a known requirement
SAF-RQ-3.5
This function satisfies it
SAF-TC-3.5 exists and exercises this function
SAF-TC-3.5
All referenced elements are covered and cross-linked
With ECLAIR, requirements traceability is no longer an afterthought or audit-time scramble: it becomes a traceable, automatable, and verifiable part of your daily development process.
Let us show you how ECLAIR can transform your requirements management.
Schedule a demo