Course Code: iso26262part6
Duration: 7 hours
Prerequisites:
  • 具有软件或系统开发经验

观众

  • 软件开发人员
  • 系统和安全工程师
  • Computer 和电气工程师
  • 安全经理
  • 工程经理
Overview:

ISO 26262是汽车行业电气/电子系统功能安全的国际标准。 第六部分专注于系统设计和实施的软件方面。

由教练领导的现场培训(在线或在线)针对汽车专业人士,希望在他们的组织内实施ISO 26262标准。

在本研讨会结束后,参与者将能够:

  • 建立完整和一致的软件安全要求。
  • 分析安全的软件架构,包括自由独立(FFI)分析。
  • 构建使用文档工具提高软件质量的过程。
  • 计划并执行软件和系统的集成测试策略。
  • 实施和测试安全应用程序的软件单位。

课程格式

  • 互动讲座和讨论。
  • 很多练习和练习。
  • 在现场实验室环境中进行手动实施。

课程定制选项

  • 要申请此课程的定制培训,请联系我们安排。
Course Outline:

介绍

风险、ASIL 和安全概念

软件开发流程

软件架构设计

软件安全要求 (SSR)

软件安全分析(FMEA、FTA等)

基于模型的开发

工具鉴定

组件鉴定

软件集成

软件验证报告

嵌入式 Software Testing

摘要和后续步骤

Sites Published:

United Arab Emirates - ISO 26262 Part 6: Safe Software Development

Qatar - ISO 26262 Part 6: Safe Software Development

Egypt - ISO 26262 Part 6: Safe Software Development

Saudi Arabia - ISO 26262 Part 6: Safe Software Development

South Africa - ISO 26262 Part 6: Safe Software Development

Brasil - ISO 26262 Part 6: Safe Software Development

Canada - ISO 26262 Part 6: Safe Software Development

中国 - ISO 26262 Part 6: Safe Software Development

香港 - ISO 26262 Part 6: Safe Software Development

澳門 - ISO 26262 Part 6: Safe Software Development

台灣 - ISO 26262 Part 6: Safe Software Development

USA - ISO 26262 Part 6: Safe Software Development

Czech Republic - ISO 26262 Part 6: Safe Software Development

Lithuania - ISO 26262 Part 6: Safe Software Development

Norway - ISO 26262 Part 6: Safe Software Development

Sverige - ISO 26262 Part 6: Safe Software Development

Türkiye - ISO 26262 Part 6: Safe Software Development

Belgique - ISO 26262 Part 6: Safe Software Development

日本 - ISO 26262 Part 6: Safe Software Development

Australia - ISO 26262 Part 6: Safe Software Development

Malaysia - ISO 26262 Part 6: Safe Software Development

New Zealand - ISO 26262 Part 6: Safe Software Development

Philippines - ISO 26262 Part 6: Safe Software Development

Singapore - ISO 26262 Part 6: Safe Software Development

Thailand - ISO 26262 Part 6: Safe Software Development

Vietnam - ISO 26262 Part 6: Safe Software Development

India - ISO 26262 Part 6: Safe Software Development

Argentina - ISO 26262 Part 6: Safe Software Development

Chile - ISO 26262 Part 6: Safe Software Development

Costa Rica - ISO 26262 Part 6: Safe Software Development

Ecuador - ISO 26262 Part 6: Safe Software Development

Guatemala - ISO 26262 Part 6: Safe Software Development

Colombia - ISO 26262 Part 6: Safe Software Development

México - ISO 26262 Part 6: Safe Software Development

Panama - ISO 26262 Part 6: Safe Software Development

Peru - ISO 26262 Part 6: Safe Software Development

Uruguay - ISO 26262 Part 6: Safe Software Development

Venezuela - ISO 26262 Part 6: Safe Software Development

Polska - ISO 26262 Part 6: Safe Software Development

United Kingdom - ISO 26262 Part 6: Safe Software Development

South Korea - ISO 26262 Part 6: Safe Software Development

Pakistan - ISO 26262 Part 6: Safe Software Development

Sri Lanka - ISO 26262 Part 6: Safe Software Development

Bolivia - ISO 26262 Part 6: Safe Software Development

Indonesia - ISO 26262 Part 6: Safe Software Development

Kazakhstan - ISO 26262 Part 6: Safe Software Development

Morocco - ISO 26262 Part 6: Safe Software Development

Tunisia - ISO 26262 Part 6: Safe Software Development

Kuwait - ISO 26262 Part 6: Safe Software Development

Oman - ISO 26262 Part 6: Safe Software Development

Slovakia - ISO 26262 Part 6: Safe Software Development

Kenya - ISO 26262 Part 6: Safe Software Development

Nigeria - ISO 26262 Part 6: Safe Software Development

Botswana - ISO 26262 Part 6: Safe Software Development

Bhutan - ISO 26262 Part 6: Safe Software Development

Nepal - ISO 26262 Part 6: Safe Software Development

Uzbekistan - ISO 26262 Part 6: Safe Software Development