Deliverables
This report will report, for year 2, about the lessons learnt on all the actions carried out in order to keep engaged the wider community of developers and enlarging the base of FIWARE Technology providers.
This deliverable will contain the measures about the FIWARE evolution processes indicators and major lessons learned as achieved in yesr 2.
This deliverable will describe the FIWARE go-to-market Strategy as a refinement of such strategy based on FIWARE related market evolution, and FIWARE adoption statistics and impact.
This deliverable will report about dissemination events where the FIWARE Community attended with statistics, feedback and lessons learnt covering year 1.
This deliverable will describe the work done in FI-NEXT for the coordination related to its involvement in the programme collaboration activities with other projects selected under the ICT-12 call. This deliverable describes work done in year 2.
This deliverable will contain the report for year 2 about the performed testing activities. It will include also the third party certification report. A post in FIWARE blog will be published summarizing the major assessment. This report will be delivered together with the produced code or tools for performing the tests.
This report will report, for yesr 2, about the lessons learnt on all the actions carried out in order to reach the wider community of developers in order to engage them as FIWARE Active Contributors.
This is a guide for FIWARE node owners with the description of the requirements, service levels, set up process, obligations and belonging rules to the FIWARE Lab. This guide is a refinement and completion of what already available from the FI-Core project.
This deliverable will report about dissemination events where the FIWARE Community attended with statistics, feedback and lessons learnt covering year 2.
This deliverable will describe the work done in FI-NEXT for the coordination related to its involvement in the programme collaboration activities with other projects selected under the ICT-12 call. This report covers the work done in year 1.
This deliverable will describe the work done regarding SCRUM activities in year 2.
This deliverable will contain the measures about the FIWARE evolution processes indicators and major lessons learned as achieved in year 1.
This deliverable will report on the evolution, usage, statistics and impact of all project websites, social tools and promotional material at year 2.
This deliverable will report on the evolution, usage, statistics and impact of all project websites, social tools and promotional material at year 1.
This deliverable will describe the work done regarding SCRUM activities in year 1.
This report will report, for yesr 1, about the lessons learnt on all the actions carried out in order to reach the wider community of developers in order to engage them as FIWARE Active Contributors.
This deliverable will describe the work done in supporting the FIWARE TSC in the year 1.
This deliverable will contain the report for year 1 about the performed testing activities. It will include also the third party certification report. A post in FIWARE blog will be published summarizing the major assessment. If needed, the report will contain an update of the testing plan. This report will be delivered together with the produced code or tools for performing the tests.
This deliverable will describe the FIWARE go-to-market Strategy.
This deliverable will describe the work done in supporting the FIWARE TSC in year 2.
This deliverable describes the evolution of the FIWARE Support tools such as the FIWARE Catalogue and the FIWARE Academy.
This report will report, for year 1, about the lessons learnt on all the actions carried out in order to keep engaged the wider community of developers and enlarging the base of FIWARE Technology providers.
This deliverable describes and formally defines model and rules for accessing the services to FIWARE Lab by third parties
This deliverable will detail the method, process, phases and tools to perform the three above mentioned testing activities (documentation, functional and stress).
"This deliverable is an update of ""Technical Roadmap v1.0"". It will define the Technical Roadmap for all of the activities within WP3, incorporating inputs from all of the tasks. These will be consolidated into a coherent roadmap outlining the development of key FIWARE technologies providing details for near term evolutions and indicators for longer term evolutions."
This deliverable will document the software developed inside the Task 4.2 in year 1, providing Users Manual and Operator Manuals following the FIWARE Community documentation policies.
This deliverable will define the Technical Roadmap for all of the activities within WP3, incorporating inputs from all of the tasks. These will be consolidated into a coherent roadmap outlining the development of key FIWARE technologies providing details for near term evolutions and indicators for longer term evolutions.
This deliverable will comprise of the software and associated documentation relating to the GEris to be released under WP3 at the FIWARE releases scheduled for M12.
This deliverable will document the software developed inside the Task 4.2 in year 2, providing Users Manual and Operator Manuals following the FIWARE Community documentation policies.
This deliverable will comprise of the software and associated documentation relating to the GEris to be released under WP3 at the FIWARE releases scheduled for M24.
This deliverable will report, for year 2, the assessment of FIWARE Lab nodes operation, recommendations to each node to improve the provided service, and lessons learnt. Corrective actions will be also reported here.
This deliverable will report, for year 1, the assessment of FIWARE Lab nodes operation, recommendations to each node to improve the provided service, and lessons learnt. Corrective actions will be also reported here.
Searching for OpenAIRE data...
Publications
Author(s): Sergio Vavassori, Javier Soriano, Rafael Fernández
Published in: Sensors, Issue 17/9, 2017, Page(s) 2148, ISSN 1424-8220
DOI: 10.3390/s17092148
