blocks|key|428878|text|上面的Aonix链接是一个很好的基本推理链接。如果您想要了解特定标准如何工作的示例，可以在google上搜索以下内容：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|428879|428880|IEC61508：“电气/电子/可编程电子安全相关系统(E/E/PES)的功能安全”。在各种地段特定标准中引用的基础标准。This+IEC+page是一个很好的起点。第61508-3部分是关于software.|unordered-list-item|offset|length|428881|DO-178B:航空电子标准的，该标准的范围与software|428882|IEC60601-1-4:类似，但对standards)|428883|EN5012x:处理“可编程电气医疗系统”的看法略有不同(standards)|428884|EN5012x:+IEC61508专用标准60601系列的一部分-+50128是关于软件的。|428885|428886|entityMap|0|LINK|mutability|MUTABLE|url|http://www.iec.ch/zone/fsafety/fsafety_entry.htm^0|0|0|1P|D|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|10|8|@]|9|@$F|11|G|12|1|13]]|A|$]]|$1|H|3|I|5|E|7|14|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|E|7|16|8|@]|9|@]|A|$]]|$1|N|3|O|5|E|7|17|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

The Aonix link above is a good one for the basic reasoning. If you want examples of how particular standards work, you can google for the following:

<ul>
<li>IEC61508: “Functional safety of electrical / electronic / programmable electronic safety-related systems (E/E/PES)”. Base standard that is referenced in various sector specific standards. <a href="http://www.iec.ch/zone/fsafety/fsafety_entry.htm" rel="noreferrer">This IEC page</a> is a good starting point. Part 61508-3 is about software.</li>
<li>DO-178B: Avionics standard with similar scope as IEC61508 that takes a slightly different view on software</li>
<li>IEC60601-1-4: Deals with "Programmable electrical medical systems" (Part of the 60601 series of standards)</li>
<li>EN5012x: Railway specific standards - 50128 is about software.</li>
</ul>

blocks|key|4210179|text|不同的行业有不同的标准。例如飞机和机器人技术。在一些新的行业中，标准仍在不断发展，例如外科机器人。仍然有一些共同的元素。第一个是冗余。我和工业机器人打交道。对于速度控制等关键项目，我们在两个不同的控制器上使用三种不同的计算。对于紧急停止系统，我们使用双电路，每个红色的e-stop按钮背后都有两个物理开关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4210180|我以前在飞机上工作。在飞机自动驾驶仪上，通常有两台甚至三台独立的计算机进行计算和比较结果。|4210181|这样做的目的是防止任何单一的故障导致系统不安全。|4210182|您需要查看管理您正在工作的领域的规则和法规，以了解法律要求是什么，但您必须确保整个系统的安全。|4210183|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Different industries have different standards. Aircraft and robotics for example. Standards are still evolving in some new industries, such as surgical robots. Still there are some common elements. The first is redundancy. I work with industrial robots. For critical items such as speed control, we use three different calculations on two different controllers. For emergency stop systems we use dual circuits, every red e-stop button has two physical switches behind it. 

I used to work on aircraft. On aircraft autopilots there are often two or even three separate computers doing the calculations and comparing results.

The goal is to prevent any single failure from making the system unsafe. 

You need to look at the rules and regulations that govern the area you are working in to see what the legal requirements are, but you have to make the entire system safe.

blocks|key|2744512|text|MISRA是汽车行业遵循的标准，但它是一个编码标准，以确保操作的正确性和可移植性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2744513|您需要阅读Therac+accidents以了解此问题的复杂性。|offset|length|2744514|此外，NASA和军事文件广泛可用，并讨论了允许确定系统安全性的编码标准。|2744515|-Adam|2744516|entityMap|0|LINK|mutability|MUTABLE|url|http://courses.cs.vt.edu/~cs3604/lib/Therac_25/Therac_1.html^0|0|5|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

MISRA is the standard followed in the automotive industry, but it's a coding standard to ensure correctness of operation and portability.

You need to read up on the <a href="http://courses.cs.vt.edu/~cs3604/lib/Therac_25/Therac_1.html" rel="nofollow noreferrer">Therac accidents</a> to understand the complexity of this issue.

Also, NASA and military documents are widely available and discuss standards for coding that allow determination of safety of the system.

-Adam

blocks|key|815111|text|方法因领域而异。(抱歉，我只对1个链接进行了评分...)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|815112|航空电子设备:+DO-178B：(参见维基百科)|815113|信息安全通用标准(参见通用标准门户网站)|815114|FDA控制医疗设备的软件(想想X光机)+http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/default.htm|offset|length|815115|英国约克大学的安全关键邮件列表(+UK+)是一个很好的资源，最近那里讨论了如何将SIL标准(参见关于SIL标准的维基百科)应用于软件系统。|815116|entityMap|0|LINK|mutability|MUTABLE|url|http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/default.htm^0|0|0|0|K|2J|0|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$H|X|I|Y|1|Z]]|A|$]]|$1|J|3|K|5|6|7|10|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

Approaches vary by field. (sorry, I only rate 1 link...)

Avionics:
DO-178B:
(see wikipedia)

Information Security
The Common Criteria
(see the Common Criteria Portal website)

The FDA controls software for medical devices (think X-ray machines)
<a href="http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/default.htm" rel="nofollow noreferrer">http://www.fda.gov/medicaldevices/deviceregulationandguidance/guidancedocuments/default.htm</a>

The safety-critical mailing list (UK) at U of York in the UK is an excellent resource
There has been discussion there recently of how to
apply the SIL standards 
(see wikipedia on SIL standards)
to software systems.

blocks|key|4210124|text|这不是一个安全的标准，但读一段时间的comp.risks就会发现你需要努力预防的那种问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4210125|(“计算机相关风险”这本书也很不错。)|4210126|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Not a saftey standard, but reading comp.risks for a while will show the kind of problems you will need to work hard to prevent.

(The book, "Computer Related Risks" is very good as well.)

blocks|key|808798|text|软件应该永远不会运行一个可能会伤害人的系统。唯一可能(而且仍然值得怀疑)的情况是，当使用专门为安全设计的safety+reliable+PLC时，这可能是错误的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|808799|您应该了解以下内容：|808800|808801|SIL+4|unordered-list-item|808802|Category+3|808803|808804|entityMap|0|LINK|mutability|MUTABLE|url|http://www2.sea.siemens.com/Products/Automation/Safety-Integrated/Safety-Integrated.htm|1|http://www.jokabsafetyna.com/products/safetyrelay/ChoiceSafetyCategory.html|2^0|1G|J|0|0|0|0|0|5|1|0|0|A|2|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|13|8|@]|9|@$A|14|B|15|1|16]]|C|$]]|$1|J|3|K|5|I|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|1C|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]|W|$5|P|Q|R|C|$S|V]]]]

Software should never run a system that could injure someone. The only possible (and still questionable) time this might be false is when using a <a href="http://www2.sea.siemens.com/Products/Automation/Safety-Integrated/Safety-Integrated.htm" rel="nofollow noreferrer">safety reliable PLC</a> which is specially engineered for safety.

You should look into:

<ul>
<li><a href="http://www.jokabsafetyna.com/products/safetyrelay/ChoiceSafetyCategory.html" rel="nofollow noreferrer">SIL 4</a></li>
<li><a href="http://www.jokabsafetyna.com/products/safetyrelay/ChoiceSafetyCategory.html" rel="nofollow noreferrer">Category 3</a></li>
</ul>

What industry known software safety standards has anyone had experience in having to adhere to while developing software that is involved in controlling a device/system that has potential to harm the individuals using it?

Software Safety Standards

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在开发涉及控制潜在危害使用人员的设备/系统的软件时，任何人都有过必须遵守哪些行业已知的软件安全标准的经验？

问软件安全标准
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问软件安全标准EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问软件安全标准
EN