Rules
Risk Assessment Summary
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
OBJ01-J | Medium | Likely | Medium | P12 | L1 |
OBJ02-J | Medium | Probable | High | P4 | L3 |
OBJ03-J | Low | Probable | Medium | P4 | L3 |
OBJ04-J | Low | Likely | Medium | P6 | L2 |
OBJ05-J | High | Probable | Medium | P12 | L1 |
OBJ06-J | Medium | Probable | High | P4 | L3 |
OBJ07-J | Medium | Probable | Medium | P8 | L2 |
OBJ08-J | Medium | Probable | Medium | P8 | L2 |
OBJ09-J | High | Unlikely | Low | P9 | L2 |
OBJ10-J | Medium | Probable | Medium | P8 | L2 |
OBJ11-J | High | Probable | Medium | P12 | L1 |
OBJ13-J | Medium | Likely | Low | P18 | L1 |
OBJ14-J | Medium | Likely | High | P6 | L2 |
3 Comments
Jonathan Paulson
Rogue 2000 Rule 71: Make all fields private. This might be a good rule to add.
David Svoboda
OBJ01-J is supposed to cover the problem of non-private fields...doesn't it?
Axel Hauschulte
I am wondering what happened to OBJ00-J. Limit extensibility of classes and methods with invariants to trusted subclasses only. It is in the printed edition of the Coding Standard and assessed with priority P12 and Level L1 in the table above, but I cannot find it online.