All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Understanding MIL-STD-882E Software Control Levels for Safety Classification

By

ibobev

5mo ago· 2 min readenInsight

Summary

The article explains the MIL-STD-882E standard for software control levels, which categorizes software based on how dangerous it can be based on its responsibilities. The standard simplifies to four levels, with the most alarming being when software has direct control of something immediately dangerous if it malfunctions. The next level includes either direct control with a delay before danger occurs, or other scenarios where software can cause harm indirectly.

Key quotes

· 3 pulled
The mil-std-882e standard specifies levels of software control, i.e. how dangerous the software can be based on what it is responsible for.
The most alarming case is when the software has direct control of something that can be immediately dangerous if the software does the wrong thing.
Still dangerous, but slightly less so is either (a) when the software has direct control, but there is a delay between when it does the wrong thing and when it becomes dangerous; or (b)
Snippet from the RSS feed

You might also wanna read