-
Notifications
You must be signed in to change notification settings - Fork 8
Minutes 26 Sep 2024
Host: Paul Albertella
Participants: Peter Brink, Vivith Parlattaya, Igor Stoppa, Mikel Azkarate
Agenda:
- Publishing OSEP contributions material as 'official' ELISA docs
- Publishing an index of previous workshop presentations
- Fault induction by simulating corruption of data structures
- Avoiding the R word: Expectations, Assertions and Evidence
Discussion
Want to make statements about Linux that we can collectively agree on as ‘ELISA’
Some concern that certain statements were negative
Pete: Stating things as they are, without hiding the challenges is necessary
Igor: Important to publish them in the right order
- Start with the foundational documents
- Paul: Would need to do a review of these
- Pete: need to establish evaluation and acceptance criteria
Publishing previous workshop presentations
- Use GitHub PR as a way of securing author’s permission to publish
- Do not include the PDF in the PR until approved
- May need some corrections / fixes applied before publication
- Define review and approval criteria
- Identify some starting presentations?
Fault induction by simulating data corruption
- Tool to explore failure modes and verify detection
- Can enable us to
Vivith: Focus of our discussions tends to be on ISO 26262. Do we need to look at functional safety standards in other industries?
- Paul: We try to talk in generally applicable terms for all domains, but Pete and I have more familiarity with 26262
- Might be useful to get input from e.g. Aerospace, Chuck Wolber
Paul: Model for thinking about requirements (without using that word!)
https://github.com/elisa-tech/wg-osep/wiki/Model-for-traceability-between-requirements-and-evidence