Chapter 19
Appendices
Appendix A: RadiMation® Support Procedure
Definitions
Malfunctions are divided in eight categories and prioritized on their severity:
- Incorrect Measurement: RadiMation® is performing a measurement (and it is not crashing), but the measured or shown data is incorrect.
- Issue with Data Loss: Data has been lost due to a problem in RadiMation®.
- Crash/Issue - No Data Loss: RadiMation® has aborted during operation (for no specific reason or known issue). After a restart, no data was lost.
- Mandatory New Functionality: RadiMation® requires a functionality - that is currently not (completely) supported or implemented - to support a new standard or measurement. This includes the development of new device drivers.
- Unexpected Functionality: Other possible cases of malfunction where the RadiMation® software is doing something differently then expected.
- Cosmetic: Possible cosmetic malfunctions where RadiMation® 'in itself' is functioning correctly but the visual representation (in the form of screens, tables and or graphs) is not. For example when:
- (Parts of) labels or information are not displayed.
- (Parts of) labels or information are overwritten by other labels or other information.
- The screen 'flashes' while writing graphs or other information.
- The manual contains an error or unclear description.
- Questions: An issue is not caused by a malfunction of RadiMation®, but by the user's knowledge of RadiMation®. A situation where the customer does not understand (part of) the functioning of RadiMation® can be solved by informing the customer about the proper use of the software.
- Wish: There is no software malfunction or knowlegde issue. However the customer wishes (or even requires) RadiMation® to function in a different way, or contain additional functionalities, to support their use of the software. This can even mean the situation is unworkable for the customer, for example in situations where a certain functionality or part of a test is not supported.
Bug Reporting Procedure
The goal of the 'Bug Reporting Procedure' is to support customers as quick and effective as possible.
If you experience an issue with your RadiMation® test software, or you simply have a request or question, please fill in the RadiMation Issue Report on the DARE!! website.
Your issue will be addressed as soon as possible.
Appendix B: Maintenance
The service of solving 'bugs' in the software is covered by the maintenance contract. Depending on the situation it might be necessary for an engineer from DARE!! Instruments to supply on-site support. These costs are covered as well, excluding travel and lodging. The service contract entitles the customer to all new push releases for the respective module(s).
Functionality improvements and/or changes to the respective software module(s) that are desired by the customer (and are assessed by DARE!! as functional and commonly applicable), will be implemented in a future release of the software. It is important to keep in mind that improvements and/or changes for one customer shoud not lead to disadvantages for other customers.
The RadiMation® Support/Upgrade contract is mandatory and should be ordered with each RadiMation® order.
- The minimum duration of this contract is 2 years.
- The first year is free of charge, each subsequent year costs 10% of the software order value.
- the starting date of the support/upgrade contract is the original delivery and/or installation date.
- If a customer does not accept a support/upgrade contact, DARE!! Instruments will not provide any software support/upgrade service.
Releases
Releases are divided in major and minor releases, indicated by a release number in the xx.yy.zz format. In this format, xx stands for the major release version and yy.zz for the minor release version.
Releases are shipped to the Reseller who is responsible for shipment and installation support at the customer.
Major release
A major release consists of any and all new functionalities and bug fixes since the previous minor release. As such the major release is a base line release.
As a rule Major releases are push releases and are automatically send to all customers with a support contract.
Minor release
A minor release consists of a specific new functionality or bug fix(es). Where yy is the new functionality and zz the bugfix(es).
As a rule Minor releases are pull releases and are send to the customer(s) with a support contract that needs or request the release.
Release Planning
There will be four main releases each year; two major/push releases and two minor/pull releases. Bug fix releases for specific customers are done in between.
The planning is as followed:
- 1st minor: The first Thursday after February 15h
- 1st major: The first Thursday after May 15th
- 2nd minor: The first Thursday after Augustus 15th
- 2nd major: The first Thursday after November 15th