Mec2005 Istt

646 views

Published on

Published in: Entertainment & Humor
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
646
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Mec2005 Istt

  1. 1. Developing a Web Registration and Course Management System for Staff Development Information Systems Technology Training (ISTT) Northern Arizona University Microcomputers in Education Conference March 15, 2005
  2. 2. ISTT Mission <ul><li>The Information Systems Technology Training Team (ISTT*) was organized to facilitate formal technology training opportunities for staff and faculty in classroom and online environments. </li></ul><ul><li>* Part of NAU Information Technology Services </li></ul>
  3. 3. ISTT Areas of Training <ul><li>Web Development Tools & Technology (Dreamweaver, Flash, HTML, CSS, SQL, FrontPage, etc.) </li></ul><ul><li>PeopleSoft </li></ul><ul><li>MS Office, Publisher </li></ul><ul><li>Other ITS Supported Applications </li></ul>
  4. 4. ISTT Team Members <ul><li>Steve Sorden – Team Lead M.Ed. Ed Tech, Ed Leadership </li></ul><ul><li>Dave Berz – Senior Trainer M.Ed. Educational Technology (in progress) </li></ul><ul><li>Rub én Vásquez – Online Developer M.Ed. Educational Technology </li></ul><ul><li>Chris Montague – Trainer M.Ed. Educational Technology (in progress) </li></ul><ul><li>Stephen Montague – Trainer </li></ul>
  5. 5. Overview of Presentation <ul><li>RegisCM Course Management System </li></ul><ul><li>Rationale for developing our own system. </li></ul><ul><li>Team process for developing RegisCM. </li></ul><ul><li>Tools and technology used in development. </li></ul><ul><li>Demonstration of RegisCM features. </li></ul><ul><li>Roadmap for future development. </li></ul>
  6. 6. RegisCM
  7. 7. RegisCM Features <ul><li>Provides a single entry point to ISTT </li></ul><ul><li>Organizes and manages training schedule </li></ul><ul><li>Offers a user-friendly way for staff & faculty to register & withdraw from classes </li></ul><ul><li>Displays training by subject, so clients see all training, not just lab classes </li></ul><ul><li>Tracks attendance & course evaluations </li></ul><ul><li>Reporting tool </li></ul>
  8. 8. ISTT Needed a New System <ul><li>Old system was five years old and looked dated </li></ul><ul><li>It was limited in features </li></ul><ul><li>It was written for a platform that we had moved away from (Cold Fusion & Access) </li></ul><ul><li>It was becoming increasingly hard to maintain the old system </li></ul>
  9. 9. Commercial Systems <ul><li>Expensive ($10,000 and up) </li></ul><ul><li>Restrictive licensing clauses </li></ul><ul><li>Took control away from us and placed it in the hands of distant vendors </li></ul><ul><li>Still didn’t do what we needed </li></ul>
  10. 10. PeopleSoft <ul><li>NAU uses PeopleSoft as our ERP system </li></ul><ul><li>PeopleSoft training module did more or less what we needed, with modifications, but we couldn’t get the modifications </li></ul>
  11. 11. Open Source Systems <ul><li>We spent a lot of time looking at open source systems </li></ul><ul><li>We even considered modifying Moodle LMS at one point </li></ul><ul><li>After an exhaustive search, we couldn’t find anything that came close to what we needed </li></ul>
  12. 12. Decision <ul><li>Reluctantly, we decided that developing our own system the only viable option. </li></ul><ul><li>The problem was that the team had limited programming skills. We were instructional designers, not programmers. </li></ul>
  13. 13. Brainstorming <ul><li>We began the project in August of 2004. </li></ul><ul><li>We started by meeting to brainstorm what features we wanted to maintain from the old system, as well as new features needed. </li></ul><ul><li>We created an extensive wish list. </li></ul><ul><li>We developed story boards for different views and passed them around for team discussion & suggestions. </li></ul>
  14. 14. Planning Phase <ul><li>We created a checklist of the most practical features for initial development </li></ul><ul><li>Main areas were divided up between team members to develop: </li></ul><ul><ul><li>Client </li></ul></ul><ul><ul><li>Admin </li></ul></ul><ul><ul><li>Instructor </li></ul></ul><ul><li>Team had limited experience. We purchased lots of books and used Web resources extensively. </li></ul><ul><li>On-the-job training for all </li></ul>
  15. 15. Planning Board
  16. 16. Development Timeline <ul><li>Project started August of 2004. </li></ul><ul><li>Development proceeded as time permitted. </li></ul><ul><li>We asked for and received permission to eventually release RegisCM as open source. </li></ul><ul><li>Conducted usability testing with clients. </li></ul><ul><li>RegisCM successfully went live at NAU in December of 2004. </li></ul>
  17. 17. Tools & Technologies <ul><li>Used Moodle as a loose guide for how to structure Regis </li></ul><ul><li>All settings are contained in two files </li></ul><ul><ul><li>Database connections </li></ul></ul><ul><ul><li>LDAP information </li></ul></ul><ul><ul><li>Email addresses and messages </li></ul></ul><ul><ul><li>Colors used in application </li></ul></ul><ul><ul><li>CSS & Themes </li></ul></ul><ul><ul><li>Long and short names </li></ul></ul>
  18. 18. Tools & Technologies <ul><li>Dreamweaver MX 2004 </li></ul><ul><li>PHP </li></ul><ul><li>MySQL Database </li></ul><ul><li>PremiumSoft Navicat MySQL Client </li></ul><ul><li>Concurrent Versions System (CVS) http://www.cvshome.org http://cvsdude.com </li></ul><ul><li>Tortoise CVS </li></ul><ul><li>Cascading Stylesheets (CSS) </li></ul><ul><li>Macromedia Captivate for Tutorials </li></ul><ul><li>DotProject Project Management System </li></ul>
  19. 19. CVS <ul><li>Allows developers to work on code from different places at different times. </li></ul><ul><li>Mediates conflicts when two developers have changed the same code. </li></ul>
  20. 20. Environment
  21. 21. Regis Demo <ul><li>Client View </li></ul><ul><li>Instructor View </li></ul><ul><li>Administrative View </li></ul><ul><li>Evaluations </li></ul>
  22. 22. RegisCM Demo
  23. 23. Evaluations Team Lead receives an email of each evaluation.
  24. 24. The Future? <ul><li>Tutorials in WebCT and SCORM </li></ul><ul><li>Add reporting capabilities </li></ul><ul><li>Complete Instructor/Admin Capabilities </li></ul><ul><li>Backup MySQL Database </li></ul><ul><li>Automate Functions (Using cron jobs?) </li></ul>
  25. 25. Developing a Web Registration and Course Management System for Staff Development http://jan.ucc.nau.edu/~sds3/mec2005

×