Reliability - Revision history

Admin: Reverted edits by Ysukivewug (talk) to last revision by Napseloff

2010-11-29T17:48:20Z

Reverted edits by Ysukivewug (talk) to last revision by Napseloff

Junk at 01:59, 24 November 2010

2010-11-24T01:59:25Z

Napseloff at 03:37, 18 December 2009

2009-12-18T03:37:40Z

Pteifer at 16:52, 14 September 2009

2009-09-14T16:52:09Z

Napseloff at 02:44, 5 October 2008

2008-10-05T02:44:05Z

Napseloff: /* Events involving reliability */

2008-09-23T15:45:56Z

‎Events involving reliability

New page

==Definitions==
*Basic definition - Information that can be depended upon with confident certainty; absence of NO error, breakdown, or or performance.<ref name="one">http://dictionary.reference.com/browse/reliability, Retrieved 9/11/08</ref>

*Technology definition - The trustworthiness to do what the system is expected or designed to do.<ref name ="two">http://www.answers.com/topic/reliability-technology, Retrieved 9/11/08</ref> Any system that consistently produces the same results<ref name="one"/>

*Computer Networking definition - A reliable protocol ensuring reliability properties with respect to the delivery of data to the intended recipient(s), as opposed to unreliable protocol, which does not guarantee that data will be delivered intact, or that it will be delivered at all.<ref name="two"/>

*Layman's definition - How reliable is it?
:*reliable – giving the same result after repeated trials / usages

*Explanation to a 12 year old - The probability that something will do what it is supposed to do.

===Different types of reliability in technology===

*POFOD (probability of failure on demand):

:*The likelihood that the system will fail when a user requests service. A biometric authentication device that fails to correctly identify or reject users an average of once out of a hundred times has a POFOD of 1%.<ref name="two"/>

*ROCOF (rate of failure occurrence):

:*The number of unexpected events over a particular time of operation. A firewall that crashes an average of five times every 1,000 hours has a ROCOF of 5 per 1,000 hours.<ref name="two"/>

*MTTF (mean time to failure):

:*The average time between unexpected events. If an IDS fails on average every 300 hours, its MTTF is 300 hours.<ref name="two"/>

*AVAIL (availability or uptime):

:*The percentage of time that a system is available for use, taking into account planned and unplanned downtime. If a system is down an average of four hours out of 100 hours of operation, its AVAIL is 96%.<ref name="two"/>

==Importance of reliability==
Now that technology and computers are so often used in an innumerable amount of places, reliability is becoming a critical aspect of information technology in our society.

For example, the software used in airplanes and air traffic control centers must be extremely reliable, considering the fact that many lives are in grave danger in the event of a failure.

==Events involving reliability==
*In 1999, the Mars Climate Orbiter crashed because the programmers who wrote the code for the software neglected to translate English measurement units to metric units.<ref>http://mars.jpl.nasa.gov/msp98/news/mco991110.html, Retrieved 9/20/08</ref>

*An new Airbus A320 crashed at an airshow in France on June 26, 1988 because of faulty software that caused his altimeter to not respond properly resulting in the pilot crashing into trees, killing the three passengers in his plane.<ref>http://catless.ncl.ac.uk/Risks/8.77.html#subj6, Retrieved 9/20/08</ref>

*Therac-25, a computerized radiation therapy machine for cancer patients, was the cause of six accidents, ending in death or critical injury, due to the software wrongly administering an overdose.<ref>http://courses.cs.vt.edu/~cs3604/lib/Therac_25/Therac_1.html, Retrieved 9/20/08</ref>

==Authors==
Nick Apseloff and Ricardo Aldana

==References==
<references/>

← Older revision		Revision as of 03:37, 18 December 2009
Line 45:		Line 45:

	==References==		==References==
−	<~~http://torrentfreak.com/its-time-to-sink-the-pirate-bay-and-replace-it-090913/~~/>	+	<references/>

← Older revision		Revision as of 16:52, 14 September 2009
Line 45:		Line 45:

	==References==		==References==
−	<~~references~~/>	+	<http://torrentfreak.com/its-time-to-sink-the-pirate-bay-and-replace-it-090913//>

@@ Line 1: / Line 1: @@
 ==Definitions==
-*Basic definition - Information that can be depended upon with confident certainty; absence of NO error, breakdown, or or performance.&lt;ref name="one">http://dictionary.reference.com/browse/reliability, Retrieved 9/11/08&lt;/ref>
+*Basic definition - Information that can be depended upon with confident certainty; absence of NO error, breakdown, or or performance.<ref name="one">http://dictionary.reference.com/browse/reliability, Retrieved 9/11/08</ref>
-*Technology definition - The trustworthiness to do what the system is expected or designed to do.&lt;ref name ="two">http://www.answers.com/topic/reliability-technology, Retrieved 9/11/08&lt;/ref> Any system that consistently produces the same results&lt;ref name="one"/>
+*Technology definition - The trustworthiness to do what the system is expected or designed to do.<ref name ="two">http://www.answers.com/topic/reliability-technology, Retrieved 9/11/08</ref> Any system that consistently produces the same results<ref name="one"/>
-*Computer Networking definition -  A reliable protocol ensuring reliability properties with respect to the delivery of data to the intended recipient(s), as opposed to  unreliable protocol, which does not guarantee that data will be delivered intact, or that it will be delivered at all.&lt;ref name="two"/>
+*Computer Networking definition -  A reliable protocol ensuring reliability properties with respect to the delivery of data to the intended recipient(s), as opposed to  unreliable protocol, which does not guarantee that data will be delivered intact, or that it will be delivered at all.<ref name="two"/>
 *Layman's definition - How reliable is it?
@@ Line 23: / Line 15: @@
 *POFOD (probability of failure on demand):
-:*The likelihood that the system will fail when a user requests service. A biometric authentication device that fails to correctly identify or reject users an average of once out of a hundred times has a POFOD of 1%.&lt;ref name="two"/>
+:*The likelihood that the system will fail when a user requests service. A biometric authentication device that fails to correctly identify or reject users an average of once out of a hundred times has a POFOD of 1%.<ref name="two"/>
 *ROCOF (rate of failure occurrence):
-:*The number of unexpected events over a particular time of operation. A firewall that crashes an average of five times every 1,000 hours has a ROCOF of 5 per 1,000 hours.&lt;ref name="two"/>
+:*The number of unexpected events over a particular time of operation. A firewall that crashes an average of five times every 1,000 hours has a ROCOF of 5 per 1,000 hours.<ref name="two"/>
 *MTTF (mean time to failure):
-:*The average time between unexpected events. If an IDS fails on average every 300 hours, its MTTF is 300 hours.&lt;ref name="two"/>
+:*The average time between unexpected events. If an IDS fails on average every 300 hours, its MTTF is 300 hours.<ref name="two"/>
 *AVAIL (availability or uptime):
-:*The percentage of time that a system is available for use, taking into account planned and unplanned downtime. If a system is down an average of four hours out of 100 hours of operation, its AVAIL is 96%.&lt;ref name="two"/>
+:*The percentage of time that a system is available for use, taking into account planned and unplanned downtime. If a system is down an average of four hours out of 100 hours of operation, its AVAIL is 96%.<ref name="two"/>
 ==Importance of reliability==
@@ Line 43: / Line 35: @@
 ==Events involving reliability==
-*In 1999, the Mars Climate Orbiter crashed because the programmers who wrote the code for the software neglected to translate English measurement units to metric units.&lt;ref>http://mars.jpl.nasa.gov/msp98/news/mco991110.html, Retrieved 9/20/08&lt;/ref>
+*In 1999, the Mars Climate Orbiter crashed because the programmers who wrote the code for the software neglected to translate English measurement units to metric units.<ref>http://mars.jpl.nasa.gov/msp98/news/mco991110.html, Retrieved 9/20/08</ref>
-*An new Airbus A320 crashed at an airshow in France on June 26, 1988 because of faulty software that caused his altimeter to not respond properly resulting in the pilot crashing into trees, killing the three passengers in his plane.&lt;ref>http://catless.ncl.ac.uk/Risks/8.77.html#subj6, Retrieved 9/20/08&lt;/ref>
+*An new Airbus A320 crashed at an airshow in France on June 26, 1988 because of faulty software that caused his altimeter to not respond properly resulting in the pilot crashing into trees, killing the three passengers in his plane.<ref>http://catless.ncl.ac.uk/Risks/8.77.html#subj6, Retrieved 9/20/08</ref>
-*Therac-25, a computerized radiation therapy machine for cancer patients, was the cause of six accidents, ending in death or critical injury, due to the software wrongly administering an overdose.&lt;ref>http://courses.cs.vt.edu/~cs3604/lib/Therac_25/Therac_1.html, Retrieved 9/20/08&lt;/ref>
+*Therac-25, a computerized radiation therapy machine for cancer patients, was the cause of six accidents, ending in death or critical injury, due to the software wrongly administering an overdose.<ref>http://courses.cs.vt.edu/~cs3604/lib/Therac_25/Therac_1.html, Retrieved 9/20/08</ref>
 ==Authors==
@@ Line 53: / Line 45: @@
 ==References==
-&lt;references/>
+<references/>