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
Strong and Weak Contract Formalism for Third-Party Component Reuse
Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems. (IS (Embedded Systems))ORCID iD: 0000-0002-7382-8437
Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems. (IS (Embedded Systems))ORCID iD: 0000-0002-6952-1053
Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems. (IS (Embedded Systems))ORCID iD: 0000-0002-8461-0230
Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems. (IS (Embedded Systems))ORCID iD: 0000-0002-7235-6888
2013 (English)In: 2013 IEEE International Symposium on Software Reliability Engineering Workshops, ISSREW 2013, 2013, 359-364 p.Conference paper, Published paper (Refereed)
Abstract [en]

Our aim is to contribute to bridging the gap between the justified need from industry to reuse third-party components and skepticism of the safety community in integrating and reusing components developed without real knowledge of the system context. We have developed a notion of safety contract that will help to capture safety-related information for supporting the reuse of software components in and across safety-critical systems. In this paper we present our extension of the contract formalism for specifying strong and weak assumption/guarantee contracts for out-of-context reusable components. We elaborate on notion of satisfaction, including refinement, dominance and composition check. To show the usage and the expressiveness of our extended formalism, we specify strong and weak safety contracts related to a wheel braking system.

Place, publisher, year, edition, pages
2013. 359-364 p.
Keyword [en]
safety contracts, strong and weak contracts, safety-critical systems, safety standards, third-party component reuse
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:mdh:diva-22884DOI: 10.1109/ISSREW.2013.6688921ISI: 000330639500076Scopus ID: 2-s2.0-84893309127ISBN: 978-1-4799-2552-0 (print)OAI: oai:DiVA.org:mdh-22884DiVA: diva2:665756
Conference
24th IEEE International Symposium on Software Reliability Engineering Workshops, ISSREW 2013; Pasadena, CA; United States; 4 November 2013 through 7 November 2013
Projects
SYNOPSIS - Safety Analysis for Predictable Software Intensive SystemsSafeCer - Safety Certification of Software-Intensive Systems with Reusable Components
Available from: 2013-11-20 Created: 2013-11-19 Last updated: 2015-11-12Bibliographically approved
In thesis
1. Facilitating Reuse of Safety Case Artefacts Using Safety Contracts
Open this publication in new window or tab >>Facilitating Reuse of Safety Case Artefacts Using Safety Contracts
2015 (English)Licentiate thesis, comprehensive summary (Other academic)
Abstract [en]

 Safety-critical systems usually need to comply with a domain-specific safety standard, which often require a safety case in form of an explained argument supported by evidence to show that the system is acceptably safe to operate in a given context. Developing such systems to comply with a safety standard is a time-consuming and costly process. Reuse within development of such systems is used to reduce the cost and time needed to both develop the system and the accompanying safety case. Reuse of safety-relevant components that constitute the system is not sufficient without the reuse of the accompanying safety case artefacts that include the safety argument and the supporting evidence. The difficulties with reuse of the such artefacts within safety-critical systems lie mainly in the nature of safety being a system property and the lack of support for systematic reuse of such artefacts.

In this thesis we focus on developing the notion of safety contracts that can be used to facilitate systematic reuse of safety-relevant components and their accompanying artefacts. More specifically, we explore the following issues: in which way such contracts should be specified, how they can be derived, and in which way they can be utilised for reuse of safety artefacts. First, we characterise the contracts as either “strong” or “weak” to facilitate capturing different behaviours reusable components can exhibit in different systems. Then, we present methods for deriving safety contracts from failure analyses. As the basis of the safety-critical systems development lies in the failure analyses and identifying which malfunctions eventually can lead to accidents, we deem that the basis for specifying the safety contracts lies in capturing information identified by such failure analyses within the contracts. Finally, we provide methods for generative reuse of the safety case artefacts by utilising the safety contracts. Moreover, we define a safety contracts development process as guidance for systematic reuse based on the safety contracts. We use a real-world case to demonstrate the proposed process. 

Place, publisher, year, edition, pages
Västerås: Mälardalen University, 2015
Series
Mälardalen University Press Licentiate Theses, ISSN 1651-9256 ; 203
National Category
Engineering and Technology Other Engineering and Technologies
Research subject
Computer Science
Identifiers
urn:nbn:se:mdh:diva-27906 (URN)978-91-7485-213-4 (ISBN)
Presentation
2015-06-11, Gamma, Mälardalens högskola, Västerås, 14:00 (English)
Opponent
Supervisors
Projects
SYNOPSIS - Safety Analysis for Predictable Software Intensive Systems
Available from: 2015-05-05 Created: 2015-04-26 Last updated: 2015-06-02Bibliographically approved

Open Access in DiVA

No full text

Other links

Publisher's full textScopus

Search in DiVA

By author/editor
Sljivo, IrfanGallina, BarbaraCarlson, JanHansson, Hans
By organisation
Embedded Systems
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

Total: 50 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