Table of Contents

Enum Severity

Namespace
NDepend.TechnicalDebt
Assembly
NDepend.API.dll

This enumeration defines the level of severity that an issue can have.

public enum Severity
Extension Methods

Fields (8)

Blocker = 4

An issue with a severity level Blocker cannot move to production, it must be fixed.

Critical = 3

An issue with a severity level Critical shouldn't move to production. It still can for business imperative needs purposes, but at worth it must be fixed during the next iterations.

High = 2

An issue with a severity level High should be fixed quickly, but can wait until the next scheduled interval.

[Obsolete("Use Severity.Low instead")] Info = 0

Use Severity.Low instead

Low = 0

The severity level Low is used by issues that have a zero, or close to zero, value for AnnualInterest.

Issues with a Low severity level represents small improvements, ways to make the code looks more elegant.
The Broken Window Theory https://en.wikipedia.org/wiki/Broken_windows_theory states that: Consider a building with a few broken windows. If the windows are not repaired, the tendency is for vandals to break a few more windows. Eventually, they may even break into the building, and if it's unoccupied, perhaps become squatters or light fires inside..

Issues with a Low or Medium severity level represents the broken windows of a code base. If they are not fixed, the tendency is for developers to not care for living in an elegant code, which will result in extra-maintenance-cost in the long term.

[Obsolete("Use Severity.High instead")] Major = 2

Use Severity.High instead

Medium = 1

An issue with a severity level Medium is a warning that if not fixed, won't have a significant impact on development.

[Obsolete("Use Severity.Medium instead")] Minor = 1

Use Severity.Medium instead

Remarks

The severity of an issue depends on the AnnualInterest the issue, expressed in man-time per year, and is obtained from the severity thresholds defined in DebtSettings.