The purpose of the deliverable D3.1 “TheFSM Open Reference Architecture” is to deliver the user requirements and the technical requirements of TheFSM, as well as to deliver the first version of the conceptual architecture of the TheFSM platform. In order to define the user and technical requirements in a solid manner, requirements identification and elicitation approach is adopted that is based on Agile development methodology. The adopted agile development methodology describes the agile processes, instruments, roles and methods that are adopted in all the phases of the development of TheFSM platform. This methodology defines User Stories definition with the appropriate guidelines and the additional information included within these User S...
This document provides an overview of the vast landscape of AI/ML frameworks. It identifies the most...
The deliverable contains an extensive elicitation of user and technical side requirements. It is goi...
Abstract Non-functional requirements (NFRs) are determinant for the success of software projects. Ho...
The purpose of the deliverable D3.1 “TheFSM Open Reference Architecture” is to deliver the second ve...
This deliverable aims at providing the 2nd version of business, data, legal and technical requiremen...
Deliverable D3.1 titled as “Technology Requirements and ToyLabs Components Analysis-v1” is used to d...
The current deliverable aims at providing a preliminary framework regarding requirements mapping and...
The current document entitled “Annual Release of TheFSM Data Platform” constitutes an accompanied re...
This is the first of the series of deliverables that specify the use case scenarios, their involved ...
This deliverable summarizes the work that has been done in the scope of Task 2.1 (“State of the art ...
This deliverable summarizes the work that has been currently done in the scope of T2.1 (“Requirement...
The purpose of Deliverable 2.3 is to design and define the FORTESIE architecture, to present the arc...
This is the final version of the UNICORE “Platform Requirements - Final” (D2.3) document. The origin...
This deliverable aims at analyzing the user stories and stakeholders' requirements and mapping them ...
This is the first of the series of deliverables that specify the pilot scenarios, their involved dat...
This document provides an overview of the vast landscape of AI/ML frameworks. It identifies the most...
The deliverable contains an extensive elicitation of user and technical side requirements. It is goi...
Abstract Non-functional requirements (NFRs) are determinant for the success of software projects. Ho...
The purpose of the deliverable D3.1 “TheFSM Open Reference Architecture” is to deliver the second ve...
This deliverable aims at providing the 2nd version of business, data, legal and technical requiremen...
Deliverable D3.1 titled as “Technology Requirements and ToyLabs Components Analysis-v1” is used to d...
The current deliverable aims at providing a preliminary framework regarding requirements mapping and...
The current document entitled “Annual Release of TheFSM Data Platform” constitutes an accompanied re...
This is the first of the series of deliverables that specify the use case scenarios, their involved ...
This deliverable summarizes the work that has been done in the scope of Task 2.1 (“State of the art ...
This deliverable summarizes the work that has been currently done in the scope of T2.1 (“Requirement...
The purpose of Deliverable 2.3 is to design and define the FORTESIE architecture, to present the arc...
This is the final version of the UNICORE “Platform Requirements - Final” (D2.3) document. The origin...
This deliverable aims at analyzing the user stories and stakeholders' requirements and mapping them ...
This is the first of the series of deliverables that specify the pilot scenarios, their involved dat...
This document provides an overview of the vast landscape of AI/ML frameworks. It identifies the most...
The deliverable contains an extensive elicitation of user and technical side requirements. It is goi...
Abstract Non-functional requirements (NFRs) are determinant for the success of software projects. Ho...