Understanding zserio functional safety features

ndsev / zserio

zero sugar, zero fat, zero serialization overhead

https://zserio.org/

BSD 3-Clause "New" or "Revised" License

105 stars 27 forks source link

Understanding zserio functional safety features #467

Open MisterGC opened 1 year ago

MisterGC commented 1 year ago

ASIL refers to Automotive Safety Integrity Level. It is a risk classification system defined by the ISO 26262 standard for the functional safety of road vehicles.

zserio has been prepared to be used for usage in road vehicles with functional safety requirements, but there is a lack of available information.

Please document the following aspects:

Summary: What does ASIL-ready mean in the scope zserio?
Which of the AUTOSAR C++14 Guidelines have been covered?
Are there missing aspects? Corresponding issues are created/reflected.
How does memory allocation customization work?
Test coverage, what, where and how to run them? (there should be test reports for each release)

mikir commented 1 year ago

Regarding functional safety features, consider to investigate the possibility of usage of static analysis tool at GitHub which can check Autosar C++ standard. More info is available here: https://github.blog/2022-06-20-adding-support-for-coding-standards-autosar-c-and-cert-c/.

q16063661 commented 12 months ago

Do you have the code for ASIL or DAL?

mikir commented 12 months ago

We focus only on ASIL.

q16063661 commented 12 months ago

I want to find some code about ASIL.Could you help me?

mikir commented 12 months ago

I am afraid that I don't understand which code do you mean. Please, describe your problem more properly.

q16063661 commented 12 months ago

For example this article 'Ant colony algorithm for automotive safety integrity levelallocation'.I want to implement the ASIL from the article in MATLAB or Python.

mikir commented 9 months ago

We have added dedicated Functional Safety section into C++ README.

It covers as well clang-tidy usage and exceptions during reading.

For time being, this issue will be put to the backlog until explicit request for more comprehensive documentation arises.