You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Facilitating Certi cation Artefacts Reuse Using Safety Contracts

Fulltext:


Authors:


Note:

Licentiate Research Proposal

Publication Type:

Conference/Workshop Paper

Venue:

International Conference on Software Reuse Doctoral Symposium


Abstract

Safety-critical systems usually need to be certified according a domain-specific safety standard. To reduce the cost and time needed to achieve the safety certification, reuse of certification artefacts together with the corresponding safety-relevant software components is needed. The certification artefacts include safety claims/goals and the supporting evidence that are documented in a safety case. The safety case is required by some safety standards to show that the system is acceptably safe to operate in a given context. Assumption/guarantee contracts can be used to capture the dependencies between a component, including its certification artefacts, and a particular operating context. In this paper we present a research proposal on how safety contracts can be used to facilitate structured reuse of certification-relevant artefacts. More specifically, we explore in which way should such contracts be specified, how can they be derived, and in which way can they be utilised for reuse of safety case argument-fragments and the artefacts those arguments include.

Bibtex

@inproceedings{Sljivo3764,
author = {Irfan Sljivo},
title = {Facilitating Certi cation Artefacts Reuse Using Safety Contracts},
note = {Licentiate Research Proposal},
month = {January},
year = {2015},
booktitle = {International Conference on Software Reuse Doctoral Symposium},
url = {http://www.es.mdh.se/publications/3764-}
}