Release Notes/Installation: Difference between revisions

From RadiWiki
Jump to navigation Jump to search
Line 32: Line 32:


== Verification ==
== Verification ==
Each newly build {{RadiMation}} version is tested extensively before it is released. We have validated this version on three levels of the four levels that should be done. The fourth level of the validation should be done by the end-user itself.
 
Every new {{RadiMation}} version is tested extensively before it is released. DARE!! validates these new versions on three ‘levels’. The fourth level of the validation is to be done by the end-user.
 
This quality management system follows the ISO/IEC 17025 standard (“General requirements for the competence of testing and calibration laboratories”).


=== Automatic knob pushing program ===
=== Automatic knob pushing program ===
This program simulates a normal end-user to {{RadiMation}} and it is run on each {{RadiMation}} version. During its simulation it is entering all kind of information in all windows; it is executing tests, reviewing the test results and generating reports. All actions that can be done by a real person are simulated by this program
This validation is a responsibility of [[DARE!! Instruments]].
=== Validation and usage in test house ===
After the first validation has passed, the {{RadiMation}} version is validated by [[DARE!! Measurements]]. This validation includes real world measurements of a 'known' EUT, and verification of the measurement results, with manual measurements.
If this validation is passed, the validated {{RadiMation}} version will be installed and used by [[DARE!! Measurements]].
In this period any reported problem will be investigated and possible an updated version of {{RadiMation}} will be created
This validation is a responsibility of [[DARE!! Instruments]].
=== Validation at selected end-user(s) ===
After the validated version is used for more than 2 weeks at [[DARE!! Measurements]], the version is send to selected end-user(s) that will also test this version of {{RadiMation}}.
After a certain amount of time, the validated version is shipped to all other end-users.
This validation is a responsibility of [[DARE!! Instruments]].


=== End-user validation ===
The ‘automatic knob pushing program’ simulates an end-user and is run on each {{RadiMation}} version. The program performs all the actions that a user could do, such as entering information, executing tests, reviewing test results and generating reports.
When an end-user receives a new {{RadiMation}} version, it should perform a validation of the software. Parts that should be validated by the end-user itself are:
 
Performing the first validation level is a responsibility of [[DARE!! Instruments]].
 
=== Validation and usage in a test lab ===
 
Ones the new {{RadiMation}} version has passed the first validation level, it progresses to the second validation level performed by [[DARE!! Instruments]].
 
This validation level consists of two stages. In the first stage the software is used to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software.
 
If the new software version passes the first stage, it progresses to the second stage where it is installed and used in the [[DARE!! Instruments]] test laboratory. Any issues that are reported during use are investigated. An updated version of {{RadiMation}} is created if needed.
 
Performing the second validation level is a responsibility of [[DARE!! Instruments]].
 
=== Validation and usage in a test house ===
 
Ones the new {{RadiMation}} version has passed the second validation level, it progresses to the third validation level performed by [[DARE!! Measurements]].
 
This validation level consists of two stages. In the first stage the software is used to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software.
 
If the new software version passes the first stage, it progresses to the second stage where it is installed and used by [[DARE!! Measurements]]. Any issues that are reported during use are investigated. An updated version of {{RadiMation}} is created if needed.
 
Performing the third validation level is a responsibility of [[DARE!! Instruments]].
 
=== Validation by end-users ===
 
Ones the new {{RadiMation}} version has passed the third validation level, it progresses to the fourth (and last) validation level performed by the end-users.
 
When end-users receives a new {{RadiMation}} version they should perform a validation of the software. The parts that should be validated by the end-user are:  
* Correct control of the used equipment
* Correct control of the used equipment
* Validation of the software according to internal quality standards
* Validation of the software according to internal quality standards
* Possible verification and comparison of measurement of a 'known' EUT.
* Possible verification and comparison of measurements on a 'known' EUT
This validation is a responsibility of the {{RadiMation}} end-user itself.
 
Performing the fourth validation level is a responsibility of the end-user.

Revision as of 13:55, 2 November 2015

Installation[edit]

Backup[edit]

Before you install the latest version of RadiMation®, please make sure to saveguard all your critical data.

Make a back up of (at least) the following files:

  • Correction files
  • TSF files
  • Sequence files
  • Device driver configuration files

Multi version installation[edit]

Since the release of RadiMation® version 4.3.67 it has become possible to run different RadiMation® versions (4.3.67 and higher) on the same PC.

This functionality can be used to verify the correct functioning of the software before it is used for EMC testing. Simply put, the functioning of the new version can be checked by comparing it with the older version. This verification can for example be required by internal quality assurance standards. During this verification process, the installation of the older RadiMation® version can still be used for all EMC tests.


Be advised that:

  • It is not possible to run two (or more) different versions at the same time without risking a software crash. Close RadiMation® before starting another version!
  • DARE!! Instruments cannot be held accountable if information is lost because two different versions of RadiMation® are used at the same time.
  • The user needs to have the rights as described in User rights and installation.

Installation[edit]

RadiMation® can be installed by starting the ‘SETUP.EXE’ program that is located on the delivered CD. By using the default settings of the setup program it should be very easy to install RadiMation®. The setup program will install the RadiMation® software in a separate installation folder which allows you to also start any previous RadiMation® versions.

After the RadiMation® version is installed, we strongly advise that the latest device drivers will also be installed. These device drivers can be installed by start the ‘DRIVERS.EXE’ program that is located on the delivered CD. The ‘DRIVERS.EXE’ program will detect the different installed RadiMation® versions, and it will present you with a dialog, in which you can select the RadiMation® version of which the device drivers should be updated. In this dialog select the correct latest version of RadiMation® that was just installed.

When both the ‘SETUP.EXE’ program and the ‘DRIVERS.EXE’ program are used to install the software, you have the latest released version of RadiMation®.

Verification[edit]

Every new RadiMation® version is tested extensively before it is released. DARE!! validates these new versions on three ‘levels’. The fourth level of the validation is to be done by the end-user.

This quality management system follows the ISO/IEC 17025 standard (“General requirements for the competence of testing and calibration laboratories”).

Automatic knob pushing program[edit]

The ‘automatic knob pushing program’ simulates an end-user and is run on each RadiMation® version. The program performs all the actions that a user could do, such as entering information, executing tests, reviewing test results and generating reports.

Performing the first validation level is a responsibility of DARE!! Instruments.

Validation and usage in a test lab[edit]

Ones the new RadiMation® version has passed the first validation level, it progresses to the second validation level performed by DARE!! Instruments.

This validation level consists of two stages. In the first stage the software is used to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software.

If the new software version passes the first stage, it progresses to the second stage where it is installed and used in the DARE!! Instruments test laboratory. Any issues that are reported during use are investigated. An updated version of RadiMation® is created if needed.

Performing the second validation level is a responsibility of DARE!! Instruments.

Validation and usage in a test house[edit]

Ones the new RadiMation® version has passed the second validation level, it progresses to the third validation level performed by DARE!! Measurements.

This validation level consists of two stages. In the first stage the software is used to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software.

If the new software version passes the first stage, it progresses to the second stage where it is installed and used by DARE!! Measurements. Any issues that are reported during use are investigated. An updated version of RadiMation® is created if needed.

Performing the third validation level is a responsibility of DARE!! Instruments.

Validation by end-users[edit]

Ones the new RadiMation® version has passed the third validation level, it progresses to the fourth (and last) validation level performed by the end-users.

When end-users receives a new RadiMation® version they should perform a validation of the software. The parts that should be validated by the end-user are:

  • Correct control of the used equipment
  • Validation of the software according to internal quality standards
  • Possible verification and comparison of measurements on a 'known' EUT

Performing the fourth validation level is a responsibility of the end-user.