Work package 3 deals with the design of the C3-Cloud solution (its system architecture). It is responsible for collecting the requirements from the C3-Cloud stakeholders, such as user requirements from patients and clinicians, as well as technical requirements, such as security and deployment requirements from the technical partners. The main deliverables of WP3 is the definition of a requirements traceability matrix against which the system is developed, as well a system architecture definition.
The goals of WP3 are achieved by four tasks. Task 3.1 focuses on identification of relevant literature and state-of-the-art in the technical infrastructure as well as technologies in integrated care (Task 3.1). Task 3.2 is responsible for eliciting, collating, categorising and documenting the requirements for the infrastructure. Task 3.3 defined the conceptual architecture for the C3-Cloud, which will feed into the development work packages. Finally, task 3.4 is responsible for monitoring user-centred design activities, as well as activities that require a high degree of coordination amongst the project partners.
At present Task 3.4 is active and responsible for a) facilitating the coproduction activities of the project, and in addition to its original scope, reviewing the validity of the requirements as the project progresses, contributing to high quality, validity of requirements and identification of potential risks before they escalate. The activities of Task 3.4 have produced valuable input for the coproduction activities. Task 3.4 does not have any formal deliverables; however, an internal report was circulated and submitted to the PMB following major milestones.
Task 3.1 Survey of the State of the Art Research, Technologies and Architectures (completed)
The task was led by INSERM, and resulted in a literature review of the main relevant subjects. Contributions to the literature review involved SRDC, WARWICK, MEDIXINE, Cambio, INSERM, OSAKI, KG, EuroRec and ORU, while the finalisation of the deliverable also involved empirica. Deliverable D3.1 has been submitted on time and has been used by other tasks in the project.
Task 3.2 Gathering Technical Requirements of C3-Cloud Architecture (completed)
This task was led by SRDC with the contribution of all partners to elicit, collate, categorise and document the requirements for the ICT elements of C3-cloud, with input from prospective users. Use case descriptions and system requirement specifications for all C3-Cloud components have been documented, in accordance with the IEEE standard 29148:2011 (Systems and Software engineering- Life cycle processes –Requirements engineering). 72 technical use cases and a total of 348 requirements have been identified. This task has resulted in the deliverable D3.2.
Task 3.3 Conceptual Design of C3-Cloud Architecture (completed)
The task was led by WARWICK, and resulted in elicitation and definition of the conceptual architecture of C3-Cloud, in order for project stakeholders to have a technical reference to continue implementation work for each subsystem in subsequent work packages. Based on a detailed analysis of the system requirements and use cases from deliverable D3.2, this task derived key communication interfaces among system components and their interaction workflow in order to fulfil the requirements. As an information intensive system, extensive information modelling has also taken place as part of the design activities. Deliverable D3.3 was produced, reviewed and approved by all partners, and submitted on time. The content of D3.3 was prepared in accordance with the IEEE Standard 1016-2009 (IEEE Standard for Information Technology – Systems Design — Software Design Descriptions). All partners contributed to this task.
Task 3.4 Facilitating Co-production among Cross-disciplinary Teams
At present Task 3.4 is active and responsible for facilitating the coproduction activities of the project, and in addition to its original scope, reviewing the validity of the requirements as the project progresses, contributing to high quality, validity of requirements and identification of potential risks before they escalate.
Those marked with a will be publicly available after approval.