1. Usage scenarios, User Interface & tools
Usage scenarios, User Interface & tools
UVA
Annual Review meeting
Genova (IT), September 22, 2009

2. Main results achieved (m12)
Main results achieved (m12)
Basic WP4 results
Initial (m9-m19) wizard and user interface – specs and prototype (in D4.1)
Partial development (m9-m19) of metrics and user-results match (D4.2)
Initial steps (m12-m19) towards user interface customization, user recommender system and multilingual support
Support for lifecycle of use scenarios and cases
Lifecycle: Elicitation, development and validation, and iterative formative evaluation and refinement of user types, use cases and scenarios (reported in D4.1 – included in D5.4 - and in D6.2 – included in D2.1)
Related significant and illustrating use cases
System expansion: metadata tagging and enrichment, metadata migration
RICK and MMF: WP3.3 (m11-m16) and reported in D5.4
R2.1 – A Teacher Education ontology (TEO) for defining the Common Metadata Model (CMM) and for allowing cultural-linguistic personalization of the Share.TEC system
R2.2 – Common metadata model (CMM) for European TE contents that draws on international standards and guarantees semantic, linguistic and cultural interoperability of the system R2.3 - Establishing a sound basis for effective brokerage through the definition of ontology-based user profiles. R3.1 – linguistic and cultural interoperability based on a multicultural metadata model (M3) and corresponding binding for overcoming cross-cultural barriers
22/9/2009

3. Basic WP4 results Wizard and user interface
User interface design document, main user profile data and system interface first prototype
First year interface to be tested for feedback and improvement (see especially Dublin m13 initial external test)
Metrics for resource-user matching
Not yet documented in a deliverable
Analysis of different ranking metrics, feasible to be implemented based on a combination of ”Human review, Text-based similarity and Contextual information”
22/9/2009

4. Use scenarios and cases
Use scenarios and cases
Support lifecycle through iterative cycles of formative evaluation
Elicitate, develop, validate, evaluate and refine
Means to develop the Share.TEC system that responds suitably to end-user requirements
Serve as a communication point with end users and stakeholders
Identify the actual needs of the users
Define user-level services and formal system processes (WP5)
Define user models and profiles, adapt interfaces, provide recommendations (WP4)
Allow for interoperability and system expansion (WP3)
22/9/2009 4

5. Main user types and goals
Main user types and goals
Teacher educator & student teacher (pre- and in-service teachers)
Seek content that supports self-directed learning and training activities
Share educational and professional practices and resources with their peers
Educational publisher
Access a wide market for digital content through a federated system across Europe
Monitor trends and identify emerging user needs
Educational content provider
Access a wide user community capable to providing rapid feedback for content development and test resource potential
22/9/2009 5

6. Example of use scenario and associated use cases
Example of use scenario and associated use cases
Look for digital content
Search using basic options
Search using advanced options
Search using personalized options
Filter using advanced options
Filter using personalized options
Browsing according to the ontology
Set automatic notification system
22/9/2009 6

7. Elicitation and validation
Elicitation and validation
End-user feedback in Venice workshop (m8)
Main user types, scenarios and cases
Adoption of User Centred Design and support of lifecycle
Validation process (m9-m12)
Check whether use cases explicit all useful services of the platform in a non-overlapping way
It involved partner teams and two experts – end users assigned by each partner
Open questions and a validation grid were provided and data were compiled
Current work includes iterative evaluation and refinement with end users (see e.g. m13 Dublin workshop)
22//9/2009 7

8. Use Case: System expansion
Use Case: System expansion
Scenario A:
User Sara, teacher educator
Associated use case:
Add new digital content description (UC_021)
Description
"Sara has a number of resources and she thinks they may be interesting to share them with other Teacher Educators.
Yet, these resources have not been previously tagged.
Using RICK, Sara annotates the resources according to the CMM metadata model (using especially the TE-specific metadata).
These metadata records are now ready to be gathered by the harvester."
VIDEO (RICK)
22/9/2009 8

9. Use Case: System expansion
Use Case: System expansion
Scenario B:
User Iván, teacher educator
Associated use case:
Add new digital content description (UC_021) & Update digital content description (UC-022)
Description
"Iván wants to add his resources collection to the Share.TEC community.
Those resources had been tagged by himself using the LOM format.
Instead of having to re-tag the resources, Iván is offered the possibility of reusing his metadata records through MMF.
This metadata translation is done automatically, but Iván may also use the RICK tool in order to enrich or review the resulting metadata."
VIDEO (MMF+RICK)
22/9/2009 9

10. Success Indicators Indicator Expected progress Result User feedback
Success Indicators
Indicator
Expected progress
Result
User feedback
base figure
Use case elicitation during Venice workshop (end users)
Use case validation (internally assigned experts)
Focus groups (end users)
Interoperability
30%
50%+
(MMM, metadata repository, harvesting capabilities)
system expansion tools
Usability
20%
UI specification and wizard (prototype)
Use scenarios and cases
Current scenario for digital resource use & sharing across Europe:
22/9/2009

11. Challenges & remedial actions
Challenges & remedial actions
Challenge: Express user needs in order to enhance usability and define user services
Action: Adopt User Centred Design. Elicit and validate use scenarios and cases, serving as communication point with final users and system developers.
Challenge: Know whether the system interface and wizard are adequate
Action: Involve users in iterative cycles of formative evaluation of use cases and prototypes. Use focus groups, interviews, questionnaires.
Challenge: Provide an efficient mechanism of enriching metadata with TE-specific metadata, while exploiting existing ones
Action: The RICK tool allows for a transparent metadata enrichment for TE-specific information (TEO, CMM schema) and standard LOM data. MMF allows for migration of existing metadata. These tools are used internally for the repository population before an external validation.
Federation, metadata aggregation/harvesting
22/9/2009