user128807
user128807

Reputation: 10547

Taxonomy/Ontology of software bugs?

Is there a taxonomy of ontology of software bugs?

Upvotes: 1

Views: 608

Answers (3)

Paul
Paul

Reputation: 21

Security-wise, a well known taxonomy of software bugs (introduced to a wider audience by Gary McGraw in his series of books on software security) distinguishes between an implementation bug and a design flaw. An implementation bug is a low-level defect lurking in your implementation. A typical example for an implementation bug is a buffer overflow. A design flaw, on the other hand, is a 'logic' bug within your implementation that allows a malicious person to break or circumvent your system or some security mechanism you implemented simply by using it in a manner you didn't anticipate. A good example for this are flaws in API design which allow an attacker to combine specific calls to the API to force the system to do things that the designers of the system did not anticipate.

Upvotes: 0

T.E.D.
T.E.D.

Reputation: 44804

There's the beginnings of one on the Wikipedia page for Software Bugs. It lists them by their cause though. Personally I find that less useful than a system that would list them by their manefestation, because you don't really know the cause until you've debugged it.

Also, that causal approach by defintion leaves off my two favorite bugs, the Heisenbug and the Schrodenbug.

Upvotes: 2

kirilloid
kirilloid

Reputation: 14304

Many bugs are rather specific to the language. If you're looking for cross-language errors/mistakes, you may start from anti-patterns

Upvotes: 2

Related Questions