Hi,

did my vote and would be happy to present you this topic as suggested below

Will be in US the second week talking on a safety conference

but am willing to do the same as Rob does.

I would like to know more about results of our cooperation and the form

Shall we gather the results in the ELISA-Wiki?

Shall we do scientific publications?

Shall we add something to open source?

Is there a quality agreement (internal review) of our results?

But this can also be done later or via email.

Kind regards,

                Oscar

--

Validas AG

Dr. Oscar Slotosch

Vorstand

mailto:slotosch@...

http://www.validas.de

fon: +49 (0) 89 / 53 88 669-11

fax: +49 (0) 89 / 53 88 669-10

--

Validas AG

Firmensitz: Arnulfstr. 27, D-80335 München

Registergericht: Amtsgericht München HRB 131653

Vorstand: Dr. Oscar Slotosch, Dr. Peter Braun

Aufsichtsratsvorsitzender: Prof. Dr. Dr. h.c. Manfred Broy

Von: devel@... [mailto:devel@...] Im Auftrag von Lukas Bulwahn
Gesendet: Donnerstag, 25. April 2019 13:50
An: devel@...
Betreff: [devel] Suitable Date for ELISA Webinar #1 #poll

A new poll has been created:

Validas' Approach to qualification kits for tools, libraries and SEOOCS compliant to ISO 26262 and IEC 61508
Referee: Dr. Oscar Slotosch, Validas

Agenda:

Recent thoughts and methods how to build a QKit for Linux.

We see three different classes of elements in ISO 26262 and IEC 61508 as part of the “safety architecture”:

• Tools
• Unchanged/pre-existing software components
• Software (SEOOCs)

And we think that Linux requires qualification for elements within all those classes.

So therefore we propose as potential activities for Elisa:

• Description of a process for qualification of Linux and Linux applications
• Safety plan, showing the compliance of the process with ISO 26262 and IEC 61508 (including of checks to be performed)
• qualification of
  • linux tools for
    • compilation, e.g. gcc
    • code coverage measurement, e.g. gcov
    • test automatization, e.g. gtest, gdb
  • Linux libraries , libc, libm, C++stdlibs (as far as needed)
  • Linux components, e.g. kernel, modules
• Provide a qualified tool chain to safely develop applications

The following things we have already achieved and can present you:

• (certified) qualification processes for Tools & Libraries (SEOOCs still open)
• QKit for gcc
• QKit concept for gcov
• QKit for 200 runtime functions of libm, libc
• QKit for QKits (adaptable for linux)

There is much to do, but we do already have parts, plans & visions that we like to share with you.

Poll:

Please let us know which date for this presentation would fit you.

1. 2019-05-06 13:00 UTC
2. 2019-05-07 13:00 UTC
3. 2019-05-08 13:00 UTC
4. 2019-05-09 13:00 UTC
5. 2019-05-10 13:00 UTC
6. 2019-05-13 13:00 UTC
7. 2019-05-14 13:00 UTC
8. 2019-05-15 13:00 UTC
9. 2019-05-16 13:00 UTC
10. 2019-05-17 13:00 UTC

Vote Now

Hi Oskar,

yes, we need to agree on those organisational questions.

My understanding/proposal:

We use github pages as wiki space, so we can create some simple webpages with the content with markdown files. We have it under version control with git and can propose changes with git commits and pull requests.

Scientific publications should also be done to get critical feedback and establish a common state of art.

We publish under CC-BY-SA-2.0. What else would you mean by “adding to open-source”?

Review is done in public for others to know our agreed quality management process. Also, we would like to ask authors to provide their “evidence of competence” (in IEC 61508/ISO 26262 speak) if possible.

Let us understand what activities we would like to start with and then also find the proper organization for that.

It all starts with a common understanding of potential activities and the decisions who wants to work on what.

Best regards,

Lukas

Hi,

did my vote and would be happy to present you this topic as suggested below

Will be in US the second week talking on a safety conference

but am willing to do the same as Rob does.

I would like to know more about results of our cooperation and the form

Shall we gather the results in the ELISA-Wiki?

Shall we do scientific publications?

Shall we add something to open source?

Is there a quality agreement (internal review) of our results?

But this can also be done later or via email.

Kind regards,

                Oscar

--

Validas AG

Dr. Oscar Slotosch

Vorstand

mailto:slotosch@...

http://www.validas.de

fon: +49 (0) 89 / 53 88 669-11

fax: +49 (0) 89 / 53 88 669-10

--

Validas AG

Firmensitz: Arnulfstr. 27, D-80335 München

Registergericht: Amtsgericht München HRB 131653

Vorstand: Dr. Oscar Slotosch, Dr. Peter Braun

Aufsichtsratsvorsitzender: Prof. Dr. Dr. h.c. Manfred Broy

Von: devel@... [mailto:devel@...] Im Auftrag von Lukas Bulwahn
Gesendet: Donnerstag, 25. April 2019 13:50
An: devel@...
Betreff: [devel] Suitable Date for ELISA Webinar #1 #poll

A new poll has been created:

Validas' Approach to qualification kits for tools, libraries and SEOOCS compliant to ISO 26262 and IEC 61508
Referee: Dr. Oscar Slotosch, Validas

Agenda:

Recent thoughts and methods how to build a QKit for Linux.

We see three different classes of elements in ISO 26262 and IEC 61508 as part of the “safety architecture”:

• Tools
• Unchanged/pre-existing software components
• Software (SEOOCs)

And we think that Linux requires qualification for elements within all those classes.

So therefore we propose as potential activities for Elisa:

• Description of a process for qualification of Linux and Linux applications
• Safety plan, showing the compliance of the process with ISO 26262 and IEC 61508 (including of checks to be performed)
• qualification of
  • linux tools for
    • compilation, e.g. gcc
    • code coverage measurement, e.g. gcov
    • test automatization, e.g. gtest, gdb
  • Linux libraries , libc, libm, C++stdlibs (as far as needed)
  • Linux components, e.g. kernel, modules
• Provide a qualified tool chain to safely develop applications

The following things we have already achieved and can present you:

• (certified) qualification processes for Tools & Libraries (SEOOCs still open)
• QKit for gcc
• QKit concept for gcov
• QKit for 200 runtime functions of libm, libc
• QKit for QKits (adaptable for linux)

There is much to do, but we do already have parts, plans & visions that we like to share with you.

Poll:

Please let us know which date for this presentation would fit you.

1. 2019-05-06 13:00 UTC
2. 2019-05-07 13:00 UTC
3. 2019-05-08 13:00 UTC
4. 2019-05-09 13:00 UTC
5. 2019-05-10 13:00 UTC
6. 2019-05-13 13:00 UTC
7. 2019-05-14 13:00 UTC
8. 2019-05-15 13:00 UTC
9. 2019-05-16 13:00 UTC
10. 2019-05-17 13:00 UTC

Vote Now