The Past

Folllowing a process of requirements analysis, design, development, testing, and piloting, the iClass consortium released the first version of the iClass system in March 2006. This work progressed on par with the findings of the Applied Research work package, hence yielding not only a performing state-of-the-art system, but also one which comprises many novelties. However, most of the technical "personalised learning" work in iClass had focused on Automated Customisation (AC). Pilots run at three schools from Turkey , France , and Belgium that lasted a month each provided valuable insight to the necessity for a more user-centric approach which was also surfaced during the project review in April 2006.

As a result the project underwent a substantial revision in its educational approach and organisation. Self Regulated Learning is adopted as another facet of personalised learning that facilitates increased levels of learner empowerment. This does not mean that automated customization is absent. To the contrary, iClass looks at the most meaningful complementarities and interdependencies between both processes.

For more on this please refer to iClass Education Vision Update.

The Present

As of June 2007, the pedagogical model is established, revised system features and functions are decided and linked to the technical components already available to determine what is yet to be done. The development work has started to create a Rich Internet Application that will blend a Web 2.0 paradigm with the use of XML Web services and P2P file/component sharing.

The process model for this development is adopted from Microsoft Solutions Framework. This advanced model is a combination of Waterfall Model and Spiral Model, where critical milestones are placed on a spiralling work process. In this way, the predictability of the Waterfall Model is blended with the continuous improvement foreseen by the Spiral Model.

As for the development methodology, Feature Driven Development adopted from Microsoft Solutions Framework will be used. This methodology consists of two episodes: planning and iterative building of features.

Feature Driven Development Methodology of MSF

The Future

According to the current work plan the milestones are as follows:

Milestone 1: Completion of Mock-up and Validation. The development of the Mock-up will be completed by the end of April 2007 and the associated validation will be completed a month later. This process involves overlap as users are engaged in the finalisation of the Mock-up. The Mock-up will constitute indicative user interfaces and “dummied” functionality to assess the acceptance and usability of the proposed iClass system.

Milestone 2: Pedagogical Model. This two phase milestone will witness the interim and final versions of the iClass Pedagogical Model. The interim version (end June 2007) will be completed following Milestone 1, taking suitable influence from it. The model will evolve as the iClass system does and will use evidence from piloting before the final version is completed for the end of April 2008.

Milestone 3: iClass System (Version 2). This version of the iClass system, which is due by the end of October 2007, will perform a set of necessary features with essential functions to provide a platform for piloting.

Milestone 4: iClass System (Version 3). This version of the iClass system is derived from continuous improvement and evolution of Version 2. Indeed, Version 3 may be seen as the final release of several stable releases after Version 2. This evolution process is heavily influenced by the evolving Pedagogical Model and from the results solicited from validation and piloting. The final release is due June 2008.

Milestone 5: Piloting, Evaluation and Exploitation. This milestone is also divided into two phases. The interim evaluation information will be based on the Mock-up and will provide significant evidence and influence in the development of both the Pedagogical Model and the versions of the iClass system. As the system evolves piloting will be carried out continuously testing discrete improvements against user experience. The final evaluation information will be available one month (in March 2008) before the Pedagogical Model is finalised. The potential exploitability of iClass will mature as the piloting and evaluation produce more evidence of the feasibility of the system.