Explicit bug

Implicit bug CRE

An explicit bug is existing functionality in software that is not operating as designed or required.

There is no grey area. The functionality should be doing A, and it is doing B. It’s not an implicit bug.

Extra – how best to communicate explicit bug

Three bits of info required:

  1. What did I do to get there (what steps did I take)
  2. What should happen (my expected behaviour)
  3. What happened instead

Adding screenshots is generally very helpful

Advanced – bug classification

This informs urgency. The lower the below score, the more time sensitive resolution is by the service provider.

A higher score means that the issue is having a low impact on the business.

Issue categories are as follows:

CategoryScoreDescription
Critical0-2Halts critical processes
Major3-9Encumbers processes
Medium10-20Impairs non-critical system functioning
Low21-64Low negative impact on process

Priority or severity is determined by the following formula: Severity/impact x Pervasiveness x Nature

For example: the Severity/impact score of an issue is a 3, the Pervasiveness score of the same issue is 1, the Nature of the same issue is 0 –> the score (3 x 1 x 0) is 0. Issue is assigned to category Critical.

 

Severity/impact
ScoreDescription
0Affects critical data or functionality and leaves users with no workaround
1Affects critical data or functionality and forces users to employ a workaround
1Lack of feature/feature issue creates data work “debt”
2Affects non-critical data or functionality and forces users to employ a workaround
3Affects non-critical data or functionality and forces users to employ a workaround
4Affects aesthetics, professional look and feel, “quality” or “usability”

 

Pervasiveness: Likelihood/visibility
ScoreDescription
1Experienced by all or almost all users who use the application (>=95% of users)
2Experienced by more than 2/3 of the users who use the application (>67% and <95%)
3Experienced by about half the users who use the application (>33% and <66%)
4Experienced by about 1/3 or less of the users who use the application (>0% and <32%

 

Nature: Class of defect
ScoreDescription
0Stability, reliability and availabilityTestability
0SecurityStorage (data loss/corruption)
0Legal (liability, copyright)
1Performance and efficiency

(use of resources: memory, disk, CPU)

Scalability
2FunctionalityCompatibility
2Logic or calculationInteroperability
3UsabilityDocumentation
3Learn abilityConsistency
3ReadabilityWorkflow
4Typographic or grammaticalAppearance or cosmetic
4Aesthetics

These impact codes are recommended to be used as guidelines.

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.
You need to agree with the terms to proceed

Content categories

Subscribe to the Mavenway

Want this content in your inbox monthly?

Menu