TELS Logo Banner Banner

OTrunkification effort

This page will be used to record the steps required to bring OTrunk data persistent model into SAIL.

Planning

Iteration 1

Goals

  • Get the existing authoring tool working. Current Authoring Tool Efforts
  • Unify the user data format used by TELS, with rest of projects at concord TEEMSS, CAPA, UDL, and ITSI

Tasks

  • Handling of possible scores in teacher grading tool.
    • new resource stored in the portal
    • the vle needs to loading that new resource
    • teacher grading tool needs to edit that resource
  • Figure out new learner data format (Scott) - Finished Jan. 1
    • Status report SAIL meeting November 30, 2007
    • Start discussion SAIL meeting December 7, 2007
    • OTrunk could supply a Rim (install service to supply rim to step types)
    • Change steptype code to abstract learner data and be able to work with either Rim or OTrunk
    • Change step entirely so it wouldn't work with old stuff- Rip out Rim code, write to Otrunk Object instead of a rim

Add initial support for all pas step types (Tony & Scott & Geoff)

  • VLE
  • Authoring Tool
    • Loading in OTml File and create the project structure
    • Add, Move and Remove Steps in the project and have those changes persist
    • Update loading and saving code of authoring tool (Tony) - start work around Dec. 7 at earliest
      • There might some work in sail-core or sail-otrunk to support this better.
        • requires time with scott should it is best to hold off until "initial learner data format work" is complete.
  • Other
    • Update the converter to write out OTrunk Curnits (Geoff) Otrunk Converter status
    • Add learner data saving for all pas step types (Tony) Otrunk Saving status
      • depends on "new learner data format".
    • Update sds reporting code (Aaron)
      • depends on "add learner data saving..."
    • Update curnitmap to work with OTrunk curnit (Hiroki?)
      • depends on "add initial support for all pas step types"
    • Update teacher grading tool to work with the otrunk learner data format (Hiroki/Tony)
      • depends on "add learner data saving..."
    • Update handling of possible scores in teacher grading tool. (Hiroki/Tony)
      • depends on "update curnitmap..."

Iteration 2

Goals

  • Unify the authoring and running application framework used by TELS and UDL.

Tasks

  • Refactor/Port the VLE and Pas Steps so they work with the OTrunk view system (??)
  • Refactor/Port the Authoring tool so it works with the OTrunk view system (??)

At our current pace I think Iteration 1 might take until the end of
February. Infusing a new programmer might speed this
up. The key is to identify medium sized tasks that don't require
knowledge of the whole system. And at the same
time don't spend effort on stuff in Iteration 1 which we are going to
redo in Iteration 2.

I came up with these 2 iterations, because stuff always takes longer
than you think. And if we tried to do it all in one
iteration it would be many months before we finished. So instead we get
something sooner that isn't perfect and will
need to be redone, but it should be usable. However this means that
major revisions and changes to the authoring tool
should be held off (if possible) until Iteration 2.

Resources

SVN URL: https://svn.concord.org/svn/projects
all of the projects are under /trunk/common/java

Root of OTrunk documentation: http://confluence.concord.org/display/CSP/OTrunk
OTrunk examples: http://confluence.concord.org/display/CSP/OTrunk+Examples

Programmer resources breakdown for this effort

Aaron 50%
Scott 15%
Stephen 10%

Hiroki 50%
Anthony 80%
New programmer 80%

Labels

 
(None)