Introduction to Sassur 2012

Alejandra Ruiz, Tim P. Kelly, Mehrdad Sabetzadeh, Didier Van Den Abeele

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Safety assurance and certification are amongst the most expensive and time-consuming tasks in the development of safety-critical systems. The increasing complexity and size of these systems combined with their growing market demand requires the industry to implement a coherent reuse strategy. A key difficulty appears when trying to reuse products from one application domain in another, because different domains are subject to different safety regulations. Subsequently, for a reused product, the full safety assurance and certification process has to be applied, just as for a new product. This reduces the return on investment of such reuse. Further, market trends strongly suggest that many future safety-critical systems will be comprised of heterogeneous, dynamic coalitions of systems of systems. For this type of systems, it is crucial to develop sound strategies that would allow safety assurance and certification to be done compositionally.

Original languageEnglish
Title of host publicationComputer Safety, Reliability, and Security - SAFECOMP 2012 Workshops
Subtitle of host publicationSassur, ASCoMS, DESEC4LCCI, ERCIM/EWICS, IWDE, Proceedings
Pages3-7
Number of pages5
DOIs
Publication statusPublished - 2012
EventWorkshop on Computer Safety, Reliability, and Security, SAFECOMP 2012 - Magdeburg, Germany
Duration: 25 Sept 201228 Sept 2012

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume7613 LNCS
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

ConferenceWorkshop on Computer Safety, Reliability, and Security, SAFECOMP 2012
Country/TerritoryGermany
CityMagdeburg
Period25/09/1228/09/12

Fingerprint

Dive into the research topics of 'Introduction to Sassur 2012'. Together they form a unique fingerprint.

Cite this