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
Tool qualification for safety related systems
Bombardier Transportation Sweden AB, Västerås, Sweden.
Safety Integrity AB, Västerås, Sweden .
Mälardalen University, School of Innovation, Design and Engineering. Mälardalen University, School of Innovation, Design and Engineering, Embedded Systems.ORCID iD: 0000-0002-5032-2310
Effective Change AB, Västerås, Sweden .
2014 (English)In: Ada User Journal, ISSN 1381-6551, Vol. 35, no 1, 47-54 p.Article in journal (Refereed) Published
Abstract [en]

Tools used in the development of safety related software applications need to be qualified as safe. That is, the tools cannot be allowed to introduce hazardous faults into the application, e.g., a compiler shall not generate dangerous code due to failure of the compiler. In many cases laws and regulations require the product development of safety related applications to comply with industry sector specific safety standards. Examples of such standards include EN50129/50128 for railway applications, ISO/EN13849 for machines with moving parts, DO-178B/C for avionics, or IS026262 for cars. These standards require the use of a rigorous development and maintenance process. The standards are also mainly intended to be used when developing systems from scratch. However, most development and test tools are not developed from scratch according to the rigorous processes of these standards. In order to address this issue, some of the standards provide means for qualifying existing tools as a more lightweight and pragmatic alternative to a regular certification process. In this paper we analyze the concept of these qualification approaches. The result of the analysis in our contribution includes a set of approaches that can be applied individually or as a combination in order to reduce the effort needed for qualifying tools. As a running example we use one of the most flexible but at the same time dangerous, even prohibited, maintenance techniques available: dynamic instrumentation of executing code. With this example, we describe how exceptions in these standards can be utilized in order to qualify a dynamic instrumentation tool with a minimal effort, without following the process of tool certification as defined by the standards.

Place, publisher, year, edition, pages
2014. Vol. 35, no 1, 47-54 p.
Keyword [en]
Certification, Dynamic instrumentation, Functional safety, Software instrumentation, Tool qualification
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:mdh:diva-24979Scopus ID: 2-s2.0-84898927339OAI: oai:DiVA.org:mdh-24979DiVA: diva2:716436
Available from: 2014-05-09 Created: 2014-05-09 Last updated: 2014-05-09Bibliographically approved

Open Access in DiVA

No full text

Scopus

Search in DiVA

By author/editor
Sundmark, Daniel
By organisation
School of Innovation, Design and EngineeringEmbedded Systems
In the same journal
Ada User Journal
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

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