2011 12 6PTC Live TechForum TOKYO manji@rd.denso.co.jp 1/ 52 1949 12 16 1,874 ( ) 1 9,457 3 1,315 ( ) 38,318 123,165 ( ) 2011 3 31 Gr. Gr. Gr. Gr. Gr. PF
2/ 52 1 2 3 4PMT 5 Integrity 6 7 8 1/2 3/ 52 OEM OEM
2/2 4/ 52 1/2 5/ 52 ISO 26262 ( )
2/2 6/ 52 ISO26262 IP SPF 7/ 52 1 2 3 4PMT 5 Integrity 6 7 8
ISO26262 8/ 52 1. 2-5 Overall safety management 3. 3-5 item definition 3-6 Initiation of the safety lifecycle 3-7 Hazard analysis and risk assessment 3-8 Functional safety concept 4-5 Initiation of product development at the system level 4-6 Specification of the technical safety requirements 4-7 System design 5. 5-5 Initiation of product development at the hardware level 5-6 Specification of hardware safety requirements 5-7 Hardware design 2. 2-6 Safety management during item develoopment 4. 4-11 Release for prodcution 4-10 Functional safety assessment 4-9 Safety valication 4-8 Item integration and testing 6. 6-5 Initiation of product development at the software levelel 6-6 Specification of software safety requirements ents 6-7 Software architectural design 2-7 Safety managemnet after release for production 7. 7-5 Production 7-6 Operation, Service and decommissioning 5-8 Hardware architectural metrics 5-9 Evaluation ation of violation of the safety goal due to random HW failures 5-10 Hardware integration and testing 6-8 Software unit design and implementation 6-9 Software unit testing 6-10 Software integration and testing 6-11 Software verificationication 8-5 Interfaces within distributed developments 8-6 Overall management of safety requirements 8-7 Configuration management 8-8 Change management 8-9 Verification 9-5 Requirements decomposition with respect to ASIL tailoring 9-6 Criteria for coexistence of elements 8. 8-10 Documentation 8-11 Qualification of software tools 8-12 Qualification of software components 8-13 Qualification of hardware components 8-14 Proven in use argument 9. 9-7 Analysis of dependenet failures 9-8 Safety analysis 10. IBM PLM/ALM PLM Product Lifecycle Management ALM Application Lifecycle Management 9/ 52 PLM ALM PTC PTC/MKS IBM SERENA Microsoft Windchill Integrity DOORS RTC PVCS VSS QM
PLMALM 10/ 52 PLM ALM Assy XXXXXX-0000 3 2 B A 1 Sub-Assy XXXXXX-0010 11/ 52 PLM PLM ALM PLM PLM ALM PLM PLM PLM ALM PLM ALM PLM
13/ 52 1 2 3 4PMT 5 Integrity 6 7 8 ISO26262 14/ 52 1. 2-5 Overall safety management 3. 3-5 item definition 3-6 Initiation of the safety lifecycle 3-7 Hazard analysis and risk assessment 3-8 Functional safety concept 4-5 Initiation of product development at the system level 4-6 Specification of the technical safety requirements 4-7 System design 5. 5-5 Initiation of product development at the hardware level 5-6 Specification of hardware safety requirements 5-7 Hardware design 2. 2-6 Safety management during item develoopment 4. 4-11 Release for prodcution 4-10 Functional safety assessment 4-9 Safety valication 4-8 Item integration and testing 6. 6-5 Initiation of product development at the software level el 6-6 Specification of software safety requirements ents 6-7 Software architectural design 2-7 Safety managemnet after release for production 7. 7-5 Production 7-6 Operation, Service and decommissioning Automotive-SPICE 5-8 Hardware architectural metrics 5-9 Evaluation ation of violation of the safety goal due to random HW failures 5-10 Hardware integration and testing 6-8 Software unit design and implementation 6-9 Software unit testing 6-10 Software integration and testing 6-11 Software verification ication 8-5 Interfaces within distributed developments 8-6 Overall management of safety requirements 8-7 Configuration management 8-8 Change management 8-9 Verification 9-5 Requirements decomposition with respect to ASIL tailoring 9-6 Criteria for coexistence of elements 8. 8-10 Documentation 8-11 Qualification of software tools 8-12 Qualification of software components 8-13 Qualification of hardware components 8-14 Proven in use argument 9. 9-7 Analysis of dependenet failures 9-8 Safety analysis 10. IBM
15/ 52 Automotive SPICE Automotive SPICE KUGLER MAAB CIE 16/ 52 1 2 80 2020 80
17/ 52 1 2 3 4PMT 5 Integrity 6 7 8 18/ 52 models for software architecture, functional network, hardware topology functional behavior model implementation model manual C-code development model based development architectural development dspace
19/ 52 C OEM/ 24/ 52 Process Methods Tools
PMT 25/ 52 Process Automotive SPICE Methods V&V Validation and Verification Tools 28/ 52 1 2 3 4PMT 5 Integrity 6 7 8
29/ 52 2003Eclipse 2008Eclipse OSS 2009Eclipse OSS CDT SubVersion Mylyn Trac Bugzilla JWT PDE Pleiades Eclipse OSS Automotive SPICE 2011MKS Integrity ASIL Automotive SPICE Integrity 30/ 52 Integrity UP IBM 1 1 2 2
FMEA FMEA FMEA Integrity 31/ 52 Integrity IBM Excel 32/ 52 FMEA
33/ 52 Integrity Integrity 34/ 52 Integrity
Safety Manual 35/ 52 FSA 36/ 52 OS Firewall
37/ 52 1 2 3 4PMT 5 Integrity 6 7 8 38/ 52 ReqIF OMG RIF HIS http://www.omg.org/spec/reqif/ http://www.automotive-his.de/rif/doku.php?id=welcomeeng
39/ 52 ReqIF http://www.omg.org/spec/reqif/1.0.1/pdf 40/ 52 DOORS RIF/Req IF Team Center MIIP Integrity Word Gateway
JasParWG 1 RIF/ReqIF 2 Office2003 3 1 RIF ReqIF 2 3 4 45/ 52 Word2003 Word2007 DOORS XXXXX JasPar Integrity TeamCenter Rational Team Concert YYYYY 46/ 52 PLM ALM PTC PTC/MKS IBM SERENA Microsoft Windchill ALM PLM Integrity DOORS RTC PVCS VSS QM
47/ 52 1 2 3 4PMT 5 Integrity 6 7 8 Matlab Integration 1/2 Matlab IntegrationSimulink 48/ 52 http://www.mks.com/images/modelingscreenshot.png
Matlab Integration 2/2 49/ 52 Simulink Requirements Model Tests Code 50/ 52 HILS AutomationDesk Matlab/Simulink TargetLink 49
51/ 52 1 2 3 4PMT 5 Integrity 6 7 8 52/ 52 PMT Process Automotive SPICE Method V&V Tool PTCIntegrity PTC