This defect type standard is derived from an article in the "IEEE Transactions on Software Engineering" [1]. It is also presented in "A Discipline for Software Engineering" [2]. Small adjustments to the descriptions were added for clarity. Also, TRDC finds the 3 letter text tags more convenient than the numbers. Note that sub-categories can be defined, with numbers between the "10's" of the major categories. For the text tags, the the sub tag is separated by a "/". The tags (or numbers) are crucial to support post analysis of the defect logs when implementing a more complex SEI process.
| Defect Type ID |
Defect Type Number |
Type Name | Description |
|---|---|---|---|
| doc | 10 | Documentation | comments, messages |
| syn | 20 | Syntax | spelling, punctuation, typos, instruction formats |
| bop | 30 | Build, Packaging | change management, library maintenance, version control |
| asn | 40 | Assignment | declaration, duplicate names, scope, limits |
| int | 50 | Interface | method calls and references, I/O, user formats |
| chk | 60 | Checking | error messages, inadequate checks |
| dat | 70 | Data | structure, content |
| fun | 80 | Function | logic, pointers, references, loops, recursion, computation, method defects |
| sys | 90 | System | configuration, timing, memory utilization |
| env | 100 | Environment | design, compile, test, environmental settings, other system support problems |
[1] R. Chillarege, I. Bhandari, J. Chaar, M. Halliday, D. moebus, B. Ray, and M.-Y Wong: "Orthogonal Defect Classification - A concept of In-Process Measurements," IEEE Transactions on Software Engineering, vol 18, no. 11 (Nov 1992): 943-956
[2] Watts S. Humphrey: "A Discipline for Software Engineering," Addison Wesley, p661.
$Id: defect-types.html,v 1.2 2002/02/15 21:53:40 rlv Exp $
$Name: $