International Workshop on Critical Software Component Reusability and Certification across Domains


This workshop addresses the interaction between component-based software reuse and safety, together with its implications on certification. Safety concerns the prevention of accidents, and can be characterized as an "emergent property that arises at the system level when components are operating together". Systematic reuse of software components in critical environments would benefit from a solid and rich certification framework. Compositional certification is a challenging approach currently under study to standardize and promote software components reuse. When safety is at stake, cross domain reuse and certification become particularly complex and challenging issues: paving the way for a suitable certification framework requires a thorough discussion among all stakeholders.

Workshop Goal

The goal of the workshop is to determine which aspects of component reuse affect safety, and to what extent cross domain reuse can have an impact on safety issues and composition. Component certification and safety parameters must be considered from a cross-domain point of view in order to gain the maximum benefit from the definition of a suitable certification paradigm. The workshop aims to bring together practitioners from software reuse and certification domains to exchange experience, discuss current and emerging problems, and construct an agenda for future work in this area.

Topics of Interest

  • How can safety-related aspects of components be specified?
  • How is reuse currently addressed in the safety international standards?
  • What are the legal aspects of reuse and safety?
  • To what extent can software reuse be based on already established (certified) properties?
  • How can we enable composable qualification and certification of software across domains?
  • What new processes could be defined to ensure components that are certifiable across domains?
  • Reuse of proven software components may increase reliability, but has little or no effect on safety
  • Specific hazards of new implementation may not have been considered