You are here: Home / RTLWS 1999-2017 / RTLWS Submitted Papers / 
2022-07-03 - 23:12

Dates and Events:

OSADL Articles:

2022-01-13 12:00

Phase #3 of OSADL project on OPC UA PubSub over TSN successfully completed

Another important milestone on the way to interoperable Open Source real-time Ethernet has been reached


2021-02-09 12:00

Open Source OPC UA PubSub over TSN project phase #3 launched

Letter of Intent with call for participation is now available


2016-11-12 12:00

Raspberry Pi and real-time Linux

Let's have a look at the OSADL QA Farm data


2016-09-17 12:00

Preemption latency of real-time Linux systems

How to measure it – and how to fix it, if it's too high?



Real Time Linux Workshops

1999 - 2000 - 2001 - 2002 - 2003 - 2004 - 2005 - 2006 - 2007 - 2008 - 2009 - 2010 - 2011 - 2012 - 2013 - 2014 - 2015

Twelfth Real-Time Linux Workshop on October 25 to 27, in Nairobi, Kenya

FLOSS for safety: Mastering mission critical development with GIT

Andreas Platschek, Nicholas Mc Guire, Georg Schiesser, Thomas Hisch, OpenTech EDV Research GmbH, Austria

Writing code for safety critical systems implies a lot of restrictions and requirements in the software development process. Depending on the field a specific development process has to be followed and fully documented. In order to be compliant with a standard ,e.g. DO-178B, ISO61508, ISO26262, MISRA-C, stringent traceability requirements must be followed allowing to justify the development process itself.

In this paper, we try to give some examples of features of git that are - in our eyes - useful in helping the developers to fulfill the traceability and documentation requirements of safety related development life-cycles. Examples for such techniques are a history for each and every line of code, or the sign-off mechanism, to find out who is responsible for any part of the code base - providing a method to ensure you know who to blame.

These git specific features can even be improved by using git hooks in combination with different tools, including formal methods, and back-end scripting, allowing to fully automate these QA related extensions.

The intention behind all of these techniques is to build a tool-chain for extended traceability [version control] around git, simplifying the verification process.
Although this paper targets safety critical systems in particular, some of the presented techniques may well be suited for enhancing the kernel development as well as for standard user space programing tasks.

[DISCLAIMER:] None of the proposed techniques replaces common sense, they are just a way of improving your code and development process.