Building safer systems with Lattix
Evaluate
Evaluate your system against key architectural metrics as required by ISO26262 Part 6
Show traceability
Show traceability from requirements to code to test in one unified matrix
Control
Control software architecture to improve testability and reduce time-to-certification
Functional Safety Compliance
Lattix offers comprehensive features to help software developers, quality engineers, software testers and architects comply with exacting functional safety standards. These features include:
- Metrics, such as Cohesion, Coupling, Complexity, Stability and Connectedness
- Traceability, including Gap Analysis, Completeness and Consistency
- Architecture Definition
- Rules Enforcement
- Freedom from Interference
- Data and Control Coupling Analysis
ISO26262
Our solutions have been used successfully on projects working to ISO26262 (up to ASIL D), ASPICE, FDA/62304 (up to Class C medical devices), DO-178C (up to Level A) and EN 61508 (SIL 3/4).
Table 3 requires demonstrating “hierarchical structure”. This is exactly what the Lattix DSM does, showing the hierarchy of the software architecture with its unique dependency structure matrix representation.
Clauses 1(d) and 1 (e) can also be tracked using Lattix Cohesion, Coupling and Stability metrics. Example thresholds for certification authorities can be derived from our metrics of well known open source systems.
Freedom From Interference (FFI)
Lattix can be used to fulfil requirements for FFI. It is common in modern automotive applications conforming to ISO26262 to allow several safety-relevant functions with different ASILs or QM classifications to coexist on a common hardware. However, this requires a suitable software architecture to be in place for corresponding software projects. Compliance with the safety architecture is the basis for FFI.
Lattix architecture rules check on data usage and partitioning ensure the compliant use of the defined interfaces and the selected memory partitioning mechanisms. Deviations from the architecture are reported in 3 places: in the Lattix desktop tool, in CI/CD Git Merge Requests, and in code editors such as Visual Code. FFI reporting shows, among other things, unexpected function calls, issues with data flow, undefined interfaces, and global data usage between architecture components.
ASPICE
The Automotive SPICE (Software Process Improvement and Capability Determination) is a software development process standard that outlines the maturity model for system development, software development, management, and business processes. ASPICE defines how to assess the capabilities of a software organization’s level of maturity. An organization seeking compliance to ASPICE needs to follow the guidelines outlined in the PAM (process assessment model) which are discussed in the Automotive SPICE Process Reference Model Process Assessment Model Version 3.1.
Lattix has been successfully used to achieve Automotive SPICE Levels 3, 4, 5, and 6 at several companies.
FDA Medical 62304
Lattix has been successfully used on Medical projects, to help verify the architectural requirements for Class A, B and C Medical devices. Please see our Siemens Healthineers customer case study for more information.