Svoboda | Graniru | BBC Russia | Golosameriki | Facebook

To install click the Add extension button. That's it.

The source code for the WIKI 2 extension is being checked by specialists of the Mozilla Foundation, Google, and Apple. You could also do it yourself at any point in time.

4,5
Kelly Slayton
Congratulations on this excellent venture… what a great idea!
Alexander Grigorievskiy
I use WIKI 2 every day and almost forgot how the original Wikipedia looks like.
Live Statistics
English Articles
Improved in 24 Hours
Added in 24 Hours
What we do. Every page goes through several hundred of perfecting techniques; in live mode. Quite the same Wikipedia. Just better.
.
Leo
Newton
Brights
Milds

Safety life cycle

From Wikipedia, the free encyclopedia

The safety life cycle is the series of phases from initiation and specifications of safety requirements, covering design and development of safety features in a safety-critical system, and ending in decommissioning of that system. This article uses software as the context but the safety life cycle applies to other areas such as construction of buildings, for example. In software development, a process is used (software life cycle) and this process consists of a few phases, typically covering initiation, analysis, design, programming, testing and implementation. The focus is to build the software. Some software have safety concerns while others do not. For example, a Leave Application System does not have safety requirements. But we are concerned about safety if a software that is used to control the components in a plane fails. So for the latter, the question is how safety, being so important, should be managed within the software life cycle.[1]

YouTube Encyclopedic

  • 1/3
    Views:
    12 633
    983
    389
  • Safety Lifecycle Overview
  • Safety Lifecycle Overview with exSILentia (Part 1)
  • The Safety Lifecycle Overview

Transcription

What is the Safety Life Cycle?

The basic concept in building software safety, i.e. safety features in software, is that safety characteristics and behaviour of the software and system must be specified and designed into the system.[2]

The problem for any systems designer lies in reducing the risk to an acceptable level and of course, the risk tolerated will vary between applications. When a software application is to be used in a safety-related system, then this must be borne in mind at all stages in the software life cycle. The process of safety specification and assurance throughout the development and operational phases is sometimes called the ‘safety life cycle’.

Phases in the Safety Life Cycle

The first stages of the life cycle involve assessing the potential system hazards and estimating the risk they pose. One such method is fault tree analysis.

This is followed by a safety requirements specification which is concerned with identifying safety-critical functions (functional requirements specification) and the safety integrity level for each of these functions.[3] The specification may either describe how the software should behave to minimize the risk or might require that the hazard should never arise.

A ‘normal’ process model is then followed with particular attention paid to the validation (inspection, testing etc.) of the system. Part of that validation should be an explicit safety validation activity.

See also

References

  1. ^ Hamid, Brahim; Geisel, Jacob; Ziani, Adel; Gonzalez, David (2012). Avgeriou, Paris (ed.). "Safety Lifecycle Development Process Modeling for Embedded Systems - Example of Railway Domain". Software Engineering for Resilient Systems. Lecture Notes in Computer Science. Berlin, Heidelberg: Springer. 7527: 63–75. doi:10.1007/978-3-642-33176-3_5. ISBN 978-3-642-33176-3.
  2. ^ Alberico, David. "Software System Safety Handbook" (PDF). Joint Services Software Safety Committee.
  3. ^ Storey, Neil (1996). Safety-Critical Computer Systems. Harlow: Prentice Hall. p. 10. ISBN 0-201-42787-7.

External links

Safety Life Cycle - Implementation Benefits and Impact on Field Devices (PDF), ISA.org, archived from the original (PDF) on 31 March 2012

This page was last edited on 25 June 2021, at 09:01
Basis of this page is in Wikipedia. Text is available under the CC BY-SA 3.0 Unported License. Non-text media are available under their specified licenses. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc. WIKI 2 is an independent company and has no affiliation with Wikimedia Foundation.