Progress status for fall 2015
Progress reporting per country, please keep your own country up-to-date - to be replaced with the tables below!!
| Epic | Norway | Finland | Italy | Sweden | Denmark |
|---|---|---|---|---|---|
Study course search and selection | First version finished. Data from FSWS (Elmo). Test and production environment in progress | in progress (course selection, starting on GUI) | will start 1.10.2015 | Beta-version is developed, data from LadokPing, filtering and Elmo-xml | won't start until 2016 |
| Authentication | Finished (Feide and IdPorten) | in progress (test-Haka working in SMP) | in progress (using test-idp) | ||
Communication between nodes (NCP/SMP/EMREG/SIS) | SIS: Finished both input and output from FS SMP/EMREG: in progress | in progress (setting up skeletons, NCP and SMP communicating) | NCP <-> SIS finished planning stage: smp | ||
| Logging | not started | not started | not started | ||
| UAT | estimated October | not started | estimated oktober | ||
Ready for field trial | estimated November | not started (estimated to be done by 22.11.2015) | estimated 30.11.2015 | estimated november |
Development Milestones
Progress reporting should be as soon as milestones ar updated or met. Status and planning initially (2015-10-02) taken from progress status fall 2015 table (above).
Progress status marking
| N/A | Done | In progress | Not started | Unspecified |
|---|
Status dates
- When the status is "Done" the date indicates the done date.
- When the status is "In progress" the date indicates the planned done date.
- When the status is "Not started! the date indicates planned start date
- When the status is "Unspecified" the date indicates the date when there is a plan
Comments
Comments can be added in each field.
NCP
| NCP Development Milestones | NO | SE | DK | FI | IT |
|---|---|---|---|---|---|
| Retrieving of results from data source | 1.9.2015 | 2016 | Will start 1.10.2015 | ||
| User interface (course selection) | 15.9.2015 | ||||
| Generate and sign ELMO document | 25.9.2015 | ||||
| Return data to SMP-client | 25.9.2015 | ||||
| Logging | 16.10.2015 | ||||
| Infrastructure for test environment (database, servers, certificates) | 25.9.2015 | ||||
| Get certificate for test NCP, populate EMREG-test with address and certificate for NCP | 9.10.2015 | ||||
| Get certificate for production NCP, populate EMREG-prod with address and certificate for NCP | 16.10.2015 | ||||
| NCP ready for user test | 19.10.2015 | 10.2015 | |||
| NCP ready for field trial | 30.10.2015 | 11.2015 | 22.11.2015 | 30.11.2015 |
SMP Common code
| SMP Common Code milestones | Common development |
|---|---|
| SMP development | 30.6.2015 |
| SMP with link to questionnaire | 16.10.2015 |
| Will use common SMP in client | NO | SE | DK | FI | IT |
|---|---|---|---|---|---|
| Yes | ? | ? | No | Yes |
EMREG
Done (date?)
EMREX Client
| EMREX Client Development Milestones | NO | SE | DK | FI | IT |
|---|---|---|---|---|---|
| Authentication | N/A | ||||
| SMP set up | 9.10.2015 | ||||
| User interface | 2.10.2015 | ||||
| Verify data from NCP | 16.10.2015 | ||||
| Store collected data | 16.10.2015 | ||||
| Redirect customer for field trial questionaire | 16.10.2015 | ||||
| Log entries | 16.10.2015 | ||||
| SMP-client implemented in test environment | 16.10.2015 | ||||
| SMP-client ready for user test | 19.10.2015 | ||||
| SMP-client ready for field trial (in production environment) | 30.10.2015 | 22.11.2015 |
JIRA Backlog and Epics
Possible way to use jira-epics/issues to commonly follow progress:
Based on the system architecture (see System Architecture). Each country can of course have other epics/issues as well and are free to drill into these in their own way. But a common high level epic-structure allows for common reporting. This structure is also focused on achieving the end goal of being ready for the field trial.
Suggested EPICS:
- Study course search and selection
- Authentication
- Communication between nodes (NCP/SMP/EMREG/SIS)
- Logging
- UAT
- Ready for field trial
First draft for a JIRA backlog in Finland
EMREX-17 Make selection from Study records (Virta data) (Study Course Search and Selection)
EMREX-19 PDF generation and signing (Study Course Search and Selection)
EMREX-20 XML generation and signing (Study Course Search and Selection)
EMREX-18 Send selected courses to SMP (Study Course Search and Selection)
EMREX-14 HAKA authentication for NCP (Authentication)
EMREX-16 Get all data from Virta (Study Course Search and Selection)
EMREX-15 Accept SMP POST-request (Authentication)
EMREX-28 ELMO-data callback to SMP (Communication between nodes)
EMREX-33 PDF-donwload (Study Course Search and Selection)
EMREX-12 NCP Selection (Communication between nodes)
EMREX-10 SMP Login (Authentication)
EMREX-13 University selection (Study Course Search and Selection)
EMREX-29 Match session and store callback data on SMP (Communication between nodes)
EMREX-30 Verification of student match on SMP (Authentication)
EMREX-31User accepts data and verification result (Study Course Search and Selection)
EMREX-32 SMP sends data to University (Communication between nodes)
EMREX-34 SMP sends copy of data to users email if requested (Study Course Search and Selection)
EMREX-35 Specify Logging Data (Logging)
EMREX-27 Retrieve course description from university (Study Course Search and Selection)
EMREX-36 Administrator access to logs (Logging)
It is possible, at least in Finland, to link from the jira-epics/issues to wiki. Thus there is no need to update wiki, it will automatically be updated with the latest jira-status of the tickets shown. As an example (you might have to be logged in to see the actual description and status?):
Finland- NCP develoment:
Collaboration tools for developers
The project uses flowdock as a chat-tool. Please keep it open and check if there are any quick questions that you can answer.
https://www.flowdock.com/app/tiptop/emrex
Anybody can invite others, so you can invite your colleagues. Or send an email to Mats and he'll add you
Other stuff
WP3 tasks are mainly technical ones. Based on the requirements from work package 2, implement technical solution for National Contact Points and the Student Mobility Plug-in. The work package will be executed through regular project meeting and workshops, both face to face and remote meetings. There will be organized workshops for development and deployment for these solutions.
Activity: Open Source mechanisms
The code developed in the project will be open source. The mechanisms to share this code will be clarified in this WP
Activity: Development of National Contact Points
A National Contact Point has to be developed for each country. In this work package, a foundation for such a contact point will be developed. Based on this foundation each partner in the project signed up for implementing the solution will develop their own.
Activity: Development of Student Mobility Plug-ins
The Student Mobility Plug-in is a common service for collecting data from other higher institutions, via a National Contact Point. The student will be in control of the data exchange.
Activity: Deployment of the National Contact Point and the Student Mobility Plug-in
Each partner signed up for implementing the solution must deploy the National Contact Point and the Student Mobility Plug-in in one or more web applications for applicants and/or students.
Activity: Security
The information exchanged in this solution is personal. It is necessary to implement solutions to secure the integrity and confidentiality in the data exchange.
Activity: Technical documentation
Make technical documentation for the National Contact Point and the Student Mobility Plug-in, including examples of use.
Meetings
Aprox 1. May 2015: Open Source Platform, Detail planning for development and deployment
How often do we need telcom status meetings?
October 2015: Meeting/workshop: Test of NCP
Overall plan (still planning)
May 2015: Start up meeting
August 2015: First version of SMP
October 2015: Pilot version of SMP, incl technical doc
November 2015: Two NCP ready for testing, incl technical doc
December 2015: Two NCP ready for pilot
December 2015: Five deployments of SMP ready for pilot
April 2016: All five NCP ready for pilot
Rest of 2016: Support, bugfixing, improvements
December 2016: Final report
ELMO
ELMO is uses as exchange format in EMREX. More information at the pages for WP6 Standardisation
A viewer has been developed to show the contenct of an ELMO document in a more human way. This code can as well be used as a starting point for the ELMO viewer in NCP's and Emrex-clients.
The viewer can at the moment be testes at this site: http://matija.no/elmo/
Nordic glossary (link to Google docs)
https://drive.google.com/open?id=1cgGaihsj0S4l_F75Xu9qBQBmDlxHC5pva8Q3KUvRMDg&authuser=0
Wireframes
Wireframes, including a flow diagram for Emrex can be found here:
https://moqups.com/lundin.goran@gmail.com/2sWGyfXn/p:a2fa73ae2
Plans for each participating country
Denmark
Contact person: Anders Bøgebjerg Hansen
Participants:
Finland
Contact person: Mats Lindstedt
Participants: Ulf Nyström + developers from vendor (not selected yet)
Italy
Contact person: Stefano Russo <strusso@kion.it>
Participants: Stefano Russo <strusso@kion.it>, Claudio Caso <ccaso@kion.it>
Norway
Contact person: Geir Vangen <g.m.vangen@fsat.no>
Participants: Richard Edvin Borge <r.e.borge@fsat.no>, Matija Puzar (matija.puzar@fsat.no), Alen Milkovic <alen.milkovic@fsat.no>
Sweden
Contact person: Mattias Holmlund <mattias.holmlund@umu.se>
Participants: Mikael Berglund <mikael.berglund@umu.se>, Sven Hedqvist <sven.hedqvist@umu.se>