Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.eso.org/projects/dfs/team/DFS-PR.html
Дата изменения: Wed Apr 13 18:07:46 2005
Дата индексирования: Sun Apr 13 22:53:20 2008
Кодировка:

Поисковые слова: arp 220
DFS Problem Reporting rules and recommendations
 [ ESO ]

DFS Department
DFS Problem Reports




DFS Department Problem Reporting rules and recommendations

 * ALL change requests, bugs or support request on operational releases (i.e. releases already installed and running on the mountain) must be reported via the DFS Problem Reporting tools, based on the Action Remedy system.

 * Problems originated internally by DFS Department during integration tests can be reported either via the DFS project To-Do lists or via the DFS Action Remedy tools.


 * IMPORTANT ! in case of bug, change request or support need directly reported to you via mail or phone call by s DFS user (Paranal, La Silla, DFO, ...), please, check whether an Action Remedy Problem Report is already open. If not, please, ask the DFS user to open a new ticket via the DFS Action Remedy tools.

Indeed, emails can be an easy or quick way to report a DFS issue, but they are usually insufficient : the problem description is often incomplete, several people are missing in the CC list, and after some days and a certain amount of emails, it's usually difficult to retrieve them.

On contrary, a problem recorded via our DFS Action Remedy schema is a good mean to be sure to find in an unique centralized place ALL information exchanged between several persons about the same topic.

It is also a practical mean to be able to evaluate trends for DFS Quality level.

 * Please, go to the following link to query or submit Problem Reports for DFS components, using our DFS Action Remedy tool.

 * All tickets originated via the DFS AR tools are regularly analyzed (1 or 2 times a month) via specific meetings called SCCB meetings.


 [Project and Developments]  [Overview page for this document]  [ESO]  [Index]  [Search]  [Help]  [News]