What is the difference between defect and fault

This defect is a variance from the given specification. It is Wrong! A requirement of the customer that was not fulfilled. This is a variance from the specifications, an indication that a specification was not implemented, or a requirement of the customer was not noted correctly.

A requirement incorporated into the product that was not given by the end customer. This is always a variance from the specification, but maybe an attribute desired by the user of the product. An error is a mistake, misconception, or misunderstanding on the part of a software developer. In the category of the developer, we include software engineers, programmers, analysts, and testers.

For example, a developer may misunderstand a de-sign notation, or a programmer might type a variable name incorrectly — leads to an Error. It is the one that is generated because of the wrong login, loop or syntax.

The error normally arises in software; it leads to a change in the functionality of the program. A bug is the result of a coding error. Possible Duplicate: Difference between defect and bug in testing. In computer science technical writing, especially in software engineering, what's the difference between fault, error and defect?

To quote the Software Engineering Body of Knowledge. 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 IEEE Based on my understanding of above definition, error is the result of fault, i.

Could someone explain more clearly? According to Fundamental Concepts of Dependability :. A system failure is an event that occurs when the delivered service deviates from correct service. A system may fail either because it does not comply with the specification, or because the specification did not adequately describe its function.

An error is that part of the system state that may cause a subsequent failure: a failure occurs when an error reaches the service interface and alters the service. A fault is the adjudged or hypothesized cause of an error. With reference to the definitions used in the linked article, an error is not the result of a fault, but potentially the cause - if the error is outside of the tolerance of the system. Most systems dealing with real data have some degree of error, but are designed to tolerate them.

Sign up to join this community. Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. What's New. Most popular in Difference Between. The Testers identify the defect. And it was also solved by the developer in the development phase or stage. Different type of bugs are as follows: Logic bugs Algorithmic bugs Resource bugs.

Following are reasons which may cause the bugs: Missing coding Wrong coding Extra coding. The below reason leads to the defects : Giving incorrect and wrong inputs. Dilemmas and errors in the outside behavior and inside structure and design. An error in coding or logic affects the software and causes it to breakdown or the failure.

The reasons for having an error are as follows: Errors in the code. The Mistake of some values. If a developer is unable to compile or run a program successfully. Confusions and issues in programming. Invalid login, loop, and syntax. Inconsistency between actual and expected outcomes.

Blunders in design or requirement actions. Misperception in understanding the requirements of the application. The reasons behind the fault are as follows: A Fault may occur by an improper step in the initial stage, process, or data definition. Inconsistency or issue in the program. An irregularity or loophole in the software that leads the software to perform improperly. Following are some of the most important reasons behind the failure: Environmental condition System usage Users Human error.

Following are the way to stop the bugs : Test-driven development. Offer programming language support. Adjusting, advanced, and operative development procedures. Evaluating the code systematically. With the help of the following, we can prevent the Defects : Implementing several innovative programming methods. Use of primary and correct software development techniques.

Peer review It is executing consistent code reviews to evaluate its quality and correctness. Below are ways to prevent the Errors : Enhance the software quality with system review and programming. Detect the issues and prepare a suitable mitigation plan.