Safety-critical software
Embedded C written to MISRA C and traced from requirement to test, ready for a functional-safety assessment.
01 · Build
What we build
In a machine guard, a vehicle or a medical device, software has to fail safely and prove it.
- C code to MISRA C:2012, with every deviation recorded and justified
- Requirements traced to design, code and tests in one matrix
- Static analysis and unit tests with statement and branch coverage reports
- Work products prepared for IEC 61508, ISO 26262 or IEC 62304 assessment
- Watchdogs, safe states and fault handling designed from a hazard analysis
02 · Demo · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
- motor_guard firmware, SIL 2 target
- MISRA C:2012 mandatory
- MISRA C:2012 required
- Requirement trace
- Branch coverage
- Statement coverage
03 · Features
What it does well
- 01
Traceability matrix
Each requirement links to its design, code and tests, and to the result of every test run.
- 02
Recorded deviations
Any MISRA rule not followed is listed with its reason, its risk and who approved it.
- 03
Coverage evidence
Statement, branch and, where required, MC/DC coverage are reported per build.
- 04
Safe states
Every detected fault leads to a defined state, documented and tested on the target.
- 05
Controlled builds
Compiler, flags and tool versions are fixed and recorded, so a release can be rebuilt.
- 06
Change impact
Each change lists the requirements and tests it touches before it is merged.
04 · FAQ
Questions
Will you certify our product?
No. Certification is issued by an accredited assessor such as a notified body or a TÜV. We prepare the evidence they ask for: the safety plan inputs, requirement traces, analysis results, test reports and records of every deviation, so the assessment has what it needs.
Which standard applies to us?
It depends on the product: IEC 61508 for industrial and general safety functions, ISO 26262 for road vehicles, IEC 62304 for medical device software. Your safety engineer sets the integrity level; we work to the methods that level requires and record that we did.
Can you bring existing code up to MISRA?
Yes, in stages. We run static analysis to count and group the violations, fix the ones with real risk first, and record a justified deviation for any rule that cannot reasonably be met. You get a report showing where the code stands at each step.
05 · Services
Services that go with it
- ServiceCustom software developmentSoftware designed and built around the way your business works, shown to you working at every review.
- ServiceCode reviewAn independent review of your codebase, with clear findings ranked by risk and a recommended fix for each.
- ServiceTechnical documentationClear, accurate documentation for developers, operators and users, written from the real running system.
06 · Software
Related software
- SoftwareEmbedded firmwareDependable code for the microcontrollers inside your product, from first board bring-up to updates in the field.
- SoftwareFPGA and RTL designLogic for FPGAs written in SystemVerilog or VHDL, verified in simulation before it reaches the board.
- SoftwareOperating systemsLean, hardened operating system images built for your hardware, your product and your update process.
- SoftwareTest automationAutomated tests that run on every change, so releases are checked by machines before customers see them.