How Lattix supports certification
Evaluate, trace and control your architecture
Functional safety compliance
Every feature, seen through the matrix
Lattix offers comprehensive features to help software developers, quality engineers, software testers and architects comply with exacting functional safety standards. Pick a feature to see what it reveals.
One platform, five solutions
Where functional safety fits in Lattix
The same dependency model powers every Lattix solution. Select a hexagon to see what it covers.
Proven on certified programs
Used up to the highest integrity levels
Our solutions have been used successfully on projects working to ISO 26262, ASPICE, FDA / IEC 62304, DO-178C and EN 61508.
ISO 26262
Automotive
Up to ASIL D
ASPICE
Automotive process
Levels 3, 4, 5 and 6
IEC 62304
Medical (FDA)
Up to Class C
DO-178C
Avionics
Up to Level A
EN 61508
Industrial
SIL 3 / 4
ISO 26262 · Part 6 · Table 3
Principles for software architectural design
Choose your ASIL to see what the standard recommends — and where Lattix gives you the evidence.
At ASIL D, 6 of 7 methods are highly recommended (++). Lattix gives direct evidence for methods 1a, 1d and 1e — 3 of them highly recommended at this level.
| # | Method | A | B | C | D | Lattix |
|---|---|---|---|---|---|---|
| 1a | Hierarchical structure of software components | ++ | ++ | ++ | ++ | |
| Table 3 requires demonstrating hierarchical structure — exactly what the Lattix DSM does, showing the hierarchy of the software architecture with its unique dependency structure matrix. | ||||||
| 1b | Restricted size of software components | ++ | ++ | ++ | ++ | |
| 1c | Restricted size of interfaces | + | + | + | + | |
| 1d | High cohesion within each software component | + | ++ | ++ | ++ | |
| Track cohesion with Lattix metrics. Example thresholds for certification authorities can be derived from our metrics of well-known open-source systems. | ||||||
| 1e | Restricted coupling between software components | + | ++ | ++ | ++ | |
| Lattix Coupling and Stability metrics show where components depend on each other too heavily — with the same open-source baselines for thresholds. | ||||||
| 1f | Appropriate scheduling properties | ++ | ++ | ++ | ++ | |
| 1g | Restricted use of interrupts | + | + | + | ++ | |
++ highly recommended · + recommended. For 1b, 1c, 1e and 1g, “restricted” means minimized in balance with other design considerations.
Freedom from interference
Mixed-ASIL software on shared hardware, kept apart
Modern ISO 26262 applications let functions with different ASILs or QM classifications share one ECU — if the software architecture keeps them apart. Lattix architecture rules check data usage and partitioning, so components only meet through defined interfaces and the selected memory partitioning.
FFI reports show unexpected function calls, data-flow issues, undefined interfaces and global data shared between components.
Automotive SPICE
The software engineering V, connected end to end
ASPICE defines a maturity model for system and software development, assessed against the Process Assessment Model (PAM). Lattix has been successfully used to achieve Automotive SPICE Levels 3, 4, 5, and 6 at several companies. Select a step to see how it is verified on the other side of the V.
- SWE.1 Software Requirements Analysis ↔ SWE.6 Software Qualification Test
- SWE.2 Software Architectural Design ↔ SWE.5 Software Integration and Integration Test
- SWE.3 Software Detailed Design and Unit Construction ↔ SWE.4 Software Unit Verification
FDA · IEC 62304
Medical device software, Class A to C
Lattix has been successfully used on medical projects to help verify the architectural requirements for Class A, B and C medical devices.
A
No injury or damage to health is possible
B
Non-serious injury is possible
C
Death or serious injury is possible
Reduce your time-to-certification
See how Lattix fits your ISO 26262, ASPICE, DO-178C or IEC 62304 program.