SCORMHome

Owned by devtools@ucdavis.edu
Last updated: Jan 31, 2008 by James RenfroVersion comment
2 min read

This is the home page for the Sakai SCORM Tool space. You can edit the content of this page using the Edit link on the right.

Release Planning

Meeting 1/30/2008

Overall Goals

  • Content is mix of heavily graphic material for students to read, plus text and self-feedback, quizzing
  • Ultimate goal is to do quizzing/grading
  • Mix of presentation in Scorm and Samigo quizzing is not desirable
  • Want a variety of tools to create content
  • Not very far with content, found some tools, problem with Flash and versioning

Long-term Goals

  • Be able to launch by URL - REST, EntityBroker
  • Be able to integrate with Resources, Gradebook, Assignments
  • Integrate with Portal

Two phases

  • Winter Quarter Version
    • To have had a functional SCORM player in test environment with 2-3 individuals trying to produce SCORM content to figure out what tools and what is possible, recommendations for toolse
  • Spring Quarter Version
    • April (beginning of April)
    • 100 students
    • Production?
  • Fall Quarter 2008
    • Ultimately, we're shooting for 700 person class environment
Blockers
  • Running Articulate content in Firefox on XP/Mac
  • Reporting more data
  • Performance
  • Make it run in 2.4 (nested as a link in the Production server, but running on another beta machine).
  • Handle "Table of Contents" launch – SEQ_NONE request
Reporting
  • Spreadsheet?
  • Click-through (drill down) screens?
Content
  • How do we recommend content developers set up their grading/scoring?
    • At the SCO level?
    • Using Global Objectives (not yet implemented)?
    • At the Interaction level?
      • Allow some kind of mapping of gradeable objects?
  • Need to generate some objectives with some scores that can be reported to the Gradebook.
Date of Release
  • Date: March 31st, 2008
Pilot Scope

Number of Users

Environment

Sakai Version

Level of Service

100

Beta

2.4

?

QA

Things that need testing

  • Different desktops/browsers/browser versions
  • Attempt limitations: allowing user to only access a module a certain number of times? Does it work?
Load Testing
Profiling / Performance

Roadmap

  1. Create maven 1 build for 2.4.x-HEAD - by Feb 7th
  2. Solve blockers (next 2 weeks) - by Feb 15th
  3. Profiling (JProfiler) (once blockers are solved – or before...) - by Feb 20th
  4. Create load tests for the running of the content - by Feb 24th
    • Load test for launching
    • Load test for navigation
  5. Soak test 24-hr load test
  6. February 28th – NEED A RELEASE CANDIDATE VERSION OF CONTENT FROM CONTENT DEVELOPER
  7. QA with release candidate – March 1st
    • rc1
  8. Re-package – take out extraneous jars and zips and things
  9. Fix all bugs from QA – March 15th

Documentation

Some of the project's docs are in Sakai SCORM Tool

Sakai Tool WG Charter

javadocs for the original adl source packages and new sakaiproject packages

Child Pages:

0%

remember to...