Sakai 3 at CSU

885 views

Published on

Sakai 3 at CSU


Matt Morton-Allen,
Charles Sturt University

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
885
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Sakai 3 at CSU

  1. 1. Sakai 3 at CSU Matt Morton-Allen - L&T Liaison Enterprise Architecture and Liaison Division of Information Technology
  2. 2. Agenda <ul><li>Historical overview </li></ul><ul><li>Sakai 3 and CSU Interact </li></ul><ul><ul><li>Why? </li></ul></ul><ul><ul><li>What? </li></ul></ul><ul><ul><li>How? </li></ul></ul>
  3. 3. 1. Historical Overview
  4. 4. CSU Interact Timeline
  5. 5. CSU Interact Vision <ul><li>Consistent and integrated </li></ul><ul><li>Scalable </li></ul><ul><li>Flexible </li></ul><ul><li>Reliable </li></ul><ul><li>Agile </li></ul>
  6. 6. Release Timelines
  7. 7. Discussions <ul><li>Nov 2008 - AuSakai @ Monash </li></ul><ul><li>Dec 2008 - Internal discussions with Sponsor et al </li></ul><ul><li>Mar 2009 - OLE Steering Committee approved initiative </li></ul><ul><li>Apr 2009 - ILSCOSC endorsed initiative </li></ul><ul><li>May 2009 - ILSC endorsed initiative </li></ul><ul><li>May 2009 - Sakai 3 IHP proposal lodged </li></ul><ul><li>Jul 2009 - T&S closed off </li></ul><ul><li>Jul 2009 - Boston Sakai conference </li></ul><ul><li>Aug 2009 - Sakai 3 Impact Assessment completed </li></ul><ul><li>Sep 2009 - SEC approval of initiative and funding </li></ul>
  8. 8. 2. Sakai 3 and Interact Why?
  9. 9. Why? <ul><li>Ease of use </li></ul><ul><li>Improved scalability </li></ul><ul><li>Reduced development costs </li></ul><ul><li>Architectural alignment </li></ul><ul><li>Interoperability </li></ul><ul><li>Vast improvement in user functionality! </li></ul>
  10. 10. 2. Sakai 3 and CSU Interact What?
  11. 13. Previously Identified Needs <ul><li>Course sites </li></ul><ul><li>Subject Entry Point </li></ul><ul><li>Contact Tool </li></ul><ul><li>Sub-sites </li></ul><ul><li>Restricted joinable sites </li></ul><ul><li>Full site merging </li></ul>
  12. 14. New Opportunities <ul><li>Sakai based tools for: </li></ul><ul><ul><li>online assignment submission (i.e. EASTS) </li></ul></ul><ul><ul><li>Gradebook? </li></ul></ul><ul><ul><li>Forums software? </li></ul></ul><ul><li>Seamless DOMS integration? </li></ul><ul><li>Public facing pages? </li></ul><ul><li>Integration with Web 2.0 services? </li></ul><ul><li>Improved collaboration with external people? </li></ul>
  13. 15. 2. Sakai 3 and CSU Interact How?
  14. 16. How? <ul><li>Multi-pronged approach: </li></ul><ul><ul><li>Sakai 3 “Preparatory Work” </li></ul></ul><ul><ul><li>Sakai 3 “Implementation project” </li></ul></ul>
  15. 17. Sakai 3 – Preparatory Work <ul><li>Paul Bristow – CSU Applications Architect </li></ul><ul><ul><li>2 days week </li></ul></ul><ul><ul><li>Focus on CSU specific technologies: </li></ul></ul><ul><ul><ul><li>Integration with CSU middleware </li></ul></ul></ul><ul><ul><ul><li>Linkages to CSU authentication </li></ul></ul></ul><ul><li>Ian Boston – CARET CTO </li></ul><ul><ul><li>1 day / week </li></ul></ul><ul><ul><li>Integration of CSU needs in “kernel”: </li></ul></ul><ul><ul><ul><li>CSU grouping </li></ul></ul></ul><ul><ul><ul><li>Site provisioning </li></ul></ul></ul>
  16. 18. Sakai 3 – Implementation <ul><li>Two phase project: </li></ul><ul><ul><li>Conceptual phase </li></ul></ul><ul><ul><ul><li>Philip Uys and Matt Morton-Allen </li></ul></ul></ul><ul><ul><ul><li>Stakeholder reference group </li></ul></ul></ul><ul><ul><ul><li>Scoping and analysis </li></ul></ul></ul><ul><ul><ul><li>August 2009 – December 2009 </li></ul></ul></ul><ul><ul><li>Implementation phase </li></ul></ul><ul><ul><ul><li>Full project team </li></ul></ul></ul><ul><ul><ul><li>Design and implementation </li></ul></ul></ul><ul><ul><ul><li>Early 2010 - 2011? </li></ul></ul></ul>
  17. 19. Questions?

×