"A property of neural computing systems that allows the system to function and gradually degrade when a small number of processing elements are destroyed or disabled." (Guido Deboeck & Teuvo Kohonen (Eds), "Visual Explorations in Finance with Self-Organizing Maps" 2nd Ed., 2000)
"Fault Tolerance is the ability of an IT system to continue to function as designed even though a fault has occurred." (Martin Oberhofer et al, "Enterprise Master Data Management", 2008)
"The ability of a system to provide an uninterrupted service, despite the failure of one or more of the system’s components." (Judith Hurwitz et al, "Service Oriented Architecture For Dummies" 2nd Ed., 2009)
"The ability of a system or component to continue normal operation despite the presence of hardware or software faults." (Mark S Merkow & Lakshmikanth Raghavan, "Secure and Resilient Software Development", 2010)
"The capability of a system to provide uninterrupted service despite the failure of one or more of the system’s components." (Marcia Kaufman et al, "Big Data For Dummies", 2013)
"1. The capability of the software product or a component to maintain a specified level of performance in case of wrong inputs (see also robustness). 2. The capability of the software product or a component to maintain a specified level of performance in case of software faults (defects) or of infringement of its specified interface." (Tilo Linz et al, "Software Testing Foundations" 4th Ed., 2014)
"The ability of a system to tolerate a fault and continue to operate. Fault tolerance systems often use redundant hardware, such as additional hard drives or additional servers, to eliminate a single point of failure." (Darril Gibson, "Effective Help Desk Specialist Skills", 2014)
"Ability to continue operate after failure of a component part" (ITIL)
"The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified interface." (ISO 9126)
No comments:
Post a Comment