Skip to Content
Use COVID-19 Alert Level 2 contact tracing form when on campus.
Towards the end of each year an email is sent to department representatives asking them to submit the bulk of the requests for the software required for teaching and learning in the following year. These representatives in turn contact the academics within their department to facilitate the negotiation of various versions of the software required. Each software request can be submitted by the academics or their department representatives by filling out the appropriate software request form:
Additional software requests are processed throughout the year, however there is usually an influx of software requests ahead of the start of each semester and ITS cannot always guarantee the software will be ready by the start of the semester, which is why users need to to submit the bulk of their requests well in advance.
Once the software and licence keys are received by the ITS Software Build Team, each software request typically takes up to three weeks to process and deploy. This includes testing to mitigate any potential issues associated with the rollout of the additional software i.e. software already deployed is not retrospectively tested (by the academics that made the original request) alongside the additional software being requested. This means there is always a chance that the additional software installed could break one of the original software packages already deployed. Asking all academics to re-test all the software each time additional software is deployed is very disruptive; instead the "Software image development process" outlined below is followed.
Want to know more about the software image development process? — take a look inside.
Academics, or their delegates, submit their software requirements using the software request system above.
Note: While requests for new or upgraded versions may be financially pre-approved by departments, with the inclusion of a ledger code on the form, these still need to be assessed by ITS on financial and other grounds before the request is accepted.
If new or updated versions of the software are being requested for purchase, the Service Desk will assess the requirements to ensure that the appropriate licencing model has been selected and that the department agrees to pay for it. The Service Desk may seek advice from the following sections if required:
The ITS Service Desk will also ensure that all required information has been supplied in the software request, and will then ask the ITS Software Build Team to coordinate the acceptance of the request by:
If the request is approved, the Service Desk will work with the ITS Licence Administrator to organise purchase of the licence (if required). This will then be supplied to the ITS Software Build Team.
The ITS Software Build Team will commence the work, building, peer reviewing and internally testing the changes:
When the software development cycle is complete, a member of the ITS Software Build Team will contact the appropriate academic or their delegate to arrange User Acceptance Testing (UAT):
Requested software does not automatically roll over from one year to the next as:
Page authorised by CIO
Last updated on Wednesday 20 November 2019
Phone 06-356-9099 ext. 82111 (preferred method)
7:45am - 5pm, Monday to Friday
(excluding Public and University holidays)
AskUs Self-Service to log a request online (staff)
IT Services Dashboard (staff)