Software Updates
Contents
Requests for software updates are submitted to the developer via the Tracker website: http://tracker.meta.com.au
User names and passwords have been supplied to all users wishing to partake in enhancement submissions and bug reports.
The developer will determine the level of testing required for approved updates. Testing falls into 3 categories:
| 1. | Low |
| 2. | Normal (Citrix), and |
| 3. | High (Citrix and Test DB) |
These levels are listed in order of severity of testing.
For the purposes of the following descriptions, Core software operation includes the following functions:
| • | New Job creation |
| • | Job allocation |
| • | Job invoice creation and data entry |
| • | Invoice batching, checking and export/upload functions for SAP transfer |
Low: Low level testing is applied to updates and modifications which clearly do not impinge on the core software operation and/or maybe cosmetic in nature. Help file updates, and reporting module updates also fall into this category. These updates may be deployed to all desktops via the SOE/NAL system without user level testing. i.e. developer testing only is required.
Normal (Citrix): Normal level testing is applied to non-core operations but may effect transaction management. It may have an impact on the efficacy of data saving functions or email of faxing functions. These updates will be initially deployed to the Citrix environment and tested by at least one operations user against the live database before deployment via SOE.
High (Citrix and TestDB): High level testing is applied to operational changes to the way jobs are created, allocation and processed as per core operations above. Tasks in this category will require proof of correct operation against a test database before acceptance testing is passed. These updates will be initially deployed to the Citrix environment and tested by at least one operations user agasint the test database before deployment via SOE.
The tracker system requires these levels to be set during task creation. The developer may increase of or decrease the testing level assignment for a task.
The overall testing level for any group of tasks being deployed in one update (build) will be the highest level assigned to any of the tasks contained in that update.