mdh.sePublications
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
The Nature and Content of Safety Contracts: Challenges and Suggestions for a Way Forward
Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems.ORCID iD: 0000-0002-6352-4368
University of York, UK.ORCID iD: 0000-0003-2415-8219
2014 (English)In: Proceedings of IEEE Pacific Rim International Symposium on Dependable Computing, PRDC, 2014, p. 135-144Conference paper, Published paper (Refereed)
Abstract [en]

Software engineering researchers have extensively explored the reuse of components at source-code level. Contracts explicitly describe component behaviour, reducing development risk by exposing potential incompatibilities early in the development process. But to benefit fully from reuse, developers of safety-critical systems must also reuse safety evidence. Full reuse would require both extending the existing notion of component contracts to cover safety properties and using these contracts in both component selection and system certification. This is not as simple as it first appears. Much of the review, analysis, and test evidence developers provide during certification is system-specific. This makes it difficult to define safety contracts that facilitate both selecting components to reuse and certifying systems. In this paper, we explore the definition and use of safety contracts, identify challenges to component-based software reuse safety-critical systems, present examples to illustrate several key difficulties, and discuss potential solutions to these problems.

Place, publisher, year, edition, pages
2014. p. 135-144
Keyword [en]
Component-based software engineering, safety, contracts, safety arguments, modular safety case
National Category
Electrical Engineering, Electronic Engineering, Information Engineering
Identifiers
URN: urn:nbn:se:mdh:diva-26785DOI: 10.1109/PRDC.2014.24ISI: 000356602600019Scopus ID: 2-s2.0-84919476333ISBN: 9781479964741 (print)OAI: oai:DiVA.org:mdh-26785DiVA, id: diva2:768545
Conference
The 20th IEEE Pacific Rim International Symposium on Dependable Computing PRDC 2014, 19-21 Nov 2014, Singapore, Singapore
Projects
SYNOPSIS - Safety Analysis for Predictable Software Intensive SystemsSafeCer - Safety Certification of Software-Intensive Systems with Reusable Components
Available from: 2014-12-04 Created: 2014-12-02 Last updated: 2016-10-31Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records BETA

Graydon, PatrickBate, Iain

Search in DiVA

By author/editor
Graydon, PatrickBate, Iain
By organisation
Embedded Systems
Electrical Engineering, Electronic Engineering, Information Engineering

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

doi
isbn
urn-nbn
Total: 11 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf