OBJECTIVES

  1. To determine the requirements of the learning-analytics enhanced portfolio system, including privacy guidelines
  2. To determine the overall architecture of the learning-analytics enhanced portfolio system
  3. To develop new and/or integrate existing workplace-based assessment instruments as determined by WP2 into the existing portfolio system
  4. To integrate the portfolio system with modules developed in WP4 and WP5.
  5.  To configure the portfolio system and assessment instruments as needed by the test beds in WP6 and to test these configurations
  6. To manage and maintain the learning-analytics enhanced portfolio system during the test beds

DESCRIPTION OF WORK AND ROLE OF PARTICIPANTS

This WP is carried out by the technical universities UM and UR and all SME Partners involved: JW, MA, NR.  MA has an important role since they host the existing electronic portfolio system that will be used.  UM has the lead of this WP.

Task 3.1: Requirements engineering

This task will produce a growing requirements document containing the functional and non-functional requirements of the overall learning-enhanced portfolio system.  The task will be executed in close cooperation with WP2 in particular since this Work Package produces descriptions of the educational needs.  The requirements engineering will have as a starting principle that the existing electronic portfolio system EPASS will be applied, but requirements will be put in as generic terms as possible. The task is cyclic in character – the requirements need to be updated when new insights come to light.
The document will include at least:

  • Description of goals, organisations, stakeholders, and end users involved
  • Description of main processes around workplace-based based assessment and feedback
  • Description of the assessment instruments that have to be implemented in the portfolio system
  • Description of external assessment instruments that have to be integrated into or linked to the portfolio system
  • Description of the data that has to be collected for the user modelling
  • Description of the data that is needed to produce Just-in-Time feedback
  • Description of the data that is needed to produce visualisations
  • Functional requirements of the connections between portfolio and student model server
  • Functional requirements of integration of JIT feedback and visualisation in the portfolio

(Detailed requirements engineering of the user-model server will take place in WP4 and detailed requirements engineering of feedback and visualisation will take place in WP5).

  • Requirements concerning server and end user platform
  • Requirements concerning performance, usability, quality and availability
  • Requirements concerning security
  • Requirements concerning privacy
  • Requirements concerning management and maintenance

As a part of the requirements, a privacy model and guidelines for privacy have to be developed.
Since requirements will develop during the project, approval will be requested at regular intervals.  As soon as the system comes into place, as part of continuous evaluation, the system must be verified according to the requirements.  If a requirement is not met, either the system must be improved or the requirement must be judged infeasible and removed and updated.
To ensure the quality of requirements process and document, a web-based environment will be used to develop and manage the requirements document that includes clearly coding of the requirements, versioning, marking approval, and verifying.
Although many project members and other stakeholders will be actively involved in developing and checking requirements, the process is led by a requirements engineer who is responsible for managing the document and arranging approval and verification.
Planning: This task will continue throughout the whole length of the project M1-M36.

Task 3.2  System architecture. This task will produce a design document that specifies the system architecture of the learning-analytics enhanced portfolio system.  This system will consist of the following elements :

  1. An existing electronic portfolio system (EPASS by Maastricht University and Mateum)
  2. External assessment tools (such as a game or simulator)
  3. A student-model engine (server) needed in WP4
  4. Just-in-Time feedback module needed in WP5
  5. Visualisation module needed in WP5

The document should be described in such way that the modules in Work Packages WP4 and WP5 can develop independently from and in parallel to WP3 and each other.  The document must adhere at all times to the requirements document.
The existing electronic portfolio system will only be described as far as needed to support the integration into the system.  This description will be put in such a generic way that another electronic portfolio system could take its role when it adheres to the requirements and architecture design.
The document will describe the following aspects:

  • Description of the above mentioned modules
  • Precise description of communication protocols (e.g. web services) or APIs that link the modules between which information needs to be exchanged.
  • The Privacy protective and socio-ethical design features to provide for:

i)    Informed Consent Process implementation within the user interface prior to the point of registration by a Workplace Trainee into the Portfolio System
ii)   Allowing profile elements to be updated by the user
iii)  Allowing user options for local generation of the training model (if their client-end device can have sufficient computational resources), or, alternatively server-side generation of the instantiated models
iv) Ensuring models are deleted after each instantiation session.

For the modules being developed within the project the following aspects need to be described if applicable:

  • Deployment platform, operating system (WP4)
  • Development platform
  • Database platform
  • Software modules, libraries, used.

The system architecture document needs to be approved by the WP-leaders of WP3, WP4 and WP5. Subsequent updates might be necessary when requirements are changed.  New approval is requested in such case.
Planning: A first approved version the system architecture needs to be available before the commencement of WP4 and WP5.

Task 3.3 Assessment tools. This task depends on the outcome of WP2 since it is determined in that Work Package which assessment instruments are needed.  It is to be decided in this task whether existing building blocks within the portfolio system can be applied or new functionality has to be developed within the portfolio system.  When it is decided to apply external assessment tools, a connection to the portfolio system has to be established.  This can either be a seamless integration into the portfolio user interface, or a data-connection in which only data collected in the tool is transported to the portfolio system.
It is already foreseen that assessment tools probably will include serious games such as that developed by Charitè (SimMed) which allows for the simulation of patient observation, differential diagnosis, diagnostic practice, etc.
This task requires close cooperation and negotiation with WP2.  It should start at the beginning of the project and finish before the implementation in client institutions.  The deliverable of this task is descriptions of the developed and selected assessment tools.

Task 3.4 Integration of WP4 and WP5 modules. This task consists of (a) implementing, integrating and testing of the electronic portfolio side of the data-exchange link with the student-model engine, (b) implementing, integrating and testing the electronic portfolio side of the Just-in-Time feedback module, particularly in the mobile version of the portfolio interface, (c) implementing, integrating and testing the electronic portfolio side of the visualisation module.
These activities have to be performed in coordination with Work Package WP4 and WP5 and should be finished before the test beds in WP6 are started.The deliverable of this task is a description of work done including the test reports.

Task 3.5 Configuration. The electronic portfolio has to be configured for the needs of the test beds in WP6.  This includes the definition of the organisational roles, permissions, user accounts, portfolio structure, competency models, and not least the assessment instruments.  All done according to the requirements document.
The three configurations, one for each test bed, including the assessment instruments have to be tested and approved by the end users.  If necessary, requirements and/or configuration must be adjusted.  Configuration includes the modules developed in WP4 and WP5 as soon as they are integrated.
The deliverable of this task is a report describing the agreed and approved configurations.

Task 3.6 Maintenance and Support. During the remainder of the project, the learning-analytics enhanced electronic portfolio system has to be managed (e.g. user management) maintained, and supported (helpdesk and second-line support).