5. What ISO 26262 means for Automotive
All Automotive System development for Electronic and Electrical (E&E) components need to
comply to ISO 26262
Consists of 10 parts
Due to the reuse of a large number of existing elements and pre-existing vehicle architectures the development
cycle is seldom a pure top down V-cycle
ISO 26262 development goes across organizational boundaries, an ISO 26262 project is unlikely to be in just one organization
Means that the safety-lifecycle must be adaptable and flexible
Heavily influenced by the V-model
Made more modular
1 Vocabulary
2 Management of functional safety
10 Guideline on ISO 26262 (informative)
9 ASIL-oriented and safety-oriented analysis
8 Supporting processes
3 Concept
phase
4 Product development on system level
5 Hardware
development
6 Software
development
7
Production
and
operation
ISO 26262
4.5-4.7
Systems Engineering
4.8-4.11
Systems Integration & test
10. 10
User Reqts Technical Reqts Test CasesDesign
ContextRequirementsBrowser
End-to-end visual validation in a single view
Writing Requirements within Context
合併文檔和電子表格視圖
簡單,直觀的界面,方便採
用
歷史和基線
解決正確的問題,因為需求在任何時候都是可見的
Input and output from/to various
common formats
IBM Rational DOORS
管理整個生命週期和跨學科的所有要求
10
13. 13
DOORS template for ISO 26262
Capture Severity, Probability and
Controllability attributes
Automatically determines ASIL
Developing requirements module
structure to capture relationships
between
Stakeholder (Item Definition)
Requirements
Functional Safety Requirements
Technical Safety Requirements
System Safety Requirements
HW and SW safety requirements
Automatic propagation through Safety
Requirement Hierarchy of ASIL
Qualifying DOORS 9.5 with TüV for use
as an ISO 26262 tool
14. Youtobe Link for IBM DOORS
IBM Doors Getting Started
IBM Rational DOORS: Hierarchy of objects
IBM Rational DOORS: Attributes
IBM Rational DOORS: Linking and traceability
IBM Rational DOORS for Regulatory Audits and Compliance
…..
14
15. Contact
Jason Lin (林裕隆) , LINYL@tw.ibm.com
Allen Tsai (蔡宗倫), ALLENT@tw.ibm.com
Randy Lin, randylin@tw.ibm.com
15
Explain difference between Requirements for Programs, Projects, Products, Systems and Systems of Systems.
Programs are originated from business needs and from the higher-level Business Processes as shown on page 12. For example in automotive a new vehicle platform development is managed as a “Program”
Our solution is “ensuring end-to-end traceability, from ideas, requirement and feature definitions, product/system specifications, models, down to mechanic, electric/electronic and embedded software implementation, test and maintenance”.
Traceability as a key characteristic of a good RE process!
Again: R. Engineering = R. Definition + Management + a lot of other specific activities like trade-off analysis, change management, etc.
The four arrows “Ideas”, “Analysis”, “Implementation” and “Test&Maintenance” are just 4 exemplarily phases of any development project.