Evaluation of software development tools for high assurance safety critical systems

2004 ◽  
Author(s):  
A.J. Kornecki ◽  
K. Hall ◽  
D. Hearn ◽  
H. Lau ◽  
J. Zalewski
Keyword(s):  
Software Development ◽  
Critical Systems ◽  
Safety Critical ◽  
Development Tools ◽  
High Assurance ◽  
Safety Critical Systems ◽  
Software Development Tools

scholarly journals Lessons learnt from IEC61508 software assessments

2018 ◽  
Author(s):  
R H Campbell ◽  
R M Phillips ◽  
C Allsopp
Keyword(s):  
Software Development ◽  
Safety Management ◽  
Critical Systems ◽  
Specific System ◽  
Safety Critical ◽  
Lessons Learnt ◽  
Variable Environments ◽  
Management Processes ◽  
Development Processes ◽  
Safety Critical Systems

With the advances in platform automation and the publication of NAN 06/2018 - Software integrity (previously NAN 02/2016), there has been a drive towards compliance to IEC61508 in the naval domain.  Over the last few years Frazer-Nash have conducted a number of Original Equipment Manufacturer (OEM) audits and assessments to determine whether the requirements for safety critical software development in IEC61508 have been followed for a specific system or if a supplier's development processes are in line with the aspects of the standard which focus on software development, namely Part 3 - Software requirements.  These audits have revealed some common problems across suppliers and highlighted that IEC61508 requires both organisational safety management processes as well as those specific for a system. As the naval industry looks to adopt the processes outlined in IEC61508 or an equivalent standard, this paper will present some of the lessons learnt from our IEC61508 assessments and offer some advice for new and existing suppliers.  The paper will highlight some of the issues going forward as the development of safety critical systems is not a new concept but the specific factors arising in the naval domain from operating in variable environments, changing safe state conditions and ever increasing function complexity, present a key challenge. Included in the paper will be a view on how other industries are tackling IEC61508 compliance and where the strategies that have been adopted may be applicable in the naval domain as well as new tools which could assist with the development of safety critical systems. 

Models Oriented Approach for Developing Railway Safety-Critical Systems with UML

2010 ◽  
pp. 305-330
Author(s):  
Jean-Louis Boulanger ◽  
Alban Rasse ◽  
Akram Idani
Keyword(s):  
Software Development ◽  
Dynamic Behavior ◽  
Model Transformations ◽  
Critical Systems ◽  
Safety Critical ◽  
Development Cycle ◽  
Railway Safety ◽  
Safety Critical Systems ◽  
Key Aspects ◽  
Oriented Approach

This chapter presents an approach for certified design of railway critical systems. This approach, which realizes the software development cycle, relies on metamodeling architecture and model-transformations. It combines semi-formal UML models and formal models in order to check, proof and generate code by refinement; we use the process algebra FSP to check the dynamic behavior and B to generate proved code. Initially, the authors select an UML subset, which could be uses to model the key aspects of critical systems. Then, from this subset, the authors perform projections to obtain B and FSP models which are exploited by tools for checking, refinement and proof.

FACILITATING THE MAINTENANCE OF SAFETY-CRITICAL SYSTEMS

1994 ◽  
Vol 04 (02) ◽  
pp. 183-204 ◽  
Author(s):  
GERALD C. GANNOD ◽  
BETTY H.C. CHENG
Keyword(s):  
Software Development ◽  
Reverse Engineering ◽  
Formal Methods ◽  
Formal Specifications ◽  
Critical Systems ◽  
Safety Critical ◽  
Engineering Aspect ◽  
Forward Engineering ◽  
Safety Critical Systems ◽  
High Level

As software is increasingly used to control safety-critical systems, correctness becomes paramount. Formal methods in software development provide many benefits in the forward engineering aspect of software development. Reverse engineering is the process of constructing a high-level representation of a system from existing lower level instanti-ations of that system. Reverse engineering of program code into formal specifications facilitates the utilization of the benefits of formal methods in projects where formal methods may not have previously been used, thus facilitating the maintenance of safety-critical systems.

Sign in / Sign up

Export Citation Format

Share Document