首页> 外文会议>International system safety conference >Convergence: Aligning the Methods and Tools of Software Safety Analysis with Those of the Software Development Process
【24h】

Convergence: Aligning the Methods and Tools of Software Safety Analysis with Those of the Software Development Process

机译:收敛性:对齐软件安全分析的方法和工具与软件开发过程的方法和工具

获取原文

摘要

Experience with the Software segment of the System Safety Process over the past fifteen years is punctuated with the maturation of the analysis process, development and application of specialized or customized tools, and definition of a set of preferred/effective deliverables. Codification of our process and the underlying power to drive program expenditures on the software and system safety process reached a peak in MIL-STD-882C with it’s clearly defined process, requirements, and deliverables. The resulting “Safety Flag” provided the safety professional with a highly effective tool to force attention on to hazards, risks, and/or major system/software concerns. However, reliance on this “Flag” often fosters an “Us against Them” relationship with the design and development team. In an effort to avoid this polarization, to be “part of the process” rather than “part of the problem”, experience has shown that tailoring the software safety process, analysis tools, and deliverables to each program has significantly improved design/analysis integration. Additionally, if applied at the earliest stages of the design development process, the safety analysis can begin to establish relationships with the key designers that allow the safety analysis to have a maximum impact on the design/implementation. The paper will highlight some of the tools utilized by our group which have resulted in favorable experiences with a number of software intensive development programs across a diverse spectrum of the defense market segment. Systems will include aircraft flight control, mobile artillery, spacecraft display, and missile defense systems. Examples of tools and techniques (deliverables in many cases) customized to fit the individual programs will be demonstrated. Lessons learned will be presented and a “roadmap” for continued convergence of the software safety analysis and software development processes suggested.
机译:在过去的十五年中,系统安全过程的软件段的经验是在专业或定制工具的分析过程,开发和应用的成熟,以及一套首选/有效可交付成果的定义。我们的进程和潜在权力的编写方法以及在软件和系统安全过程上驱动程序支出的潜在权力在MIL-STD-882C中达到了峰值,其中有明确的过程,要求和可交付成果。由此产生的“安全标志”为安全专业提供了一个高效的工具,强迫注意危害,风险和/或主要系统/软件问题。然而,依赖于这个“旗帜”经常与设计和开发团队有关“我们反对他们”的关系。为了避免这种极化,成为“过程的一部分”而不是“部分问题”,经验表明,对每个程序定制软件安全过程,分析工具和可交付成果具有显着改善的设计/分析集成。此外,如果在设计开发过程的最早阶段应用,安全性分析可以开始与允许安全分析对设计/实施产生最大影响的关键设计人员建立关系。本文将突出我们集团利用的一些工具,这些工具导致了跨越国防集团各种软件强化发展计划的优惠经验。系统将包括飞机飞行控制,移动炮兵,航天器显示器和导弹防御系统。将展示根据以适应各个计划的工具和技术(可交付成果)的示例将得到证明。展示的经验教训以及“路线图”,用于持续融合软件安全分析和软件开发过程。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号