Severity level criteria

This section explains the severity levels indicated in the issue reports.

In HULFT, issues are classified into four levels according to the following criteria:

Severity level: A (critical)

Description

Example of a Situation Users May Face

Defects that significantly affect business systems or transfer operations

  • Product defects that cause incorrect user data

  • Product defects that prevent businesses from continuing in the product-operating environment

  • Product defects that cause unavoidable problems with business collaboration

  • Product defects that lead to security risks

  • Product defects that cause the product to unexpectedly terminate or freeze

and so on

Severity level: B (high)

Description

Example of a Situation Users May Face

Defects that affect transfer operations (not including severity level A)

  • Product defects that cause the transfer processing to fail under certain conditions

  • Product defects that cause problems with transfer completion notifications (such as incorrect log records, incorrect messages)

  • Product defects that cause problems with product management information (such as inability to register, incorrect information)

  • Product defects that cause error codes and messages that differ from the specifications to be output, which affects business

and so on

Severity level: C (medium)

Description

Example of a Situation Users May Face

Defects that do not directly affect transfer operations

  • Product defects that cause problems under certain conditions during installation

  • Product defects that cause problems with the output information that is not directly related to transfer operations

  • Product defects that cause problems with the operation of the screen

  • Product defects that cause problems with utility operations

and so on

Severity level: D (low)

Description

Example of a Situation Users May Face

Defects that do not directly affect operations such as display problems

  • Product defects that cause minor problems in output errors (such as a typographical error)

  • Product defects that cause registration errors that do not affect transfer operations (such as registration of comments)

and so on