Software system safety

Hatton, L. (1997), Unexpected (and Sometimes Unpleasant) Lessons from Data in Real Software Systems, Safety and Reliability of Software Based Systems, Springer-Verlag, Heidelberg, Germany. [Pg.226]

SOFTWARE SYSTEMS SAFETY - TRIPLE REDUNDANCY FOR SOFTWARE ... [Pg.131]

Mil STD-882B (11) outlines the general concepts of Systems Safety. Notice 1 (12) appended to that document specifically covers requirements for software systems safety. The Air Force also has a Software Systems Safety Handbook (13). A number of recent articles in Hazafd Prevention (14), the Journal of the Systems Safety Society, expanded on the technical content of this handbook. The concepts were covered in a more explicit and useful manner by Erwin Schoitsch of the Austrian Research Center Seibersdorf in a recent forty-two page, two-part, article (15). [Pg.131]

Anon "Software Systems Safety" MIL-STD-882B-Notice 1 (3/84)... [Pg.142]

Anon-Software Systems Safety handbook AFISC SSH-1-1 (5 September 1985) (U.S. Air Force)... [Pg.142]

Anon "Software Systems Safety" Hazard Prevention-Journal of the Systems Safety Society, Vol. 22, Nos. 1, 2, 3, 6, 1986... [Pg.142]

Tailoring of safety requirements sources from generic lists, such as those in Leveson (1995) and the DoD s Software System Safety Handbook (2010). The purpose here is to use the documented experience of those before us to determine if we do not know that we do not know, and to prompt us on what requirements might be relevant. [Pg.208]

Software System Safety Handbook, 2010. Joint Services Computer Resources Management Group U.S. Navy, U.S. Army, and the U.S. Air Force, Joint Services Software Safety Committee, Joint Services System Safety Panel. Electronic Industries Association, G-48 Committee. https //acc.dau.miPCommunityBrowser.aspx id=683698. [Pg.271]

At the 1993 International System Safety Conference, the then Chief of Air Force Safety in his keynote presentation said that the two challenges for the 90s were in software system safety and in human factors. This was true then, and it is today, more than ten years later. [Pg.7]

Finally, there is a general lack of expertise in the area of software system safety. Not only are there grossly insufficient numbers of qualified system safety engineers with software safety credentials but also very few recognized textbooks, seminars, university programs, or competent consultants are available. The lack of technical competence in this area seems to span the entire system safety community. [Pg.44]

As an overview of software system safety, the following is provided from the website of the U.S. Army Communications-Electronics Command (www.monmouth.army.mil/cencom/safety/main.htm). Software system safety optimizes system safety in the design, development, use, and maintenance of software systems and their integration with safety critical hardware systems in an operational environment. ... [Pg.53]

Software system safety is an element of the total safety and software development program. Software cannot be allowed to function independently of the total effort. [Pg.53]

Joint Software Systems Safety Engineering Handbook, Department of Defense, 2010. www.acq.osd.mU/se/docs/Joint-SW-Systems-Safety-Engineering-Handbook.pdf... [Pg.535]

Note that the term SCL goes by different names, such as SHRI, SL, DAL, or SIL, depending on the guidance documentation used. These alternate terms and similar SwS processes are defined in M1L-STD-882C, the DoD Joint Software Systems Safety Engineering Handbook and RTCA/DO-178B. [Pg.390]

Department of Defense (DoD) Joint Software Systems Safety Handbook, December 1999. [Pg.460]

DoD Joint Software Systems Safety Engineering Handbook, September... [Pg.460]

U.S. Army Aviation and Missile Command (AMCOM) Regulation 385-17, AMCOM Software System Safety Policy, March 15,2008. [Pg.460]

SSSTRP Software System Safety Technical Review Panel... [Pg.503]

Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...