Abstract The motivation to have safe products could be as old as the product development itself. The safety of a product is an implicit expectation from almost, perhaps all the stakeholders of any product. In fact, the safety of a product is an obligation even more so than an expectation, going by the requirements of the product liability. In a general context, IEC 61508 covers the aspects to be considered during the development of E/E/PE systems. For functional safety of the road vehicles, ISO26262 defines the requirements of functional safety in the system-, hardware-, and software development. While the standards are comparatively precise for the development phases like verification and validation, the requirements for the design phase are more generic, leaving the details very much to the implementer. For a design to be functionally safe, the standards requires to avoid complexity. The use of formal methods and principles like stateless design are encouraged. The examples given in the standards are either very domain specific like Calculus of Communicating Systems (CCS) or are difficult to apply like the formal language Z.
SCODE: Designing and verifying functionally safe systems in conformance to IEC61508 and ISO26262
2018-01-01
12 pages
Aufsatz/Kapitel (Buch)
Elektronische Ressource
Englisch
Managing Functional Safety (ISO26262) in Projects
SAE Technical Papers | 2017
|Systems safety engineering nach ISO26262
Kraftfahrwesen | 2013
|ISO26262 in der Getriebeentwicklung von Hybridfahrzeugen und Elektrofahrzeugen
Kraftfahrwesen | 2014
|Application of IEC61508 SIL Recommendations to a Control-model Based Lifecycle
SAE Technical Papers | 2006
|10 Steps to ISO26262-compliant Model-based Software Components
SAE Technical Papers | 2015
|