Software+Evaluation+Criteria

The technical services department reserves the right to evaluate each software request based on criteria such as the following (this list is given as an example and may be adjusted accordingly):
 * Evaluation Criteria for Software Purchases**

1) Educational value – Does the software have any built in assessment module? Is there a resource on the internet or elsewhere that is of the same or higher caliber? Was the resource evaluated and recommended by more than one individual? Will the resource be used by more than one individual? (Exceptions to this rule: Software required by a student’s IEP, assistive technology needs, specialized software) 2) Technical Specifications – Will this software run on district owned resources? If it is networked, does it work with Novell? What are the minimum requirements? 3) Frequency of Use (will this software be used once a year, or all the time) 4) Number of requested licenses – Is the software just for one teacher? 5) District Commitments – Does the software provide methods of collaboration between students and with the world-wide learning community? Is the software applicable to today’s world? Does the software provide opportunities for experiential learning?