Difference between revisions of "FuSa SIG/Charter"

From Xen
Jump to: navigation, search
(Created page with "<p>Xen Project Functional Safety Special Interest Group</p> <p>Project Charter</p> <h1>Background</h1> <p>Modern safety critical systems such as autonomous vehicles or industr...")
 
m
Line 1: Line 1:
<p>Xen Project Functional Safety Special Interest Group</p>
+
= Background =
<p>Project Charter</p>
 
<h1>Background</h1>
 
<p>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 &ldquo;safe&rdquo; may require reducing their complexity by separating critical and non-critical parts, or implementing functions migration, which in turn can be achieved with system level virtualization. While Xen hypervisor might be the best tool for system virtualization it still is limited in use since there is currently no simple way to certify Xen-based product for Functional Safety requirements - most of them are simply not addressed by community-driven development model and process.</p>
 
<h1>Goal</h1>
 
<p>Create a framework and all required artifacts (documentation, tests, traceability matrices, etc.) that can be used to build and certify safety-critical systems (e.g compliant to IEC61508 or ISO26262) based on mainline Xen hypervisor codebase.</p>
 
<h1>Members</h1>
 
<p>Implementers</p>
 
<ul>
 
<li>ARM (Antonio Priore, Julien Grall, Robin Randhawa)</li>
 
<li>Citrix (George Dunlap, Lars Kurth)</li>
 
<li>EPAM (Artem Mygaiev, Alex Agizim)</li>
 
<li>LF (Kate Stewart)</li>
 
<li>Renesas (Hisao Munakata)</li>
 
<li>Resiltech (Francesco Rossi)</li>
 
<li>Xilinx (Stefano Stabellini)</li>
 
</ul>
 
<p>Assessors</p>
 
<ul>
 
<li>Exida (Piotr Serwa)</li>
 
<li>MIRA (David Ward)</li>
 
<li>TUV Rheinland (Robert Heinen)</li>
 
<li>TUV SUD (Bernhard Nalte, Claudio Gregorio)</li>
 
</ul>
 
<h1>Scope</h1>
 
<p>SIG activities can be represented in several streams:</p>
 
<h3>Safety management system</h3>
 
<p>Definition and implementation for the safety management system that can coexist with generic Xen mainline development.</p>
 
<p><em>Keywords: hazard analysis, safety manual</em></p>
 
<h3>Process to eliminate gaps of community-driven development</h3>
 
<p>Define and implement processes to keep design documentation artifacts (requirements, architecture, design) and corresponding validation &amp; verification artifacts updated without significant changes in existing development process and tools. This may include creating guidelines to keep existing public documentation updated - a change requiring support for all key members of Xen project community (maintainers, committers), as well as retrospective application of defined guidelines to existing codebase. Many of such artifacts can be made public which will benefit the community.</p>
 
<p><em>Keywords: documentation, traceability, testing, dynamic analysis</em></p>
 
<h3>Process for interacting with mainline development community</h3>
 
<p>Define and implement processes to keep a subset of Xen hypervisor codebase compliant without significant impact on generic mainline development. This may include implementing guidelines and changes to coding standard, probably the most painful change requiring support for all key members of Xen project community (maintainers, committers), as well as retrospective application of defined guidelines to existing codebase.</p>
 
<p><em>Keywords: MISRA, fusa clang compiler, code maintainability, code coverage, static analysis</em></p>
 
<h3>Process automation tools</h3>
 
<p>Most of the processes above shall be optimized or fully automated with software tools - either existing or new, FOSS or proprietary.</p>
 
<p><em>Keywords: code minimization tool, impact analysis tool, coverity, qa-verify, osstest</em></p>
 
<h1>Considerations</h1>
 
<p>At the initial stage SIG operate independently from Linux Foundation but this may be changed with time.</p>
 
  
[[Category:Safety Certification/FuSa SIG]]
+
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, or implementing functions migration, which in turn can be achieved with system level virtualization. While Xen hypervisor might be the best tool for system virtualization it still is limited in use since there is currently no simple way to certify Xen-based product for Functional Safety requirements - most of them are simply not addressed by community-driven development model and process.
[[Category:Safety Certification]]
+
 
 +
= Goal =
 +
 
 +
Create a framework and all required artifacts (documentation, tests, traceability matrices, etc.) that can be used to build and certify safety-critical systems (e.g compliant to IEC61508 or ISO26262) based on mainline Xen hypervisor codebase.
 +
 
 +
= Members =
 +
 
 +
Implementers
 +
 
 +
* ARM (Antonio Priore, Julien Grall, Robin Randhawa)
 +
* Citrix (George Dunlap, Lars Kurth)
 +
* EPAM (Artem Mygaiev, Alex Agizim)
 +
* LF (Kate Stewart)
 +
* Renesas (Hisao Munakata)
 +
* Resiltech (Francesco Rossi)
 +
* Xilinx (Stefano Stabellini)
 +
 
 +
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:
 +
 
 +
=== Safety management system ===
 +
 
 +
Definition and implementation for the safety management system that can coexist with generic Xen mainline development.
 +
 
 +
''Keywords: hazard analysis, safety manual''
 +
 
 +
=== Process to eliminate gaps of community-driven development ===
 +
 
 +
Define and implement processes to keep design documentation artifacts (requirements, architecture, design) and corresponding validation & verification artifacts updated without significant changes in existing development process and tools. This may include creating guidelines to keep existing public documentation updated - a change requiring support for all key members of Xen project community (maintainers, committers), as well as retrospective application of defined guidelines to existing codebase. Many of such artifacts can be made public which will benefit the community.
 +
 
 +
''Keywords: documentation, traceability, testing, dynamic analysis''
 +
 
 +
=== Process for interacting with mainline development community ===
 +
 
 +
Define and implement processes to keep a subset of Xen hypervisor codebase compliant without significant impact on generic mainline development. This may include implementing guidelines and changes to coding standard, probably the most painful change requiring support for all key members of Xen project community (maintainers, committers), as well as retrospective application of defined guidelines to existing codebase.
 +
 
 +
''Keywords: MISRA, fusa clang compiler, code maintainability, code coverage, static analysis''
 +
 
 +
=== Process automation tools ===
 +
 
 +
Most of the processes above shall be optimized or fully automated with software tools - either existing or new, FOSS or proprietary.
 +
 
 +
''Keywords: code minimization tool, impact analysis tool, coverity, qa-verify, osstest''
 +
 
 +
= Considerations =
 +
 
 +
At the initial stage SIG operate independently from Linux Foundation but this may be changed with time.
 +
 
 +
[[Category:Safety Certification/FuSa SIG]] [[Category:Safety Certification]]

Revision as of 02:14, 15 May 2019

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, or implementing functions migration, which in turn can be achieved with system level virtualization. While Xen hypervisor might be the best tool for system virtualization it still is limited in use since there is currently no simple way to certify Xen-based product for Functional Safety requirements - most of them are simply not addressed by community-driven development model and process.

Goal

Create a framework and all required artifacts (documentation, tests, traceability matrices, etc.) that can be used to build and certify safety-critical systems (e.g compliant to IEC61508 or ISO26262) based on mainline Xen hypervisor codebase.

Members

Implementers

  • ARM (Antonio Priore, Julien Grall, Robin Randhawa)
  • Citrix (George Dunlap, Lars Kurth)
  • EPAM (Artem Mygaiev, Alex Agizim)
  • LF (Kate Stewart)
  • Renesas (Hisao Munakata)
  • Resiltech (Francesco Rossi)
  • Xilinx (Stefano Stabellini)

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:

Safety management system

Definition and implementation for the safety management system that can coexist with generic Xen mainline development.

Keywords: hazard analysis, safety manual

Process to eliminate gaps of community-driven development

Define and implement processes to keep design documentation artifacts (requirements, architecture, design) and corresponding validation & verification artifacts updated without significant changes in existing development process and tools. This may include creating guidelines to keep existing public documentation updated - a change requiring support for all key members of Xen project community (maintainers, committers), as well as retrospective application of defined guidelines to existing codebase. Many of such artifacts can be made public which will benefit the community.

Keywords: documentation, traceability, testing, dynamic analysis

Process for interacting with mainline development community

Define and implement processes to keep a subset of Xen hypervisor codebase compliant without significant impact on generic mainline development. This may include implementing guidelines and changes to coding standard, probably the most painful change requiring support for all key members of Xen project community (maintainers, committers), as well as retrospective application of defined guidelines to existing codebase.

Keywords: MISRA, fusa clang compiler, code maintainability, code coverage, static analysis

Process automation tools

Most of the processes above shall be optimized or fully automated with software tools - either existing or new, FOSS or proprietary.

Keywords: code minimization tool, impact analysis tool, coverity, qa-verify, osstest

Considerations

At the initial stage SIG operate independently from Linux Foundation but this may be changed with time.