This deliverable presents the second and final release of the functional and non-function specifications of the iHelp solution and updates and replaces the first release D2.6 – “Functional and Non-Functional Specifications I” (Mel, Pan, 21), submitted at M10. Functional and non-functional specifications guide the development activities throughout the project, in order to achieve a consensus on what the iHelp platform will offer. This has a two-fold advantage as it lets the developers know what to build and the users what they will get. These specifications explain how the requirements provided by the pilots and the technical partners will be fulfilled by the iHelp platform and provide a detailed definition of the functionalities/behaviours of the iHelp components and the interactions among them. Details on the design of the components are outlined in the related deliverables and are out of the scope of this document. This work started from the initial version of the specifications and took into account the last outcomes of the requirements elicitation and architectural design. More specifically, the reported requirements in D2.3 – “State of the art and requirements analysis III” (M., A., C., + 22) and the updated architecture in D2.5 – “Conceptual model and reference architecture II” (M., P., A., + 22). Moreover, use cases reported in D2.3 have been analyzed to identify new or updated functionalities compared to those considered in D2.6. The final release of the iHelp architecture has been examined to understand the role and objective of each component, and the technical specifications were produced for all iHelp components. What is more, technical partners have provided the Swagger/OpenAPI files documenting the components they are responsible for. Connection mechanisms, data flows and control flows have been discussed and clarified during frequent brainstorming involving all interested parties. Requirements specified in D2.3 have been reviewed to update the non-functional specifications reported in D2.6.