|
# Project overview
|
|
# Project overview
|
|
|
|
|
|
TODO
|
|
This project sets out to ask questions about the problem of Compliance in software, particularly with regards to Safety Critical Engineering.
|
|
|
|
|
|
|
|
What is the problem of Compliance in software? From a simplified viewpoint: verification against Compliance requirements, as we know it, does not work. It is too bureaucratic and subjective - there is no formal, objective method of guaranteeing that a piece of software will do what it claims it will do, and nothing more or less.
|
|
|
|
|
|
|
|
The number of lines of code in the software used in Safety Critical Engineering is only growing, and until there is an automated process for formal verification of Compliance, the human effort needed to perform this verification will only increase as well. We need to change this, and there currently does not appear to be any work on this in the open domain.
|
|
|
|
|
|
|
|
As a initial objective, we are aiming to complete some research into some of the existing technologies in this field, so that we can create something in the way of a 'toy' or minimal framework for the creation of Trustable Software. We intend for this to then be used, reviewed and critiqued by the wider community, and then built upon.
|
|
|
|
|
|
|
|
At a very high level, we are working on the following principles:
|
|
|
|
- Using a tool to perform compliance validation is more objective, reliable, cheaper and ultimately more trustable than an industry of people performing compliance validation.
|
|
|
|
- Working transparently and having discussions in the open, engaging the wider community, is better than working behind closed doors.
|
|
|
|
|
|
# Standups
|
|
# Standups
|
|
|
|
|
... | | ... | |