メンテナンスのお知らせ(2010年3月20日 - 日本時間)

2010年3月20日午後12時より翌日にかけて(米国時間の3月19日午後7時より翌日)、いくつかのデータベースとWebアプリケーションサーバーを新しいデータセンターに移設します。

サービス停止時間は最小にとどめるよう努力いたしますが、作業期間中、一時的にシステムをご利用いただけないことがあります。ご迷惑をおかけいたしますが、ご理解いただきますようお願い申し上げます。

CodeGear Severity Level Definitions

概要: Abstract: CodeGear defines three severity levels for classifying developer support cases

Borland defines three Severity Levels for classifying technical support cases:

  • Severity 1 - Critical: An incident that results in a critical business impact for a Production System; may be assigned to an Incident where customer experiences (i) a complete or substantial loss of service when using a Production System, or (ii) real or perceived data loss or data corruption making an essential part of the Production System unusable, or (iii) the inability to use a mission critical application within a Production System.
  • Severity 2 - Significant: An incident that results in some business impact for a Production System or Development System; maybe be assigned to an incident where customer experiences (i) the functionality of the software is adversely affected, but can be circumvented, or (ii) certain functions within the software are disabled, but the Software remains operable, or (iii) a complete or substantial loss of service when using a Development System.
  • Severity 3 - Normal: An incident that results in a minimal business impact for a Production System or Development System; may be assigned to an incident where customer experiences no loss of service and the incident has no significant effect on the usability of the software. This level is typically used for questions, comments and enhancement requests.