Analyzing software requirements errors in safety-critical, embedded systems

  title={Analyzing software requirements errors in safety-critical, embedded systems},
  author={Robyn R. Lutz},
  journal={[1993] Proceedings of the IEEE International Symposium on Requirements Engineering},
  • R. Lutz
  • Published 4 January 1993
  • Computer Science
  • [1993] Proceedings of the IEEE International Symposium on Requirements Engineering
The root causes of safety-related software errors in safety-critical embedded systems are analyzed. The results show that software errors identified as potentially hazardous to the system tend to be produced by different error mechanisms than those that produce nonsafety-related software errors. Safety-related software errors are shown to arise most commonly from: discrepancies between the documented requirements specifications and the requirements needed for correct functioning of the system… 

Tables from this paper

Targeting safety-related errors during software requirements analysis

  • R. Lutz
  • Computer Science
    SIGSOFT '93
  • 1993
This paper provides a Safety Checklist for use during the analysis of software requirements for spacecraft and others safety-critical, embedded systems to reduce the number of safety-related software errors.

Requirements discovery during the testing of safety-critical software

The results suggest that "false positive" problem reports from testing provide a rich source of requirements information that can be used to reduce operational anomalies in critical systems.

A Survey of Formal Specification Application to Safety Critical Systems

  • S. P. NandaEmanuel S. Grant
  • Computer Science
    2019 IEEE 2nd International Conference on Information and Computer Technologies (ICICT)
  • 2019
The paper will examine how different domains affect the standards of formal specification methods in different applications and the approach will be to survey various papers in the related fields.

Identifying dependability requirements for space software systems

A structured software dependability requirements analysis process that uses system software requirement specifications and traditional safety analysis techniques and the final results are more complete, consistent, and reliable specifications.

Analysis of Errors in Safety Critical Embedded System Software in Aerial Vehicle

The main aim is to propose the error prevention guidelines that are practical to be implemented despite the project schedules and considered valuable outcome of the Independent Verification and Validation effort carried out for this safety critical embedded software.

Safety analysis of an evolving software architecture

  • R. de Lemos
  • Computer Science
    Proceedings. Fifth IEEE International Symposium on High Assurance Systems Engineering (HASE 2000)
  • 2000
This work assumes that components remain unchanged while their interactions adapt to the different requirements needs, and performs safety analysis using model checking to verify whether safe behaviour is maintained when interactions between components change.

Safety analysis of an evolving software architecture

This work assumes that components remain unchanged while their interactions adapt to the different requirements needs, and performs safety analysis using model checking to verify whether safe behaviour is maintained when interactions between components change.

A process for failure modes and effects analysis of computer software

The procedure described here was developed and used to analyze mission- and safety-critical software systems and database tools make the process reasonably painless, highly accurate, and very thorough.

Engineering Requirements for System Reliability and Security

This paper overviews a systematic, goal-oriented approach to requirements engineering for high-assurance systems and the target of this approach is a complete, consistent, adequate, and structured set of software requirements and environment assumptions.



A case study on isolation of safety-critical software

  • E. Addy
  • Business
    COMPASS '91, Proceedings of the Sixth Annual Conference on Computer Assurance
  • 1991
In the case study presented, a series of problems affecting safety that were identified in a large, real-time control system that contained both safety-critical and non-safety-critical functions were

Analyzing Software Safety

This paper defines software safety and describes a technique called software fault tree analysis which can be used to analyze a design as to its safety and has been applied to a program which controls the flight and telemetry for a University of California spacecraft.

Software Requirements Analysis for Real-Time Process-Control Systems

Using these criteria, analysis procedures can be defined for particular state-machine modeling languages to provide semantic analysis of real-time process-control software requirements requirements.

A Case History Analysis of Software Error Cause-Effect Relationships

Four major error-occurrence mechanisms were identified; two are related to hardware and software interface specification misunderstandings, while the other two arerelated to system and module function misunderstandings.

An Experimental Evaluation of Software Redundancy as a Strategy For Improving Reliability

The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is discussed. The effectiveness of multiversion software is studied

Collecting and categorizing software error data in an industrial environment

An analysis of errors and their causes in system programs

  • A. Endres
  • Medicine
    IEEE Transactions on Software Engineering
  • 1975
Using a classification of the errors according to various attributes, conclusions can be drawn concerning the possible causes ofThese errors detected during internal testing of the operating system DOS/VS.

An Experiment in Software Error Data Collection and Analysis

An experiment in software error data collection and analysis was conducted in order to study relationships between complexity measures and error charateristics under conditions where the error data could be carefully defined and collected.

On hierarchical design of computer systems for critical applications

  • P. Neumann
  • Computer Science
    IEEE Transactions on Software Engineering
  • 1986
Hierarchical abstraction is shown to provide the basis for successive layers of trust with respect to the full set of critical requirements, explicitly reflecting differing degrees of criticality.

Software Requirements Analysis and Specification

This chapter discusses the requirements taxonomy, characteristics of requirements requirements paradigms, and design system support processes requirements changing turning the wheel process.