Requirements & Safety Traceability
Use Visure to connect requirements, hazards/risks, tests, change and evidence.
Connect automotive requirements, safety and cybersecurity traceability, software design verification, C/C++ testing, coverage, release evidence and embedded security technologies.
Capabilities and terminology aligned to the current partner portfolio and target application.
Use Visure to connect requirements, hazards/risks, tests, change and evidence.
Use Dezyne where component interactions and concurrency justify formal design verification.
Use C/C++test or C/C++test CT for static analysis, unit testing, coverage, requirements traceability and compliance reporting.
Use DTP to consolidate testing and coverage information across releases.
Apply security-oriented static-analysis and coding-standard workflows.
Use wolfSSL technologies for secure communication, cryptography and secure boot where the ECU/device architecture requires them.
Relevant standards, coding guidelines and assurance frameworks for the technology and its application areas.
Industry connections are included where the technology addresses a defined engineering, verification or product-security requirement.
Connect the technology with the existing engineering environment, lifecycle tools, CI/CD platform and target architecture.
Visure ↔ Jira / Azure DevOps / DOORS / MBSE
C/C++test / C/C++test CT ↔ CI/CD / DTP
wolfSSL ↔ MCU / RTOS / hardware security