h2 Criteria for Systems Team

This list is based on the criteria in {link:Systems Team.doc|worksite:/Systems Team.doc}. I've added the ~~Notes~~ field to explain reasons for modifying these criteria. --Strike through-- text shows the original criteria, and ~~italic~~ text shows the proposed modifications.

{table}
System Considerations|Definition|Weight|~~Notes~~
System stability|Minimal unexpected downtime. Ability to manage peak loads without interruption of service or sluggish behavior.|3|Very vague; how is this measurable?
System reliability|Tools function as designed and are not subject to errors. ~~Change this to  how quickly vendor responds to bugs and security problems~~|3|All software has bugs: we should know the bug-fixing and tracking processes of each system, as well as gather stats on vendor response time.
Security features|Password protection, SSL encryption.|--2-- 1|All systems offer this; any system that does not should not be evaluated; remove from criteria, but note this in final report?
Scalability|System can grow as needed to accommodate projected growth in number of users.|--2-- 1|Again, any system we eval must be scalable
--OS independence-- ~~Platform integration w/ current OS?~~|--Application can run on multiple platforms including Windows, Unix, and Linux.-- ~~Application can run on existing DLS OS?~~|--1-- 3|Application needs to integrate with existing DLS and CITC systems; an entirely new OS platform would take an overwhelming amount of resources (human, financial) to implement, so we need a system that integrates with our current platform.
Hardware --independence-- ~~integration?~~|--Application can run on multiple brands of hardware.-- ~~Run on current DLS hardware?~~|--2-- ~~3~~|See above.
Ability to integrate with SIS (PeopleSoft/EIS)|The learning management system would be able to communicate directly with UNTŐs student information system. A direct connection makes it easier to populate courses and makes it possible to post grade data from a course to the student information system.|1|
Easy-to-use enrollment management tools|Network administrators and support team can run student uploads using automated processes and data from the EIS system/Registrar.|2|
Easy to create and restore backups|Backup files can be created easily and run quickly by automated scripts. Files can be restored as courses within a few hours.|2|
Ability to migrate courses to/from another learning management system|Some learning managements provide a migration utility that enables an institution to copy the existing courses to the new system. If there were no migration utility, instructors would likely need to rebuild courses in the new system.|2|Vista migrations are difficult; look into IMS migration abilities.
{table}