1. © 2004 Running a Unit of Learning in CopperCore Colin Tattersall, The Open University of the Netherlands

2. © 2004 Alfanet (IST-2001-33288) ­Active Learning for Adaptive Internet (5 th Framework) ­Adaptation is about creating a user experience that purposely adjusts to various conditions (personal characteristics, pedagogical knowledge, the learner interactions, the outcome of the actual learning processes) over a period of time with the intention to increase pre-defined success criteria (score, time, economical costs, user satisfaction) ­Adaptation in aLFanet operates on a combination of: ­ knowledge of the user LIP ­ knowledge of the contents MD ­ an explicit design LD ­ formal progress QTI ­ actual user interactions

3. © 2004 ALFANET General Architecture (I)

4. © 2004 Windows Forms and User Interface.Net Components.Net Framework.Net Logic Components External.Net Components User Modelling Prespecification Learning Resource Editing Unit of Learning Editor Groove XML Forms Environment Learning Design XML Editor & Schema/DTD Validator Groove Collaboration Environment Authoring Tool ­Enables authors to create courses and/or Units of Learning that conform to the ALFANET LMS ­Gives learning designers the ability to create pedagogical- instructional models

5. © 2004

6. Example template Inductive presentation (template guidelines) · Inductive presentation requires presenting first a number of possible examples and then giving a definition of the concept. · - The examples should be as diverse as possible to allow learner to generalize. They should represent the full range of cases that the learner will encounter after the instruction. · - Begin with easy examples so learners can master the activity and build confidence. - End with ………………………..

7. © 2004 ALFANET General Architecture (I)

8. © 2004 What is CopperCore? ­Open source IMS Learning Design engine capable of processing units of learning. ­Hides complexity of IMS LD for developers wishing to incorporate IMS LD into their products. ­Does not provide any user interface. Not a stand alone product. ­Uses XML for data exchange with clients ­XML format resembles IMS LD as closely as possible ­Uses properties as main data storage mechanism

9. © 2004 CopperCore positioning LD PlayerRun toolRepository Unit of Learning Run Authoring Learner & Staff Administration Unit of Learning Learner & staff details Design timeRun time Portal Learning services CopperCore

10. © 2004 CopperCore APIs ­CopperCore provides three API’s ­CourseManager: provides administrative functions ­users, runs, roles, publications ­LDEngine: provides run-time behavior ­activity trees, environment trees, content, completions ­Timer: triggers timed events ­various timed completions ­CopperCore provides one library ­Validation: provides validation routine for an LD manifest ­IMS LD manifest files

11. © 2004 CopperCore 3 APIs CopperCore Integration

12. © 2004 CopperCore Environment ­Developed in Java using JBuilder9, can be deployed on any J2EE application server ­Tested: Borland Enterprise Server 5.2.1 and JBoss 3.2.1 ­Can use any relational database ­Tested with PostgreSQL 7.3 and MS SQL Server 2000 ­Runs on Linux and MS-Windows ­Tested with Windows XP/2000 and SuSe Linux (kernel 2.4.20) ­CopperCore version 1.0 available via SourceForge (http://sourceforge.net/projects/coppercore) ­Today: level B. Upgrading to level C