ECALC SOFTWARE POLICIES

ECALC SOFTWARE POLICIES

FUNDING SOFTWARE:

Funding New Software:
Contingent upon the availability of funds, funding for the acquisition of new software is provided by the College of Engineering with the goal of minimizing hurdles to innovation and change.

Funding Software Renewal:
It is expected the requestor’s Department (s) will share renewal costs (50/50 or as appropriate) with the College.

INSTALLING AND TESTING SOFTWARE:

Request for eCalc Software:
Faculty and staff may request installation of software in eCALCs by contacting their departmental ecalc committee liaison. Planning is critical for successful software installation.  College management in consultation with the ecalc committee decide on software to be installed in the eCALCs. General practice is to install software during winter and summer sessions.
Testing Software:
To be eligible for eCALC installation, software must be tested in an eCALC test environment. COE-IT will notify requesters when a test installation is ready. Requesters are responsible for testing within 3 days of notification. COE-IT can not determine an installation is working properly and relies on the application specialists for this determination. When the application specialist(s) determine the software is functioning properly, the software will be deployed for production for the duration of the semester.
Post Testing Errors/Bugs:
Bugs and errors found after the testing period will be fixed as soon as possible, but with no guaranteed timeframe. Fixes that disrupt, or will likely disrupt, other existing software packages will not be considered.
Post Deadline Software Adaptations or Installations:
Generally, COE-IT will NOT modify or install eCALC software once the semester has begun. However, mitigating circumstances may require such change. College management is responsible for assessing circumstances for post deadline changes. Should the college decide to make a post deadline change, a similar installation and testing protocol will be followed, as per above. The change control procedures listed below also apply.

CHANGE CONTROL PROCEDURES

These procedures apply to in-semester change to the eCALC image. These changes may include but are not limited to: security updates, new software, software patches, etc.Criteria for Level of Severity:
College management will assign a requested in-semester change a level of severity based on discussion with requester(s), COE-IT and others as needed. The criteria used to determine severity includes:

1. Security of the classrooms and students
2. The number of students affected
3. Time period software will be in use
4. Cost
5. Availability
6. Feasibility of alternatives

Levels of Severity:

1. Normal change
2. Emergency change – Includes changes to remedy security compromises.

Back out Procedures:

1. All change must have a back out procedure should the change be deemed unsuccessful.
2. Backup images will be up to date and kept on file.
3. Software installed prior to change has priority over new/changed software.

Notification:

1. Notification will be made to eCALC classroom stake holders and college management as follows:
2. Normal change: 48 hours prior to change.
3. Emergency change: Notification of the emergency as soon as possible and when the change has been completed.