Category: Severity & Priority

Severity & Priority

Severity: How much impact is on system due to particular bug is defined in severity.

Severity is classified as follow:

1. Critical:-There is a functionality that blocks the application is not able to produce any other step or functionality.

2. Major:-Effect on functionality is not as desired and output of any functionality is according to specification.

3. Minor:-Normal bug there is no failure report due to the defect but need to rectify.

4. Cosmetic:-Application look and feel comes in this category.

Priority: How much importance to be given for particular bug such as In Web Application Link is not working may be high priority.

Priority is classified as follow:

1. High:-Resolve the defect at the earlier stage or we can call it urgent level.

2. Low:-Resolve the defect.

3. Very Low:-Could be resolve later on stage.

Examples– Priority/Severity

High Priority & High Severity: A site keep the student details, on saving record if it, doesn’t allow saving the record then this is high priority and high severity bug.

High Priority & Low Severity: The spell mistakes that happens on the cover page or title of an application.

Low Priority and Low Severity: Any cosmetic or spell issues which is within a paragraph or in the report.

High Severity & Low Priority: If the application crashes after using it 100 times, it has high severity but low priority.