Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!cs!shimeall From: shimeall@cs.nps.navy.mil (Tim Shimeall x2509) Newsgroups: comp.software-eng Subject: Re: Information on current state of software safety desired Summary: Read a bit more... Keywords: bibliography Message-ID: <304@cs.nps.navy.mil> Date: 2 Oct 89 20:05:45 GMT References: <1321@cs.rit.edu> Reply-To: shimeall@cs.nps.navy.mil (Tim Shimeall x2509) Followup-To: comp.software-eng Organization: Naval Postgraduate School, Monterey CA Lines: 14 Suggestions (these answer most of your questions): Read Nancy Leveson's "Software Safety: What, Why and How", ACM Computing Surveys, June 1986. Get onto the RISKS list (comp.risks) -- Peter Neumann (risks-request@csl.sri.com) is the moderator. Read the IEEE Transactions of Software Engineering, Sept. 1986, a special issue on safety. Get copies of the proceedings of COMPASS, an IEEE sponsored annual conference on safety (among other things). Get copies of the proceedings of SAFECOMP, an AFIPS sponsored annual conference on safety (among other things). This might be a bit tricky, since this is a European conference, but Pergammon Press is the publisher. Tim