Difference between revisions of "Reliability (glossary)"

From SEBoK
Jump to navigation Jump to search
(Created page with '<blockquote>''DEFINITION'' (Citation)</blockquote> If more than one definition, please copy/paste the code for the definition (above) and insert a number in parentheses at the b...')
 
m (Text replacement - "SEBoK v. 2.9, released 13 November 2023" to "SEBoK v. 2.9, released 20 November 2023")
 
(31 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<blockquote>''DEFINITION'' (Citation)</blockquote>
+
<blockquote>''The probability of a system or system element performing its intended function under stated conditions without failure for a given period of time.'' -- modified slightly from (American Society for Quality 2011)</blockquote>
  
If more than one definition, please copy/paste the code for the definition (above) and insert a number in parentheses at the beginning of each definition (i.e. (1), (2), (3), etc.) ‘’’Make sure to include the source citation at the end of the definition.’’’
+
===Sources===
 +
American Society for Quality.  2011. Glossary: Reliability. Accessed on 11 September 2012Available at http://asq.org/glossary/r.html.
  
====Source(s)====
+
===Discussion===
Please include the source(s) for the definition(s) above. The sources should be formatted using Chicago Manual of Style (15th ed.). Please see the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for formatting.
+
This definition is similar to the one found in the ''Defense Acquisition Guidebook'', and the commonly used texts. (DAU 2010) It has four important parts. First, reliability is defined as a probability that a system or system element performs some function. That function must be explicitly defined. Second, the stated operating conditions (which can include environment, load, and any other factor affecting life) must be explicitly stated. Third, a failure must be defined. Last, the appropriate time scale must be specified. This time scale can be chronological, or it can by cycles of operation, miles, landing, or any other measure that is related to the assumed failure mechanism.
 
 
If there is more than one definition, the source for each definition must be provided. Sources should be listed in alphabetical order by author.
 
  
===Discussion===
+
'''Work Cited'''
'''This area is for the ''Glossary Term Owner'' to provide discussion on the context and uses of the term.  This is ''not'' where you should provide comments. '''  Please use the “Discussion” tab (above) to provide feedback if you are not the term owner.
 
  
Please note that if there is more than one definition, it is very important to provide information on the context of the different terms and to explain to the user why it is not possible to identify only one definition. For example, is this an emerging concept for which there is still much research to be done?  Or have two different definitions emerged as the result of two different disciplines interacting with systems engineering?
+
DAU. 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD). February 19, 2010.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
 +
<center>'''SEBoK v. 2.9, released 20 November 2023'''</center>

Latest revision as of 23:35, 18 November 2023

The probability of a system or system element performing its intended function under stated conditions without failure for a given period of time. -- modified slightly from (American Society for Quality 2011)

Sources

American Society for Quality. 2011. Glossary: Reliability. Accessed on 11 September 2012. Available at http://asq.org/glossary/r.html.

Discussion

This definition is similar to the one found in the Defense Acquisition Guidebook, and the commonly used texts. (DAU 2010) It has four important parts. First, reliability is defined as a probability that a system or system element performs some function. That function must be explicitly defined. Second, the stated operating conditions (which can include environment, load, and any other factor affecting life) must be explicitly stated. Third, a failure must be defined. Last, the appropriate time scale must be specified. This time scale can be chronological, or it can by cycles of operation, miles, landing, or any other measure that is related to the assumed failure mechanism.

Work Cited

DAU. 2010. Defense Acquisition Guidebook (DAG). Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD). February 19, 2010.

SEBoK v. 2.9, released 20 November 2023