Requirements Federated Learning and mUlti-party computation Techniques for prostatE cancer, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/flute-requirements/ and changes regularly. See the Directory of published versions

2.1 Methodology

We used the following methodology. First, we researched the threat model to be considered in FLUTE. The threat model builds on the TRUMPET one, and takes into account the differences between TRUMPET and FLUTE. Next, a section of User and Stakeholder requirements was considered that provides high-level requirements that can be understood by non-technical people. Requirements are provided both in textual and tabular format. To capture the requirements, we utilized the expertise of researchers in PETs. The following section breaks down the User Requirements into Functional and Non-Functional requirements. These requirements are the basis of the System Requirements Specification that will guide the FLUTE software developers in the design of FLUTE components and architecture. These requirements are also provided both in textual and tabular format. Following the capture of requirements a section “PETs and security and privacy requirements” is provided, which identifies which of the captured requirements can be tackled with the use of FLUTE PETs, and also maps which particular PET (SMPC, TEEs, or a combination of both) is relevant.