2.3.3. Expected project outputs

(Recommended length: 1 page) Detail the concrete final results of the project: give a clear description of what will be its actual set of outputs (novel algorithms, standards, open source libraries, implemented collaborative framework, demonstrator, product prototype, new service based on some software, wearable device, etc.). The description should be detailed enough to give a clear picture of what will be generated, including the core functionalities and levels of maturity. At the end of the project, the results will be confronted with the content of this subsection (potentially updated through Change Requests). A poor description will be considered as a lack of expected results, or as significant uncertainty about what will be delivered: clarity is therefore highly recommended here. The requested description must focus on tangible, realistic and credible outputs that will be developed within the project (if the project extends existing solutions, then clearly clarify the specific contributions of the project) and available at project closure, i.e. demonstrated at the final project review. Post-closure results, like exploitation plans and prospects, have to be indicated in §2.2.2. This subsection should convince evaluators that the project will deliver tangible results of interest that will support the business goals of the project partners.