Newer
Older
Angelina Elizabeth Uno-Antonison
committed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
# Defect Taxonomy and Defect Logging
The purpose of this taxonomy is to be used in classifications of injected bugs.
These bugs are the starting point, if post mortem's reveal we have an
abudnance of a certain type of bug, this reveals an area for room to improve
as well as a potential reason to increase the granularity of a defect type.
## Taxonomy
### Documentation
Comments, messages, etc.
### Syntax
Spelling, punctuation, typos, instruction formats, etc.
### Build/Package
Change management issues, librariy issues, dependencie issues, version issues.
### Assignment
Decleration, naming, scope, bounds/limit issues
### Interface
Procedure calls and references, I/O, user formats
### Checking
Error Messages (stack trace trouble shooting), inadequete error checks
### Data
Structure, content, fixture issues
### Function
Business Logix, loops, recursion, copmputation, and other function issues.
### System
Configuration, timing, memory issues
### Enviornment
Design, compile, test, or other support system problems
## Defect Logging
Logging Defects is encouraged at an individual level (for Personal development
improvement) and required for all bugs that make their way into master branches
of code so our team process can be improved. That is, we can retoroactively
improve our process to reduce bugs that make their way into master branches
of code.
### Personal Defect Logging
This is up to the discretion and/or guidance of both the individual dev as
well as their supervisor
### Team Defect Logging
This will take place in Wrike, in the respective project under a `Defect Log`
folder.