Safety-Critical Mailing List Archive 2001
By Thread

End of Messages	Date view	Subject view	Author view	Other groups

775 Messages
Starting:	Mon, 8 Jan 2001 15:32:41 -0000	Ending:	Fri, 21 Dec 2001 08:52:35 -0000

Reliability claims in telecomms Armstrong, Jim
- Re: Reliability claims in telecomms Felix Redmill
"The sense of security more frequently springs from habit than fr om conviction..." Ganter, John H
RE: Re[2]: Reliability claims in telecomms Armstrong, Jim
- Re: Reliability claims in telecomms Peter B. Ladkin
UK Health & Safety Executive Database - Prosecutions UK72
IEC61508 interpretation? Olle Bridal
- Re: IEC61508 interpretation? John McDermid
- RE: IEC61508 interpretation? Tony Foord
- RE: IEC61508 interpretation? Spriggs, John
- RE: IEC61508 interpretation? Mike Ellims
- RE: IEC61508 interpretation? bill black
- RE: IEC61508 interpretation? Neil J. Robinson
  - Re: IEC61508 interpretation? John McDermid
  - Re: IEC61508 interpretation? John McDermid
  - Re: IEC61508 interpretation? Peter B. Ladkin
  - RE: IEC61508 interpretation? pgb(at)adelard.co.uk
- Re[2]: IEC61508 interpretation? simon.brown(at)hse.gsi.gov.uk
  - Re: Re[2]: IEC61508 interpretation? leveson(at)sunnyday.mit.edu
  - Re: IEC61508 interpretation? Peter B. Ladkin
- Re: IEC61508 interpretation? Felix Redmill
  - Re: IEC61508 interpretation? Peter B. Ladkin
  - Re: IEC61508 interpretation? Pete Fenelon
  - Re: IEC61508 interpretation? John McDermid
  - Re: IEC61508 interpretation? Pete Fenelon
  - Re: IEC61508 interpretation? Peter B. Ladkin
  - Re: IEC61508 interpretation? Mark Werenowski
  - Re: IEC61508 interpretation? ross_hannan
  - Re: IEC61508 interpretation? Peter B. Ladkin
  - Re: IEC61508 interpretation? ross_hannan
- Re: IEC61508 interpretation? Felix Redmill
- Re: IEC61508 interpretation? Felix Redmill
- Re[2]: IEC61508 interpretation? simon.brown(at)hse.gsi.gov.uk
  - Re: Re[2]: IEC61508 interpretation? Des Nutt
  - Re: Re[2]: IEC61508 interpretation? brian wichmann
RE: Message Delivery: email message stopped at MAILsweeper Pavey Deryk
Whilst we are talking about car safety issues... Spriggs, John
- Re: Whilst we are talking about car safety issues... John McDermid
- Re: Whilst we are talking about car safety issues... simon.brown(at)hse.gsi.gov.uk
  - Re: Whilst we are talking about car safety issues... Peter B. Ladkin
  - Re: Whilst we are talking about car safety issues... John Dalton
  - Re: Whilst we are talking about car safety issues... John Dalton
  - Re: Whilst we are talking about car safety issues... Peter B. Ladkin
- RE: Whilst we are talking about car safety issues... Andy Ashworth
- RE: Whilst we are talking about car safety issues... Michael.Schmidt(at)industrialrisk.com
- RE: Whilst we are talking about car safety issues... G.F.
- RE: Whilst we are talking about car safety issues... Mike Ellims
- Re: Whilst we are talking about car safety issues... Peter B. Ladkin
- RE: Whilst we are talking about car safety issues... Spriggs, John
  - Re: Whilst we are talking about car safety issues... Peter B. Ladkin
- Re[2]: Whilst we are talking about car safety issues... simon.brown(at)hse.gsi.gov.uk
  - Re: Whilst we are talking about car safety issues... Jonathan Moffett
  - Re: Whilst we are talking about car safety issues... Peter B. Ladkin
- Re: Whilst we are talking about car safety issues... johnson(at)dcs.gla.ac.uk
  - Re: Whilst we are talking about car safety issues... Peter B. Ladkin
  - Re: Whilst we are talking about car safety issues... Peter B. Ladkin
  - RE: Whilst we are talking about car safety issues... escharpf(at)exida.com
- RE: Whilst we are talking about car safety issues... Spriggs, John
- RE: Whilst we are talking about car safety issues... UK72
- RE: Whilst we are talking about car safety issues... Spriggs, John
- RE: Whilst we are talking about car safety issues... Michael.Schmidt(at)industrialrisk.com
  - Re: Whilst we are talking about car safety issues... Peter B. Ladkin
Cell phones and gas stations considered urban legends Ganter, John H
- RE: Cell phones and gas stations considered urban legends MCLELLAN Alexander
Re[4]: IEC61508 interpretation? simon.brown(at)hse.gsi.gov.uk
- Re: IEC61508 interpretation? Peter B. Ladkin
- Re: Re[4]: IEC61508 interpretation? leveson(at)sunnyday.mit.edu
Car safety issues... Mobile Phones mark.coates(at)baesystems.com
Re[6]: IEC61508 interpretation? simon.brown(at)hse.gsi.gov.uk
VB: IEC61508 interpretation? Andrew Hussey
Policies concerning Phones and Forecourts Peter B. Ladkin
SV: Policies concerning Phones and Forecourts Andrew Hussey
- Re: SV: Policies..... Peter B. Ladkin
Re: Mobile phones, forecourt fires etc Ken Frith
- Re: Mobile phones, forecourt fires etc Peter B. Ladkin
Re: Mobile phones, forecourt fires etc Ken Frith
IEC61508 interpretation - debate at a conference? Peter Sheppard
RE: Phones and Forecourts.. PREFERRED VERSION!! Spriggs, John
Process Safety Time Requirment Wise Technics Limited
- Re: Process Safety Time Requirment Tony Cox
- Re: Process Safety Time Requirment Paul Gruhn, P.E.
Use of Automatically generated code in SCS Steven Crook-Dawkins
- RE: Use of Automatically generated code in SCS Mike Ellims
- Re: Use of Automatically generated code in SCS leveson(at)sunnyday.mit.edu
  - RE: Use of Automatically generated code in SCS Steven Crook-Dawkins
  - Re: Use of Automatically generated code in SCS Steve White
- RE: Use of Automatically generated code in SCS Bahadur Sihota
- RE: Use of Automatically generated code in SCS Mike Ellims
- RE: Use of Automatically generated code in SCS R.S.
- RE: Use of Automatically generated code in SCS Garlington, Kennie E
- RE: Use of Automatically generated code in SCS Pavey Deryk
- RE: Use of Automatically generated code in SCS Mike Ellims
MIL-STD-882B software hazard analysis tasks Simon Hughes
- RE: MIL-STD-882B software hazard analysis tasks Garlington, Kennie E
- RE: MIL-STD-882B software hazard analysis tasks Spriggs, John
Windows NT and SILs timothy.fry(at)baesystems.com
- RE: Windows NT and SILs Smyth, Thomas
  - Re: Windows NT and SILs david.biddulph(at)baesystems.com
  - Re: Windows NT and SILs info(at)fnc.co.uk
- RE: Windows NT and SILs Spiker, Rolf
- RE: Windows NT and SILs Mike Ellims
- RE: Windows NT and SILs Simon Hughes
- Re: Windows NT and SILs gary.mcguire(at)westsig.co.uk
- RE: Windows NT and SILs mark.coates(at)baesystems.com
- Re: Windows NT and SILs Paul Gruhn, P.E.
- RE: Windows NT and SILs UK72
- Re[2]: Windows NT and SILs simon.brown(at)hse.gsi.gov.uk
- RE: Windows NT and SILs Simon Hughes
References to COTS/SOUP research? Rune Winther
Intelligent Systems Chris Harper
UML in Safety Related Software. Smith Mark
- RE: UML in Safety Related Software. Spriggs, John
  - Re: UML in Safety Related Software. Peter B. Ladkin
  - RE: UML in Safety Related Software. Tony Foord
- RE: UML in Safety Related Software. Tony Foord
"System Stress" test for Windows NT/2000 Ganter, John H
Cost of independant safety monitor nikola.kanuritch(at)baesystems.com
- Re: Cost of independant safety monitor leveson(at)sunnyday.mit.edu
- Re: Cost of independant safety monitor Wise Technics Limited
- Re: Cost of independant safety monitor Dock Allen
  - Re: Cost of independant safety monitor leveson(at)sunnyday.mit.edu
New members of the safety-critical mailing list. Jonathan Moffett
Workshop on Human Error, Safety, and System Development leveson(at)sunnyday.mit.edu
Submarine failure Felix Redmill
- RE: Submarine failure Spriggs, John
Reliability of fault-tolerance/error handling acoombes(at)realogy.com
- RE: Reliability of fault-tolerance/error handling Spriggs, John
- Re: Reliability of fault-tolerance/error handling Felix Redmill
  - Re: Reliability of fault-tolerance/error handling Pete Fenelon
  - Re: Reliability of fault-tolerance/error handling Peter B. Ladkin
  - Re: Reliability of fault-tolerance/error handling Stefan Leue
  - Re: Reliability of fault-tolerance/error handling Peter B. Ladkin
- Re: Reliability of fault-tolerance/error handling John McDermid
- Re: Reliability of fault-tolerance/error handling Neale Fulton
Software functions and CENELEC SIL 0 ricardo.gonzalez(at)dimetronic.es
- RE: Software functions and CENELEC SIL 0 Martyn Thomas
- RE: Software functions and CENELEC SIL 0 Andy Ashworth
- RE: Software functions and CENELEC SIL 0 Felix Redmill
- RE: Software functions and CENELEC SIL 0 bill black
- Re: Software functions and CENELEC SIL 0 Frank Renpenning
Elementary Particles and Computer Memory [longish] Peter B. Ladkin
- More on Elementary Particles and Computer Memory [longish] Peter B. Ladkin
- Neutron Irradiation and Computer Memory: original experiments [longish] Peter B. Ladkin
Flight Computer Anomalies Peter B. Ladkin
- Re: Flight Computer Anomalies pgb(at)adelard.co.uk
  - Re: Flight Computer Anomalies Peter B. Ladkin
Single Event Effects: a warning brian wichmann
- RE: Single Event Effects: a warning Garlington, Kennie E
- Re: Single Event Effects: a warning pgb(at)adelard.co.uk
  - Re: Single Event Effects: a warning Peter B. Ladkin
Safety Critical Mailing List application michael.eccles(at)baesystems.com
Standards writing. brian wichmann
- RE: Standards writing. Spriggs, John
- RE: Standards writing. Palmer, Steve
  - Re: Standards writing. Peter B. Ladkin
Fwd: AI and safety critical applications Jonathan Moffett
- Call for Participation: Formal Design of Safety-Critical Embedded Systems Poign�
newbie: concrete experiences on safety-critical software Dambacher, Christoph, VME23
RA Position: High Integrity Software Verification/Theorem Proving Andrew Ireland
An IEC 61508 instrument brian wichmann
- RE: An IEC 61508 instrument Martyn Thomas
- RE: An IEC 61508 instrument UK72
- Re: An IEC 61508 instrument Dr. William Goble
  - Re: An IEC 61508 instrument Jon Davies
- RE: An IEC 61508 instrument Rachid BELHAJ
- RE: An IEC 61508 instrument Spriggs, John
SN29500 Marc Pijnenburg
Re: IEC 61 508 Marc Pijnenburg
(no subject) frank.renpenning(at)gmx.de
Typical Example Dambacher, Christoph, VME23
- Re: Typical Example John Fox
  - RE: Typical Example John Fox
ATEX Directive ( 94/9/CE ) Rachid BELHAJ
IEC61508 forum Laurie Blackmore
Re: IEC61508 forum Ian Toyn
Use of standard PLC's for safety applications Jeremy Reed
- Re: Use of standard PLC's for safety applications Paul Gruhn, P.E.
- Re: Use of standard PLC's for safety applications Laurie Blackmore
RE: unsubscribe Robinson, Paul
Workshop on Worst-Case Execution Time Analysis Iain Bate
Re: SEC: Unclassified Use of Linux in a Safety Critical System Michael A Eccles
RE: Osprey woes: Cultural root causes Ganter, John H
SW Direct Cause of December Osprey Crash Peter B. Ladkin
- RE: SW Direct Cause of December Osprey Crash Martyn Thomas
  - Re: SW Direct Cause of December Osprey Crash leveson(at)sunnyday.mit.edu
  - Re: oops, forgot one leveson(at)sunnyday.mit.edu
  - Re: SW Direct Cause of December Osprey Crash Peter B. Ladkin
  - RE: SW Direct Cause of December Osprey Crash Martyn Thomas
- RE: SW Direct Cause of December Osprey Crash Michael.Schmidt(at)industrialrisk.com
- RE: SW Direct Cause of December Osprey Crash Garlington, Kennie E
- RE: SW Direct Cause of December Osprey Crash Neale Fulton
- RE: SW Direct Cause of December Osprey Crash Garlington, Kennie E
- RE: SW Direct Cause of December Osprey Crash Neale Fulton
More information on the SW Peter B. Ladkin
- Re: More information on the SW Pete Mellor
RE: oops, forgot one Michael.Schmidt(at)industrialrisk.com
- Re: oops, forgot one John McDermid
Definition of "Latent Fault" Peter B. Ladkin
- RE: Definition of "Latent Fault" Tony Foord
  - RE: Definition of "Latent Fault" Martyn Thomas
- Re: Definition of "Latent Fault" brian wichmann
- Re: Definition of "Latent Fault" brian wichmann
- RE: Definition of "Latent Fault" Garlington, Kennie E
- RE: Definition of "Latent Fault" Spriggs, John
- RE: Definition of "Latent Fault" Robinson, Paul
  - Re: Definition of "Latent Fault" Peter B. Ladkin
- RE: Definition of "Latent Fault" Spriggs, John
- Re[2]: Definition of "Latent Fault" simon.brown(at)hse.gsi.gov.uk
- Re: Definition of "Latent Fault" Felix Redmill
- RE: Definition of "Latent Fault" Michael.Schmidt(at)industrialrisk.com
- RE: Definition of "Latent Fault" Garlington, Kennie E
  - Re: Definition of "Latent Fault" Peter B. Ladkin
- RE: Definition of "Latent Fault" Garlington, Kennie E
- Re: Definition of "Latent Fault" Robin Cook
  - Re: Definition of "Latent Fault" Peter B. Ladkin
- RE: Definition of "Latent Fault" Garlington, Kennie E
- RE: Definition of "Latent Fault" Felix Redmill
- Re: Definition of "Latent Fault" Robin Cook
  - Re: Definition of "Latent Fault" Peter B. Ladkin
- Re: Definition of "Latent Fault" nikola.kanuritch(at)baesystems.com
  - Re: Definition of "Latent Fault" Peter B. Ladkin
- RE: Definition of "Latent Fault" Garlington, Kennie E
  - Re: Definition of "Latent Fault" Peter B. Ladkin
- RE: Definition of "Latent Fault" Peter Amey
Post doc or visiting research position in software safety leveson(at)sunnyday.mit.edu
Discussion of Definitions Peter B. Ladkin
- RE: Discussion of Definitions by way of Jonathan Moffett
  - Re: Discussion of Definitions Peter B. Ladkin
  - Re: Discussion of Definitions Jonathan Moffett
- RE: Discussion of Definitions Simon Hughes
  - Re: Discussion of Definitions Peter B. Ladkin
  - RE: Discussion of Definitions Martyn Thomas
  - RE: Discussion of Definitions pgb(at)adelard.co.uk
- RE: Discussion of Definitions Michael.Schmidt(at)industrialrisk.com
- RE: Discussion of Definitions Andy Ashworth
- RE: Discussion of Definitions johnson(at)dcs.gla.ac.uk
- RE: Discussion of Definitions Simon Hughes
- RE: Discussion of Definitions Simon Hughes
RE: Definition of "Latent Fault" Pete Mellor
- Re: Definition of "Latent Fault" Peter B. Ladkin
- Re: Definition of "Latent Fault" Peter B. Ladkin
Re: Help - Is there a digest version? pgb(at)adelard.co.uk
Re: Discussion of Definitions Peter B. Ladkin
RE: Help - Is there a digest version? Michael.Schmidt(at)industrialrisk.com
A comment on overall effectiveness Ganter, John H
- Re: A comment on overall effectiveness John McDermid
- RE: A comment on overall effectiveness Peter Amey
- RE: A comment on overall effectiveness Garlington, Kennie E
SILs - Fact, Fiction or Filibuster? Peter Sheppard
- RE: SILs - Fact, Fiction or Filibuster? Peter Sheppard
Osprey Peter B. Ladkin
V-22 PANEL RECOMMENDATIONS Garlington, Kennie E
Osprey Peter B. Ladkin
Osprey Peter B. Ladkin
- RE: Osprey Garlington, Kennie E
  - Re: Osprey Peter B. Ladkin
- RE: Osprey Garlington, Kennie E
Use of OO technologies in safety critical software M.Lewis(at)rmcs.cranfield.ac.uk
- Re: Use of OO technologies in safety critical software John McDermid
- RE: Use of OO technologies in safety critical software Andy Ashworth
- Re: Use of OO technologies in safety critical software Kevin Charles Lano
- Re: Use of OO technologies in safety critical software Chris Harper
IEE Railway Professional Network, Launch Lecture 10th May 2001 - POSTPONED to 12th June 2001 Peter Sheppard
1st European COTS User Working Group Workshop Ljerka Beus
Independent Safety Auditor (System & Software) Wong, Chi
- RE: Independent Safety Auditor (System & Software) bill black
  - Re: Independent Safety Auditor (System & Software) John McDermid
- Re: Independent Safety Auditor (System & Software) John McDermid
More on Osprey Peter B. Ladkin
- Re: More on Osprey Gerard Le Lann
- Re: More on Osprey Peter B. Ladkin
- Re: More on Osprey Gerard Le Lann
- Re: More on Osprey Peter B. Ladkin
- Re: More on Osprey Gerard Le Lann
- Re: More on Osprey Peter B. Ladkin
- RE: More on Osprey Michael.Schmidt(at)industrialrisk.com
- RE: More on Osprey Garlington, Kennie E
HSE publish Adelard research on Software of Unknown Pedigreee George Cleland
HSE publish Adelard research on Software of Unknown Pedigreee George Cleland
PC + Windows NT/2000 Per-Tore Aasestrand
- RE: PC + Windows NT/2000 Martyn Thomas
- Re: PC + Windows NT/2000 John McDermid
- RE: PC + Windows NT/2000 Robin Cook
- RE: PC + Windows NT/2000 Simon Hughes
- [sc] Re: PC + Windows NT/2000 Chris Harper
  - Re: [sc] Re: PC + Windows NT/2000 Per-Tore Aasestrand
- Re: PC + Windows NT/2000 Felix Redmill
AW: PC + Windows NT/2000 Baal, Joep van
- Re: PC + Windows NT/2000 John McDermid
  - Re: PC + Windows NT/2000 Per-Tore Aasestrand
[Fwd: Non-linear Sensitivity of Electrochemical Oxygen Sensors to Helium] Kelly Mahoney
AW: PC + Windows NT/2000 Baal, Joep van
UPDATED CFP: Workshop on Inspection in Software Engineering J. Harauz
[re:Fwd: Non-linear Sensitivity of Electrochemical Oxygen Sensors to Helium] Ian.Gibson(at)Fluor.com
[sc] safety critical laser printers Pierluigi Guida
- RE: [sc] safety critical laser printers Tony Foord
- Re: [sc] safety critical laser printers Jon Davies
- RE: [sc] safety critical laser printers Michael.Schmidt(at)industrialrisk.com
  - Re: [sc] safety critical laser printers Jon Davies
- RE: [sc] safety critical laser printers Phil Williams
  - RE: [sc] safety critical laser printers Stephen Bull
  - Re: [sc] safety critical laser printers Jon Davies
- RE: [sc] safety critical laser printers Derek Mannering
  - Re: [sc] safety critical laser printers Peter B. Ladkin
- RE: [sc] safety critical laser printers Andy Ashworth
  - RE: [sc] safety critical laser printers pgb(at)adelard.co.uk
- RE: [sc] safety critical laser printers UK72
  - RE: [sc] safety critical laser printers pgb(at)adelard.co.uk
  - Re: [sc] safety critical laser printers Mike.Falla
- RE: [sc] safety critical laser printers UK72
- RE: [sc] safety critical laser printers Michael.Schmidt(at)industrialrisk.com
- RE: [sc] safety critical laser printers Spriggs, John
- Re: [sc] safety critical laser printers UK72
[sc] Safety-related communication (EN 50159-2), was: PC + Windows NT/2 000 Braband Jens
[sc] Cell-phone safety... Prof. Chris Johnson
[sc] Man-rated? King, Michael B
- Re: [sc] Man-rated? John McDermid
- Re: [sc] Man-rated? Chris Harper
[sc] Automotive safety-critical systems acoombes(at)realogy.com
- RE: [sc] Automotive safety-critical systems Tony Foord
- RE: [sc] Automotive safety-critical systems UK72
- RE: [sc] Automotive safety-critical systems Mike Ellims
- RE: [sc] Automotive safety-critical systems Mike Ellims
- Re: [sc] Automotive safety-critical systems D, Joseph G
- RE: [sc] Automotive safety-critical systems Robin Cook
- Re: [sc] Automotive safety-critical systems mark.bowell(at)hse.gsi.gov.uk
[sc] Literature searching Jonathan Moffett
AW: [sc] Automotive safety-critical systems Baal, Joep van
[sc] Definitions in ARP4761 Mark Werenowski
- Re: [sc] Definitions in ARP4761 John McDermid
AW: [sc] Definitions in ARP4761 Baal, Joep van
[sc] Definitions in ARP4761 Robin Cook
[sc] Definitions in ARP4761 Baal, Joep van
- RE: [sc] Definitions in ARP4761 Spriggs, John
- RE: [sc] Definitions in ARP4761 OLIVER Mervyn
Definitions in ARP4761 Mark Werenowski
[sc] Impact of new European Railway Standards Braband Jens
[sc] IEE Railway Professional Network Seminar 12th July - SILs Fact, F iction and Filibuster Peter Sheppard
- Re: [sc] IEE Railway Professional Network Seminar 12th July - SILs Fact, Fiction and Filibuster John McDermid
Re: [sc] IEE Railway Professional Network Seminar 12th July - SILs Fact, Fiction and Filibuster John Calvert
RE: [sc] IEE Railway Professional Network Seminar 12th July - SIL s Fact, Fiction and Filibuster Peter Sheppard
[sc] ISA Conference Laurie Blackmore
[sc] Fwd: FAO: Jonathan Moffett - Safety-critical mailing list Jonathan Moffett
[sc] A320 Incident Peter B. Ladkin
- RE: [sc] A320 Incident Spriggs, John
  - Re: [sc] A320 Incident Peter B. Ladkin
- Re: [sc] A320 Incident Neale Fulton
  - Re: [sc] A320 Incident Peter B. Ladkin
[sc] Hazop Guidewords Haskins, Tom
- Re: [sc] Hazop Guidewords John McDermid
[sc] report on accident models and causes (safety) leveson(at)sunnyday.mit.edu
- RE: [sc] report on accident models and causes (safety) Martyn Thomas
  - Re: [sc] report on accident models and causes (safety) leveson(at)sunnyday.mit.edu
  - [ata-watchers] Re: [sc] report on accident models and causes (safety) leveson(at)sunnyday.mit.edu
  - RE: [sc] report on accident models and causes (safety) Martyn Thomas
[sc] accidents and incidents... johnson(at)dcs.gla.ac.uk
[sc] accidents and incidents... johnson(at)dcs.gla.ac.uk
[sc] Proof Testing Prior to Use Wise Technics Limited
- Re: [sc] Proof Testing Prior to Use Laurie Blackmore
- RE: [sc] Proof Testing Prior to Use Spriggs, John
- RE: [sc] Proof Testing Prior to Use bill black
- Re: [sc] Proof Testing Prior to Use Paul Gruhn
  - Re: [sc] Proof Testing Prior to Use Wise Technics Limited
  - Re: [sc] Proof Testing Prior to Use Paul Gruhn
- Re: [sc] Proof Testing Prior to Use Marc Pijnenburg
  - Re: [sc] Proof Testing Prior to Use Wise Technics Limited
- RE: [sc] Proof Testing Prior to Use Robin Cook
[sc] Research position in Norway Rune Winther
Re: [sc] Research position in Norway Rune Winther
[sc] Real-time Book Mathai Joseph
[sc]-Compliance to CENELEC 50128 jacqui.newbegin(at)invensys.com
- RE: [sc]-Compliance to CENELEC 50128 Robin Cook
- RE: [sc]-Compliance to CENELEC 50128 Tony Foord
- RE: [sc]-Compliance to CENELEC 50128 Robinson, Paul
[sc] Re: report on accident models and causes (safety) Braband Jens
[sc] Peter Ladkins wba Haskins, Tom
- RE: [sc] Peter Ladkins wba Spriggs, John
- Re: [sc] Peter Ladkins wba Simon Carter
- Re: [sc] Peter Ladkins wba Peter B. Ladkin
[sc] Software Verification Project CKWONG(at)ctrl.co.uk
- Re: [sc] Software Verification Project Kevin Charles Lano
Re: [sc] Re: report on accident models and causes (safety) Peter B. Ladkin
- Re: [sc] Re: report on accident models and causes (safety) leveson(at)sunnyday.mit.edu
  - Re: [sc] Re: report on accident models and causes (safety) Peter B. Ladkin
Re: Not Re:ally accident models and causes leveson(at)sunnyday.mit.edu
- Re: Not Re:ally accident models and causes Peter B. Ladkin
RE: Not Re:ally accident models and causes Robinson, Paul
[sc] Critical Systems Conference, October 2001, Birmingham UK Jonathan Moffett
[sc] MOD For 911 Jackson, William
[sc] SAFETY AND SECURITY CRITICAL SYSTEMS Course, 3rd September--7th September Kevin Charles Lano
- Re: [sc] SAFETY AND SECURITY CRITICAL SYSTEMS Course, 3rd September--7th September John McDermid
- Re: [sc] SAFETY AND SECURITY CRITICAL SYSTEMS Course, 3rd September--7th September Mark Werenowski
RE: [sc] SAFETY AND SECURITY CRITICAL SYSTEMS Course, 3rd Septemb er--7th September Haskins, Tom
New members of the safety-critical mailing list. Jonathan Moffett
New moderator of the safety-critical list Jonathan Moffett
- Re: [sc] New moderator of the safety-critical list david.biddulph(at)baesystems.com
Employment Opportunity: GUI Testers Wise Technics Limited
- Re: [sc] Employment Opportunity: GUI Testers Partha
- I am sorry Partha
request information about medical software failure nadia qureshi
- Re: [sc] request information about medical software failure leveson(at)sunnyday.mit.edu
- Re: [sc] request information about medical software failure Paul Gruhn
  - Re: [sc] request information about medical software failure Pete Mellor
RE: [sc] request information about medical software failure Spriggs, John
Forwarded Message: Re: New Moderator of the Safety-Critical Mailing List Tim Kelly
New Web-Based Archive of the Safety-Critical Mailing List 1995-2001 Tim Kelly
- Re: [sc] New Web-Based Archive of the Safety-Critical Mailing List 1995-2001 Wise Technics Limited
  - Re: [sc] New Web-Based Archive of the Safety-Critical Mailing List 1995-2001 Pete Fenelon
  - Re: [sc] New Web-Based Archive of the Safety-Critical Mailing List 1995-2001 Jonathan Moffett
  - Re: [sc] New Web-Based Archive of the Safety-Critical Mailing List 1995-2001 Tim Kelly
Re: [sc] request information about medical software failure johnson(at)dcs.gla.ac.uk
Medical informatics [sc] johnson(at)dcs.gla.ac.uk
Forwarded Message from Chris Johnson: Medical Informatics Tim Kelly
RE: [sc] request information about medical software failure Simon Hughes
FTA,RBD for maintainability Lars Grunske
Re: [sc] FTA,RBD for maintainability johnson(at)dcs.gla.ac.uk
[sc] I am sorry william.mcgillivray(at)ukaea.org.uk
- Re: [sc] I am sorry Partha
  - Re: [sc] I am sorry Pete Fenelon
Bayesian belief network Ian B Pirie
- Re: [sc] Bayesian belief network Peter B. Ladkin
- Re: [sc] Bayesian belief network John McDermid
- Re: [sc] Bayesian belief network Pete Mellor
Brain surgery by robot (could perhaps be safety-critical? :-) Pete Mellor
Re: [sc] Bayesian belief network johnson(at)dcs.gla.ac.uk
- Re: [sc] Bayesian belief network Trevor.Cockram
- Re: [sc] Bayesian belief network Bev Littlewood
Re: [sc] Bayesian belief network johnson(at)dcs.gla.ac.uk
RE: [sc] Bayesian belief network Michael.Schmidt(at)industrialrisk.com
- RE: [sc] Bayesian belief network Pete Mellor
  - Re: [sc] Bayesian belief network Peter B. Ladkin
Temelin nuclear plant software problem Pete Mellor
The Heavens at War : BBC Radio 4 programme Pete Mellor
[sc] The Heavens at War : BBC Radio 4 programme (fwd) Pete Mellor
Re: [sc] Bayesian belief network Ian B Pirie
- Re: [sc] Bayesian belief network Peter B. Ladkin
Re: [sc] Bayesian belief network johnson(at)dcs.gla.ac.uk
[sc] The Heavens at War: NMD assessed Pete Mellor
More about Star Wars 2: "Letter from America" [sc] Pete Mellor
More about Star Wars 2: "Letter from America" [sc] Pete Mellor
- Re: More about Star Wars 2: "Letter from America" [sc] Peter B. Ladkin
Use of CSP Hutchison Peter B Flt. Lt.
RE: [sc] Use of CSP Rod Chapman
news about recent fuel leak incident leveson(at)sunnyday.mit.edu
Re: more about fuel leak incident Peter B. Ladkin
Risk Assessment Of Hazards Present For a Short Time Wise Technics Limited
- RE: [sc] Risk Assessment Of Hazards Present For a Short Time Edward M. Marszal, P.E.
- Re: [sc] Risk Assessment Of Hazards Present For a Short Time Laurie Blackmore
- Re: [sc] Risk Assessment Of Hazards Present For a Short Time Peter B. Ladkin
  - Re: [sc] Risk Assessment Of Hazards Present For a Short Time Wise Technics Limited
  - Re: [sc] Risk Assessment Of Hazards Present For a Short Time Peter B. Ladkin
RE: [sc] Risk Assessment Of Hazards Present For a Short Time Michael.Schmidt(at)industrialrisk.com
- RE: [sc] Risk Assessment Of Hazards Present For a Short Time Wise Technics Limited
  - RE: [sc] Risk Assessment Of Hazards Present For a Short Time Edward M. Marszal, P.E.
RE: [sc] Risk Assessment Of Hazards Present For a Short Time Robin Cook
RE: [sc] Risk Assessment Of Hazards Present For a Short Time Michael.Schmidt(at)industrialrisk.com
Problems with IEC 61511, CDV, please help Dr. Wolfgang Ehrenberger
RE: [sc] Risk Assessment Of Hazards Present For a Short Time bill black
Automation Gotcha Peter B. Ladkin
RE: [sc] Use of CSP Hutchison Peter B Flt. Lt.
RE: [sc] Automation Gotcha Penny John
- Re: [sc] Automation Gotcha Peter B. Ladkin
Re: [sc] New Web-Based Archive of the Safety-Critical Mailing List 1995-2001 David Smith
RE: [sc] Automation Gotcha Penny John
[sc] Use of controllability or observability properties in safety arguments Chris Harper
- Re: [sc] Use of controllability or observability properties in safety arguments leveson(at)sunnyday.mit.edu
- Re: [sc] Use of controllability or observability properties in safety arguments Axel Poign
- Re: [sc] Use of controllability or observability properties in safety arguments Peter B. Ladkin
. DOVE Announcement Cant, Tony
RE: [sc] Risk Assessment Of Hazards Present For a Short Time Ian.Gibson(at)Fluor.com
- RE: [sc] Risk Assessment Of Hazards Present For a Short Time Martyn Thomas
RE: [sc] Risk Assessment Of Hazards Present For a Short Time Rod Chapman
RE: [sc] Risk Assessment Of Hazards Present For a Short Time Rod Chapman
RE: [sc] Risk Assessment Of Hazards Present For a Short Time Stephen Parker
Y2K bug hits pregnant women [sc] Pete Mellor
[sc] Risk Analysis in Standards, was :Risk Assessment Of Hazards Present For a Short Time Braband Jens
- Re: Risk Analysis in Standards, Peter B. Ladkin
Technical Security Analysis Peter B. Ladkin
- Re: [sc] Technical Security Analysis Pete Mellor
  - RE: [sc] Technical Security Analysis Bertrand Ricque
  - Re: [sc] Technical Security Analysis Gary T. Leavens
RE: Technical Security Analysis: Reply from Frank Taylor Peter B. Ladkin
Re: Technical Security Analysis Peter B. Ladkin
RE: [sc] Technical Security Analysis Garlington, Kennie E
RE: [sc] Technical Security Analysis Michael.Schmidt(at)industrialrisk.com
- RE: [sc] Technical Security Analysis Bertrand Ricque
  - RE: [sc] Technical Security Analysis Pete Fenelon
- Re: [sc] Technical Security Analysis Gary T. Leavens
RE: [sc] Technical Security Analysis Michael.Schmidt(at)industrialrisk.com
Current Topic of Discussion Tim Kelly
- Re: [sc] Current Topic of Discussion Gary T. Leavens
  - Re: [sc] Current Topic of Discussion Mats Heimdahl
- Technical Security Analysis Peter B. Ladkin
  - RE: Technical Security Analysis Michael.Schmidt(at)industrialrisk.com
  - Re: Technical Security Analysis Peter B. Ladkin
  - RE: Technical Security Analysis Michael.Schmidt(at)industrialrisk.com
CfP: International Symposium on Software Testing and Analysis nigel.tracey(at)livedevices.com
Please release me, let me go william.mcgillivray(at)ukaea.org.uk
Call for Papers -- U.S. Software System Safety Working Group leveson(at)sunnyday.mit.edu
New members of the safety-critical mailing list. Tim Kelly
New members of the safety-critical mailing list. Tim Kelly
address change please WellerCS(at)aol.com
Re: [sc] Caches in safety-critical-systems Mathai Joseph
Caches in safety-critical-systems Christian Hoppe
- Re: [sc] Caches in safety-critical-systems Steve White
- RE: [sc] Caches in safety-critical-systems David Crocker
  - RE: [sc] Caches in safety-critical-systems Pete Fenelon
- Re: [sc] Caches in safety-critical-systems Francois Taiani
- Re: [sc] Caches in safety-critical-systems Francois Taiani
  - Re: [sc] Caches in safety-critical-systems Pete Fenelon
RE: [sc] Caches in safety-critical-systems Andy Farnsworth
- Re: [sc] Caches in safety-critical-systems Peter B. Ladkin
Re: [sc] Caches in safety-critical-systems Mathai Joseph
changes in CFP for next meeting of US Software Safety Working Group leveson(at)sunnyday.mit.edu
Call for Contributions - DSN 2002 Dr Tim Kelly
Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric Dock Allen
  - RE: [sc] Rhetoric Martyn Thomas
- Re: [sc] Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric Bev Littlewood
  - RE: [sc] Rhetoric Martyn Thomas
- Re: [sc] Rhetoric Peter Bishop
- Re: [sc] Rhetoric wlmostia
- Re: [sc] Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric wlmostia
- Re: [sc] Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric wlmostia
- Re: [sc] Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric wlmostia
RE: [sc] Rhetoric stuart.palin(at)baesystems.com
RE: [sc] Rhetoric Palmer, Steve
RE: [sc] Rhetoric UK72
- RE: [sc] Rhetoric Martyn Thomas
- Re: [sc] Rhetoric Peter B. Ladkin
RE: [sc] Rhetoric Neale Fulton
RE: [sc] Rhetoric UK72
- RE: [sc] Rhetoric Martyn Thomas
- RE: [sc] Rhetoric Peter Bishop
Re: [sc] Rhetoric johnson(at)dcs.gla.ac.uk
RE: [sc] Rhetoric Simon.Brown(at)hse.gsi.gov.uk
Typo in Interim Defence Standard 00-54 Issue 1 Part 1 David Smith
RE: [sc] Typo in Interim Defence Standard 00-54 Issue 1 Part 1 Spriggs, John
Reminder concerning submissions to this safety critical list being 'bounced' Tim Kelly
Call for abstracts -- U.S. Software System Safety Working Group leveson(at)sunnyday.mit.edu
2nd European COTS User Working Group Workshop L.Beus-Dukic
CALL FOR PAPERS (IPDS) 2002 Dr Tim Kelly
Accident investigation Simon.Brown(at)hse.gsi.gov.uk
Re: [sc] Accident investigation johnson(at)dcs.gla.ac.uk
Re: [sc] request information about medical software failure nadia qureshi
RE: [sc] request information about medical software failure nadia qureshi
Another DEF.STAN.00-56 clarification, please. Spriggs, John
- Re: [sc] Another DEF.STAN.00-56 clarification, please. Peter B. Ladkin
RE: [sc] Another DEF.STAN.00-56 clarification, please. Spriggs, John
- Re: [sc] Another DEF.STAN.00-56 clarification, please. Peter B. Ladkin
RE: [sc] Another DEF.STAN.00-56 clarification, please. Robin Cook
- [sc] For those in Peril on the C John McDermid
  - RE: [sc] For those in Peril on the C Peter Amey
  - Re: [sc] For those in Peril on the C John McDermid
  - RE: [sc] For those in Peril on the C Rod Chapman
  - RE: [sc] For those in Peril on the C Mike Ellims
  - RE: [sc] For those in Peril on the C G.F.
  - Re: [sc] For those in Peril on the C brian wichmann
  - RE: [sc] For those in Peril on the C G.F.
  - RE: [sc] For those in Peril on the C Derek Mannering
  - RE: [sc] For those in Peril on the C Mike Ellims
  - RE: [sc] For those in Peril on the C Andy Farnsworth
  - RE: [sc] For those in Peril on the C Pete Fenelon
  - RE: [sc] For those in Peril on the C Rod Chapman
  - RE: [sc] For those in Peril on the C Andy Farnsworth
  - RE: [sc] For those in Peril on the C Andy Farnsworth
  - RE: [sc] For those in Peril on the C Stephen Parker
  - Re: [sc] For those in Peril on the C John McDermid
  - RE: [sc] For those in Peril on the C Stephen Parker
RE: [sc] Another DEF.STAN.00-56 clarification, please. Simon Hughes
RE: [sc] Another DEF.STAN.00-56 clarification, please. Simon.Brown(at)hse.gsi.gov.uk
- Re: [sc] Another DEF.STAN.00-56 clarification, please. Peter B. Ladkin
- Re: [sc] Another DEF.STAN.00-56 clarification, please. leveson(at)sunnyday.mit.edu
  - Re: [sc] Another DEF.STAN.00-56 clarification, please. Bev Littlewood
  - Re: [sc] Another DEF.STAN.00-56 clarification, please. Peter Bishop
R: [sc] Another DEF.STAN.00-56 clarification, please. Joaquim Marco
R: [sc] Rhetoric Joaquim Marco
- Re: R: [sc] Rhetoric Tim Kelly
- Re: R: [sc] Rhetoric Peter B. Ladkin
- RE: [sc] Rhetoric Steven Crook-Dawkins
Re: [sc] Another DEF.STAN.00-56 clarification, please. Simon.Brown(at)hse.gsi.gov.uk
Handling engineering design process that intended to be compliance with IEC 61508. Larry Cheung
landing gear Mike Ellims
- RE: [sc] landing gear Steven Crook-Dawkins
RE: [sc] Handling engineering design process that intended to be compliance with IEC 61508. Fotis Fotopoulos
RE: [sc] landing gear Graham Tebby
R: R: [sc] Rhetoric Joaquim Marco
- Re: R: R: [sc] Rhetoric Peter B. Ladkin
[Fwd: [sc] Another DEF.STAN.00-56 clarification, please.] Victoria Stavridou
RE: [sc] Another DEF.STAN.00-56 clarification, please. Daniel Moulding
R: R: [sc] Rhetoric Joaquim Marco
R: [sc] landing gear Joaquim Marco
- Re: [sc] landing gear Jon Davies
R: R: R: [sc] Rhetoric Joaquim Marco
- Re: R: R: R: [sc] Rhetoric Peter B. Ladkin
- Re: R: R: R: [sc] Rhetoric Dock Allen
sc Rhetoric johnson(at)dcs.gla.ac.uk
- RE: [sc] sc Rhetoric jon hind
- Re: [sc] sc Rhetoric Charles Waite
  - Re: [sc] sc Rhetoric Peter B. Ladkin
[Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] Tim Kelly
- Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] Bev Littlewood
Rhetoric johnson(at)dcs.gla.ac.uk
R: [sc] Rhetoric Joaquim Marco
Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] David Smith
Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] johnson(at)dcs.gla.ac.uk
Overabundance of Riches Scharbach, Peter N
RE: [sc] For those in Peril on the C Pete Fenelon
Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] Courtois Pierre-Jacques
- Re: FW: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] Peter B. Ladkin
RE: [sc] For those in Peril on the C Pete Fenelon
RE: (MISRA-C) [sc] For those in Peril on the C Rod Chapman
RE: FW: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] Courtois Pierre-Jacques
RE: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.] Michael.Schmidt(at)industrialrisk.com
[Fwd: Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.]] Tim Kelly
- Re: [Fwd: Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification, please.]] johnson(at)dcs.gla.ac.uk
RE: [Fwd: Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification , please.]] Michael.Schmidt(at)industrialrisk.com
- Re: [Fwd: Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification , please.]] leveson(at)sunnyday.mit.edu
  - Re: [Fwd: Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification , please.]] Bob Noel
  - Re: [Fwd: Re: [Fwd: Re: [sc] Another DEF.STAN.00-56 clarification , please.]] Andrew Brydon
RE: [sc] Rhetoric UK72
- Re: [sc] Rhetoric Peter B. Ladkin
Re:[sc] perilous C Martyn Thomas
Re:[sc] perilous C Mathai Joseph
- Re:[sc] perilous C Stephen Bull
RE: [sc] Rhetoric UK72
VISOR Hazard Tracking System Jackson, William
Re: <no subject> brian wichmann
RE: optimization, compilers, safety, etc. Rod Chapman
Re: FW: [sc] For those in Peril on the C Andy Farnsworth
Re: [sc] VISOR Hazard Tracking System JSCOTT900(at)aol.com
Request for information Kevin Rose
- Re: [sc] Request for information Dr. William Goble
RE: [sc] JSF software to be written in C++ Mike Ellims
- Re: [sc] JSF software to be written in C++ Pete Fenelon
ANN: SPARK Tools Release 6.0 Rod Chapman
Point of information, not intended to start a new discussion Spriggs, John
CFP: SAFECOMP 2002 & ECCE-11 Massimo Felici
Re: [sc] Point of information, not intended to start a new discussion JSCOTT900(at)aol.com
Language Formal Definitions brian wichmann
SIL ranges in ENV50129, prEN50129 and Yellow Book 3 Fotis Fotopoulos
- Re: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 John McDermid
Rhetoric About Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric About Rhetoric Pete Fenelon
  - Re: [sc] Rhetoric About Rhetoric Peter B. Ladkin
  - Re: [sc] Rhetoric About Rhetoric John McDermid
- Re: [sc] Rhetoric About Rhetoric John McDermid
- Re: [sc] Rhetoric About Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric About Rhetoric Bev Littlewood
- Re: [sc] Rhetoric About Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric About Rhetoric Peter B. Ladkin
  - Re: [sc] Rhetoric About Rhetoric Peter Bishop
Re: [sc] Rhetoric About C brian wichmann
- Re: [sc] Rhetoric About C Peter B. Ladkin
clarity of thought and expression [sc] Martyn Thomas
Re: [sc] Rhetoric About Rhetoric JSCOTT900(at)aol.com
Re: [sc] Rhetoric About Rhetoric brian wichmann
RE: [sc] Rhetoric About Rhetoric Meine van der Meulen
- Re: [sc] Rhetoric About Rhetoric Philippa Conmy
- Re: [sc] Rhetoric About Rhetoric John McDermid
Re: [sc] Rhetoric About Rhetoric brian wichmann
- Re: [sc] Rhetoric About Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric About Rhetoric Michael Harrison
RE: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 Paul Gruhn, P.E.
Re: [sc] Rhetoric About Rhetoric Peter B. Ladkin
- Re: [sc] Rhetoric About Rhetoric Peter Bishop
  - Re: Re: [sc] Rhetoric About Rhetoric tom(at)faaconsulting.com
DO-178B Simon Hughes
- Re: [sc] DO-178B Peter B. Ladkin
- Re: [sc] DO-178B Steve White
What is language? was: Rhetoric About Rhetoric Peter Amey
- Re: [sc] What is language? was: Rhetoric About Rhetoric John McDermid
Software Sneak Analysis H�gberg, Frode
- Re: [sc] Software Sneak Analysis John McDermid
RE: [sc] DO-178B Rod Chapman
- Re: [sc] DO-178B Steve White
RE: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 Robin Cook
- Re: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 John McDermid
- RE: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 Peter Bishop
- Re: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 David Tombs
RE: [sc] DO-178B Rod Chapman
- Re: [sc] DO-178B Steve White
Sneak, supplementary John McDermid
Re: [sc] What is language? brian wichmann
Registration Laurie Blackmore
- Re: [sc] Registration Margy Aerts
RE: [sc] What is language? was: Rhetoric About Rhetoric Peter Amey
RE: [sc] What is language? was: Rhetoric About Rhetoric Spriggs, John
RE: [sc] DO-178B Rod Chapman
- Re: [sc] DO-178B Steve White
Rhetoric Peter B. Ladkin
clarity of thought and expression [sc] Martyn Thomas
RE: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 Simon Hughes
- RE: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 Dr. Wolfgang Ehrenberger
  - RE: [sc] SIL ranges in ENV50129, prEN50129 and Yellow Book 3 John C. Grebe Jr.
Re: [sc] For those in Peril on the C Gerard Le Lann
Safety-Critical Mailing List will be out of action until the end of next week Tim Kelly
Use of the mailing list Alan Burns
The Safety Critical Mailing List is now back in operation Tim Kelly
[sc] IEC 61508-Frequently asked questions on IEC Website UK72
Jacqui Newbegin/AU/WSA/Rail is out of the office. jacqui.newbegin(at)invensys.com
EAM 2002 CfP johnson(at)dcs.gla.ac.uk
IRIA (Incident and Accident Workshop) CfP johnson(at)dcs.gla.ac.uk
SILs - the return Peter Sheppard
RE: [sc] SILs - the return CKWONG(at)ctrl.co.uk
RE: [sc] SILs - the return Peter Sheppard

Start of Messages	Date view	Subject view	Author view	Other groups

This archive was generated by hypermail 2.0b3 on Fri 21 Dec 2001 - 08:49:56 GMT

tpk(at)cs.york.ac.uk

Safety-Critical Mailing List Archive 2001By Thread

Safety-Critical Mailing List Archive 2001
By Thread