DFS Department The QA rules applicable to DFS Commissioning
	HOME INDEX SEARCH HELP NEWS

The Commissioning kick-Off : first milestone where goals to be achieved by the next delivery to the mountain are defined.

• list of main new features / functionalities / performances requirements to be developed.

• list of existing features / functionalities / performances requirements to be maintained.

• list of existing Problems Reports (existing operational bugs and change requests) to be included in the next DFS delivery.

• table describing, for each UT and each DFS component, the main new features to be installed.

Define in general terms what should be tested : expected level of tests to be run by SEG :

• general testsuites or testcases definition : preliminary draft of the main tests to be run (what is to be verified); it's not necessary at this stage to describe how they may be run.

• what should NOT be tested.

• list of new testsuites/testcases to be developed or existing ones to be adapted (for automatic tests).

• New test means (machines, operating system, softwares, databases, ...) to be provided or updated by SEG.

• New Test Data to be delivered to SEG.

Define due dates for the forthcoming milestones (Integration Kick-Off, Integration Acceptance, ...).

WHY : a formal commissioning protocol has to be defined between DFS Department and the Mountain.

HOW: Commissioning Kick-off meeting at DFS group level with:

• the DFS group Head.

• all relevant project managers.

• the Quality Assurance manager.

• the SEG testers.

Before this meeting,
each relevant project manager will prepare a small document (1 to 3 pages) describing :
A list of main new features, functionalities, performances and/or data structure requirements to be developed.
A list of existing features, functionalities, performances and/or data structure requirements to be maintained.
A summary of the main actions to be performed by the DFS project members (extracted by each project manager from his current To-Do list).

The SEG testers will prepare :
a list of the main testcases to be performed : main functions to test. This description will be extracted from an automatic test environment (if any) and/or from previous Test Plans (if any).
For each of these testcases, say if an automatic environment already exists or if it has to be developed.
A list of tests which will not to be performed and the associated justification.
The description of test means to be provided : new test data to get, specific database content to retrieve or to generate, specific machine configuration to install, new hardware or software licence to purchase, ...

The QA manager will prepare :
a list of all existing Problem Reports (bugs and change requests) which severity is "serious" or "critical". Produce a report displaying at minimum : the DFS component name, the DFS PR number, the synopsis of the PR and the current status.
A status of the current documentation associated to each DFS project: the Commissioning Kick-off meeting will also decide which document to update.

The current Commissioning Plan will be updated after this meeting (usually by the QA manager).
It is strongly recommended that each participant prepares the meeting before going to it, in order to save time.

Send comments to <khaggouc@eso.org> Last modified: Thu Nov 30 09:58:37 MET