Technical feasibility

SECTION I: Testing

1 Has the R & D result been tested?

1a In what mode has the result been tested?

•              Prototype

•              Pilot Application

•              Alpha/BETA testing


  • The first prototype has been tested by Consortium partners. The pilot application will be tested and evaluated during June so as to provide feedback to developers for finalization of technical implementations, while Beta testing will be performed during July-September and Best practice recommendations will be obtained.
1b. Please describe and discuss the testing results

Testing results of the first prototype by consortium partners is related to the tests and the validation required as part of the development process. These tests and validations include testing on available APIs for distributed searches across LCMS from mEducator partners, tests of the APIs operating on top of data stores to share and host Linked Data about educational services and data, populating the RDF store and depicting the repurposing history. Along with the finalisation of the full and complete prototype, full system tests will be carried out until June 2011, providing input to the actual evaluation of the mEducator solution 2.




SECTION 2: Current Stage of Development


2a To what extent does the development team have technical resources for supporting the production of a new product? (Researchers, human resources, hardware, etc. )
The development team consists of all partners of the mEducator consortium. Human resources are available for further technical implementations until August 2011. However, the project will be running until April 2012 and resources have been allocated for the evaluation and assessment of the platform as well as for reporting on best practices and relevant recommendations.
2b What are the technical issues that need to be tackled for full deployment, if needed?
A core group of mEducator partners has been working since January in order to detect problems and deficiencies of solution 2. The methodology used was based on a comparison between the initial functional requirements identified, the use cases that have been created and the observation/testing of the solution. An evaluation grid has been developed which embraces:

  • binary assessment (functionality present or absent)
  • qualitative evaluation identifying relevance or deficiencies problems in the way the functionality has been implemented, and
  • qualitative assessment related to the identification of other possible functionalities to enrich the solution.

The evaluation is being performed in 3 distinctive phases:

  1. Technical aspects of Solution 2
  2. Usability of the solution and the interface related aspects, and
  3. Quality of the results obtained by Solution 2 (mainly relevance of the  information)

During July the outcomes of the above evaluation will provide feedback to developers for full deployment of the mEducator Solution 2.

2c What additional technical resources are needed for the production of this new product?


2d Overall assessment of the current stage of technical development.
Detailed comment

The mEducator Solution 2 is implemented and evaluated in 60%, developments will be finalised by August 2011.

mEducator partners have started implementing the Content Sharing Solution 1 in May 2010. Several technology and content providers have been collaborating closely for the development of the APIs and for the development of the Semantic Web Services brokerage which is concerned with the development of an infrastructure which allows exposing educational services and LCMS in a Linked Data-oriented way (“Linked Services”) to enable the automated discovery/execution of distributed services. Tools and services (API’s) have also been developed in order to allow the integration of federated LCMSs. The first prototype of Content Sharing Solution 2 deploys and extends Linked Services technologies for integration of heterogeneous educational data stores and allows storage and enrichment of distributed educational resource metadata in a fully Linked Data-compliant way. The described federated architectural framework may allow for multiple instantiations of the interface. Currently, the content sharing functionality is accessible through a core platform interface as well as through a module which has been developed for partners using moodle as their LCMS.



SECTION 3: Deployment

3a Define the demands for large scale production in terms of
  • Materials

No materials are required



  • technologies, tools, machineries




  • Staff effort
Staff effort is required, specifically technical developers, in order to develop the services required for the integration of additional federated LCMSs.





SECTION 4: Overall Assessment


What is you overall assessment of the technical feasibility of the research result?


The product is technically feasible from the result of pilot implementation




Please put X as appropriate.

1 2 3 4 5
Adequacy of testing activity undertaken so far   x      
Adequacy and availability of technical resources of the development team         x
Current development stage     x    
Overall technical feasibility         x


Bookmark the permalink. Follow any comments here with the RSS feed for this post. Post a comment or leave a trackback: Trackback URL.

Post a Comment

You must be logged in to post a comment.

Request a proposal

Valorisation Plan Authors

Related Documents

There in no related documents

Visit the other applications of the INTERVALUE Platform: R&D Repository | IP Agreements

© 2009-2010 INTERVALUE Project