Error Fault
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might error fault and failure difference have Meta Discuss the workings and policies of this site About
Error Fault In Nonpaged Area
Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting segmentation fault error ads with us Programmers Questions Tags Users Badges Unanswered Ask Question _ Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual
Protection Fault Error
questions about software development. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top What's the difference between fault, error and defect? [duplicate] up vote 9 down vote favorite 5 Possible Duplicate: Difference windows error fault bucket between defect and bug in testing In computer science technical writing, especially in software engineering, what's the difference between fault, error and defect? I want to quote an answer on Stack OverFlow by Daniel Joseph: To quote the Software Engineering Body of Knowledge Typically, where the word “defect” is used, it refers to a “fault” as defined below. However, different cultures and standards may use somewhat different meanings for these terms, which have led to attempts to define them. Partial definitions taken from standard (IEEE610.12-90) are: Error: “A difference…between a computed result and the correct result” Fault: “An incorrect step, process, or data definition in a computer program” Failure: “The [incorrect] result of a fault” Mistake: “A human action that produces an incorrect result” Based on my understanding of above definition, error is the result of fault, i.e., failure. Could someone explain more clearly? terminology quality share|improve this question edited Jan 22 '13 at 11:05 Thomas Owens♦ 47k12117200 asked Jan 20
failure. In telecommunications, according to the Federal Standard 1037C of the United States, the term fault has the following meanings: An accidental condition that causes a functional unit to fail to
Difference Between Error And Fault
perform its required function. See §Random fault. A defect that causes a reproducible
Error Fault Failure Defect
or catastrophic malfunction. A malfunction is considered reproducible if it occurs consistently under the same circumstances. See §Systematic fault. In power difference between error fault and failure with example systems, an unintentional short-circuit, or partial short-circuit, between energized conductors or between an energized conductor and ground. A distinction can be made between symmetric and asymmetric faults. See Fault (power engineering). Random fault[edit] http://programmers.stackexchange.com/questions/184412/whats-the-difference-between-fault-error-and-defect A random fault is a fault that occurs as a result of wear or other deterioration. Whearas the time of a particular occurrence of such a fault cannot be determined, the rate at which such faults occur within the equipment population on average can be predicted with accuracy. Manufacturers will often accept random faults as a risk if the chances are virtually negligible. A fault can happen https://en.wikipedia.org/wiki/Fault_(technology) in virtually any object or appliance, most common with electronics and machinery. For example, an Xbox 360 console will deteriorate over time due to dust buildup in the fans. This will cause the Xbox to overheat, cause an error, and shut the console down.[citation needed] Systematic fault[edit] Systematic faults are often a result of an error in the specification of the equipment and therefore affect all examples of that type. Such faults can remain undetected for years, until conditions conduce to create the failure. Given the same circumstances, each and every example of the equipment would fail identically at that time. Failures in hardware can be caused by random faults or systematic faults, but failures in software are always systematic[citation needed] See also[edit] Product defect Reliability engineering Software bug Defect (disambiguation) Fault (disambiguation) This technology-related article is a stub. You can help Wikipedia by expanding it. v t e Retrieved from "https://en.wikipedia.org/w/index.php?title=Fault_(technology)&oldid=676974935" Categories: Fault toleranceSoftware anomaliesComputer errorsTechnology stubsHidden categories: All articles with unsourced statementsArticles with unsourced statements from December 2011Articles with unsourced statements from August 2015All stub articles Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces Article Talk Variants Views Read Edit View history More Search Navigation M
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers http://stackoverflow.com/questions/6323049/understanding-what-fault-error-and-failure-mean or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Understanding what Fault, Error and Failure mean up vote 2 down vote favorite 1 Consider the following class: class Xyz { public int count; public void numZero (int[] x) { // Effects: if x error fault == null throw NullPointerException // else return the number of occurrences of 0 in x int count = 0; for (int i = 1; i < x.length; i++) //we have a bug here { if (x[i] == 0) { count++; } } this.count = count; } } I'm trying to wrap my head about what Fault, Error and Failure really mean. Fault From what I've come to understand, a Fault in this context would be a flaw in the code's written error fault and logic. So in this case the Fault would be the fact that the code instructs the computer to start iterating over all elements of v with a start index of 1 instead of the expected 0. Error When running the above method, we always get an Error but in once instance (when v.length == 0), as what we really want is to iterate over all elements of x, but since we're starting with i = 1, that is not really happening. With an empty vector as input, as we don't enter the for loop, so our incorrect code isn't run, meaning that the Error doesn't happen, and everything happens as should in theory. Failure Since our code has a Fault that in execution-time will almost always manifest in a Error, we only have a Failure when we effectively see the incorrect output. Assuming that an Error effectively happened in my program, we only have a Failure if it is in some way visible to the outside world. That is, had I private int count; instead of public int count; I'd never ever have an Error in my class (of course it'd be the most useless class ever!). Is this right? Is everything I said correct or am I erring in something? Thanks testing share|improve this question edited Jun 13 '11 at 15:50 user7116 47.5k11100146 asked Jun 12 '11 at 16:22 devoured elysium 28.6k70229407 This belongs at en