...
| # | Requirements | Short description | Type* | Business Value (0-lower 5-higher) | Effort needed (in hours) | Proposed Timeline (2015 or 2016) | Timeline Expected (2015 or 2016) | Obs. |
|---|---|---|---|---|---|---|---|---|
| 1 | Refactoring of nomenclature of packages and components, replacing epSOS (and other companies) specific wording toward generic eHealthNCP | 2016 | This does not break the licensing constraints (GPL V3) this only consist on changing nomenclature by normalised naming. | |||||
| 2 | Extension of epSOS services to can be used by mobile devices. The services have to be REST ready and will help other applications to adapt OpenNCP gateway for usage beyond epSOS | In order to use epsos services a rest api has to be built above client connector to give the possibility to mobile developers create mobile apps for using epsos services. This API will use the existing functions of OpenNCP portal and expose some of these with the REST architecture | 2016 | |||||
| 3 | Test Strategy | Invoke eADC, Audit Manager and XCPD/XCA/XDS Validator in an asynchronous mode to increase response time of servers | 2015 | |||||
| 4 | Preparation of ready to use OpenNCP images using Docker or other alike technologies for easier installation | 2015 | ||||||
| 5 | Stress testing of OpenNCP components to assure that they can handle significant number of concurrent users | 2016 | ||||||
| 6 | Security tests of OpenNCP bundle to assure that they are ready for LIVE DATA | 2015 | * Markus will provide results |
...