[SystemSafety] A Fire Code for Software?

[Andrew Banks]

Hi Steve

 

And here is the rub:

 

>> My definition of "model based" involves creating and maintaining precise
specifications of semantics:

>> policies that need to be enforced and processes that need to be carried
out. 

 

It is the absence of this up-front work that is so prevalent in software
(and systems-) engineering. even in formal development environments,
engineers need to "get on with it" and let the requirements catch up.  Then
throw in the paradigm shift to more Agile methods and it gets even more
unpredictable.

 

But The Authorities seem to not care: Eg in the automotive world, despite
standards such as ISO 26262 there is no statutory requirement to follow a
formal development process. only "conformity of production" matters - and
the type approval process doesn't even mention the existence of software (or
involve any checking of how it came into being), and just concerns itself
with the physical characteristics of the vehicle.

 

Compare with civil engineering, where the detailed plans form part of the
planning process, and implementation is controlled by strict building
regulations, and independently monitored - and all components have to comply
with appropriate standards.

 

 

Regards

Andrew

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.techfak.uni-bielefeld.de/mailman/private/systemsafety/attachments/20180308/373fee37/attachment-0001.html>