2 PROBLEM REPORTING/CHANGE REQUEST

To report problems/errors, suggest changes in software or documentation or to require clarification, please use the VLT Software Problem Report (VLTSPR) Utility.

VLTSPR is build using the commercial tool Action Remedy (c) and has a Web Browser interface.

Access is granted to registered users only via a login procedure.

If you are aware of other persons on your working team that need access to the system, please send the following information:

1. Login name

2. Full Name

3. Institute address and phone number

4. Full email address

to vltsccm@eso.org and an account will be set for him.

2.1 LOGIN INTO VLT SPR

Run netscape (or another Web browser), connect to VLT Software development page:

http://www.eso.org/projects/vlt/sw-dev/

and select VLT Software Problem Report. The login page is shown. Provide your identification in terms of username and password

If you have problems accessing the system or you have forgot your password contact:

vltsccm@eso.org

2.2 VLT SPR SUBMIT

To submit an SPR use the following procedure:

1. login into VLT SPR system

2. mark VLT SPR radio button on the Login section and click Submit

3. The submit page should be displayed. Fill it as explained. The fields whose labels display in bold type are mandatory, the other optional.

4. Click Submit. The SPR will be added to the archive. The initial Status is "Open".

Remember to specify the Consortium you belong to on the Location field.

Normally each software component is labeled with a name and a revision number.This name and number are the ones used in the VLT Software Archive (CMM Archive). When submitting an SPR, please identify the file or module that gives problem on the Module Name and Module Version fields. To identify an existing file you can use the which and what UNIX utility as in the following example:

$ which dbl

/vlt/bin/dbl

$ what /vlt/bin/dbl

/vlt/bin/dbl:

$Id: dblInit.tcl,v 1.8 1995/03/08 13:46:53 gchiozzi Exp $

$Id: dblMisc.tcl,v 1.8 1995/03/08 ....

....

In this case, the module is dbl 1.8.

If the what command does not give output or if you are not sure about it or if you cannot identify which module or family (LCC, CCS, Drivers, etc.), please indicate the VLTSW release you are using (e.g.: OCT98) in the Synopsis field of the SPR. Do not forget to specify how to reproduce the problem!

2.3 VLT SPR QUERY

The VLT SPR QUERY functionalities are available after the following procedure:

1. login into VLT SPR system

2. mark VLT SPR radio button on the Query section and click Query

3. The Query page should be displayed

From there on is possible to perform the following main operations:

Get a list of SPR: the selection can be performed using one or more of the available fields. Once the searching rules are set, click on Run Query As result of the selection a list of suitable SPR(s) is displayed.

Display an SPR: Specify the SPR number and press Run Query or if the SPR appears already on the list of displayed SPRs, simply click on Display for the entry in the list.

Add a Remark: To add a remark to a selected SPR click on Modify. The Modification page should be displayed. Add any remark on the Worklog field and click Apply

2.4 CHANGE LOGIN PASSWORD

1. login on the System

2. select either Submit or Query

3. select "Change your Password"

4. The VLT SPR User Schema page will appear

5. Click on Modify on the left of your account name

6. Change the contents of the Password field and Click Modify

2.5 OVERVIEW ON THE SYSTEM

Here follows a more detailed description of the system. The same info are available as on-line help The SPR System is meant to be used by internal or external users of VLT software in case an error in some code or in the documentation is found or a change to improve the behavior of an existing software seems needed.

2.5.1 Basic workflow of the system

· Problem submitted

· Assigned to vltsccm

· Notify all relevant people

· Comments added by any known user

· The SPR is discussed in the SCCB meeting and a Responsible Person is appointed for the problem

· Responsible works on problem

· Responsible can close the SPR (must add a final remark on it)

When a SPR is submitted, the vltsccm, a list of people defined by the Package and any names/addresses in the cc field will be notified with all details of the problem. After this point, any change in Status will result in all the listed people above and the Responsible being notified of the changes on all problem details.

Upon closing a Closed Status value must be set and a remark must be added on the Workflow field. If those fields are not filled, an error is generated and the problem is not closed. Once those fields are completed the problem can be successfully closed.

When a problem is submitted to the Problem Reporting Tool, it is assigned to the vltsccm. This user is the only one who can progress the Status of the report from `open' to `assigned' and therefore initiate the continuance of the workflow. After this point the Responsible user as well as the vltsccm can progress the Status of a problem.

2.5.2 Fields on Submit page

Originator This field is automatically filled by the system using the login name

Location This field specify the ESO general geographic location or the external Consortium

Package This field specify to which Package the SPR is related. If the SPR doesn't fit in any package select <unavailable>. The list of people defined on the Package name will be notified with all details of the problem.

Module Name This Field should be filled with the name of the module to which the Software problem is related. This name is the one used in the VLT Software Archive (CMM Archive)

Module Version This Field should be filled with the version of the module to which the Software problem is related. This version number is the one used in the VLT Software Archive (CMM Archive)

cc This Field should be filled with all the people not included on the Package list that need to be notified by e-mail about the SPR progress

Synopsis is a brief description to quickly identify the SPR Remember that <Synopsis> will be used later on when selecting SPRs by keyword. Choose meaningful words!

Description the complete statement of the problem (as long as you need)

2.5.3 Additional Fields on Query Page

Status The status values of the problem report:

open The SPR has been entered into the DB

assigned This is an intermediate status which automatically progresses

progress The SPR has been assigned and work is in progress.

suspended The SPR has been discussed and suspended. To be discussed again.

closed The SPR is not being worked on and no further work is envisaged.

Closed Status This field is associated with the closed state and indicates the circumstances under which the SPR was closed. The values for this field are:

deleted The problem is incorrectly submitted or duplicated.

solved Action has been taken and the problem has been solved.

clarified Problems that are user error or already fixed.

rejected The problems is acknowledged, but no work will be undertaken

Responsible Is the person assigned by the SCCB (SOFTWARE CONFIGURATION CONTROL BOARD) to work on problems. He can modify the status of the SPR after it as been assigned to him by the vltsccm. The responsible is asked to provide the evidences that the SPR can be closed. Before closing it, he must adds a remark explaining how and why the SPR is closed.

Originator The one who submitted the problems via web access

Worklog In this field any user can add a remark on the SPR. (as long as needed) Must be filled any time the status of the SPR is changed.

2.6 NOTES

Remember that the Back and Forward buttons on the Netscape menu can be used to move around on the different System pages. In particular when a submit or query action is not successful you can go back to the starting page (for modifying some fields) using the Back button.

Please report to vltsccm@eso.org any major problem you encounter using the system.

2.7 SUBMIT WITHOUT USING VLTSPR

In case a Web Browser is not available you can use a standard Problem Report/Request Form. Please use the form you get by the utility getTemplate. Any other form found in ESO documentation is out-dated and should not be used. Send the form, and any other material you think could be helpful as e-mail (preferred method), mail of fax. The corresponding addresses are:

· mail:

ESO - VLT/ELE- SOFTWARE GROUP

Attention: G. FILIPPI, F. CARBOGNANI

Karl-Schwarzschild-Str. 2

D-85748 - GARCHING b. MUENCHEN - GERMANY

· fax:

ESO - VLT/ELE- SOFTWARE GROUP

Attention: G. FILIPPI, F. CARBOGNANI

fax: + 49 89 320 2362

· e-mail:

vltsccm@eso.org

Your request will be submitted in the VLTSPR System and you will get notified by email about the changes on all problem details.

REMARK: SPR concerning software

· where a newer version is available, or

· used in HW/SW configurations that are either newer or older than those required one, or

· installed in ways different from those prescribed

will be rejected.

==============================================================================
E. S. O. ---- VERY LARGE TELESCOPE PROJECT ----
-----------------------------------------------------------------------------
SOFTWARE PROBLEM REPORT/CHANGE REQUEST FORM DATE: <dd/mm/yy>
------------------------------------------------------------------------------
From:
<consortium/company name> <contract identification
<name of the submitter with its e-mail address/fax number/phone number>
------------------------------------------------------------------------------Subject: . . <module name | document title + version number> . . . . . .
Title: . . . . <problem short description (max 40 chars)>. . . . . . .
-----------------------------------------------------------------------------
Please mark one of the following categories
_ software error
_ error in the documentation
_ change request
------------------------------------------------------------------------------
Description:

>>>>> Please delete lines marked with ">>>>>" and provide in this space:
>>>>> for software errors:
>>>>> - the description of the anomaly, including outputs,
>>>>> - how to reproduce it,
>>>>> - if existing, the temporary solution,
>>>>> - if known, the reference to where it was correctly specified
>>>>> - if known, the way to fix it.
>>>>>
>>>>> for errors in the documentation:
>>>>> - the exact location of the error (DocNr, issue, page, etc.)
>>>>> - the text that is wrong
>>>>> - if known, into what should it be changed.
>>>>>
>>>>> for change request
>>>>> - the description of what you would like to have
>>>>> - if available, possible implementation hints.
>>>>>
==============================================================================