FuSa SIG/Charter

Background

Modern safety critical systems such as autonomous vehicles or industrial robots are constantly and rapidly increasing their complexity with cloud-connected and dynamically deployed functions. Keeping such systems “safe” may require reducing their complexity by separating critical and non-critical parts which can be achieved with Xen.

Goal

Xen can be safety-certified: it has been certified in the past by individual companies, and experts groups have confirmed its certifiability after careful analysts of the codebase and contribution processes. However, the burden of the certification process falls on the user. The goal of the Xen FuSa SIG is to reduce this burden by moving upstream Xen closer to safety-certifiability. The Xen FuSa SIG oversees activities such as improving the Xen code quality and producing artifacts (documentation, tests, traceability matrices, etc.) necessary for certifications.

Members

• ARM (Antonio Priore, Bertrand Marquis, Robin Randhawa)
• Citrix (George Dunlap)
• EPAM (Artem Mygaiev, Alex Agizim)
• LF (Kate Stewart)
• Renesas (Hisao Munakata)
• Resiltech (Francesco Rossi)
• AMD (Stefano Stabellini, Ayan Kumar Halder)

Assessors

• Exida (Piotr Serwa)
• MIRA (David Ward)
• TUV Rheinland (Robert Heinen)
• TUV SUD (Bernhard Nalte, Claudio Gregorio)

Scope

SIG activities can be represented in several streams:

Code Quality

Improve Xen code quality and safety. Implement features to improve real-time and reduce interference. Improve Xen coding style and align it with MISRA-C.

Keywords: MISRA, code quality, static analysis, real-time

Documentation

Define and implement guidelines, templates and examples related to requirements, architecture, design and API documentation. Develop a strategy to produce missing documentation and work with the Community Interactions and Processes stream to ensure documentation stays up-to-date and is generated where needed.

Keywords: documentation, requirements, architecture, design, APIs, traceability

Verification Tests

Define and implement guidelines and examples related to the verification of requirements, architecture, design and APIs as required for safety certification. Develop a strategy to produce missing documentation and work with the Community Interactions and Processes stream to ensure documentation stays up-to-date and is generated where needed.

Keywords: traceability, testing, dynamic analysis