Work package 3
Objectives: System requirements and system architecture, security, specific requirements for the pilot use cases
Task 3.1 – Operational Context and Requirements Analysis
This task analyzes the overall operational context, including regulatory frameworks, operational barriers, existing solutions, and emerging trends. It reviews recent research and the State of Practice (SoP) in applying similar technologies.
Each Use Case (UC) owner will collect detailed functional, non-functional, and business requirements, reported in Deliverable D3.1, serving as input for architecture design in Task 3.3.
The analysis will provide WP11 with benchmarks for technology validation and include use case-specific user acceptance criteria. Task 3.1 will assess end-user and stakeholder needs, deriving constraints and guidelines for subsequent design, development, and integration phases.
Task 3.2 – Security and Privacy
The platform will be developed following ethical and legal standards for privacy, security, and fundamental rights protection. This includes ensuring GDPR and EU Cybersecurity Act (Reg. 2019/881) compliance.
The task defines security and privacy configurations for platform–service provider interactions and provides guidelines for access control, anonymization, and zero-trust execution to prevent data leaks and attacks.
Dynamic, context-aware security policies will guide encryption of data at rest and in transit (HTTPS, SSL, TLS, FTPS, IPSEC). Implementation will be supported by WP4–WP7 under this task’s guidance.
Task 3.3 – Platform Specification and Architecture Definition
This task defines the data analysis pipeline model based on T3.1’s findings, introducing innovations in dynamic pipelines, analytics quality, and edge–cloud execution.
It specifies the platform architecture, analyzing existing models and designing a Service-Oriented Architecture (SOA) with Function-as-a-Service, microservices, and cloud-to-edge compute continuum.
External beta testers will validate design and requirements. Development follows an iterative cycle of design, deployment, evaluation, and refinement through rapid prototyping.
A Zero Trust Architecture (ZTA) and Kubernetes-inspired marketplace will enable stakeholders to offer data, analytics, and ML resources. The task will also define and maintain APIs for external stakeholders and marketplace providers.
Task 3.4 – Pilot Use Case Adaptation and Integration (ALL) [M3–M18] | Deliverable: D3.3
This task prepares Pilot Use Cases for testing and evaluation, based on requirements from T3.1 and the architecture from T3.3.
By Month 3, requirements and objectives will be finalized; by Month 6, data tasks will be extracted from existing applications and ported to the platform API as preliminary workflows by Month 7.
Workflows will be expanded to full functionality by Month 18, ensuring all artefacts and data flows between UC functions are adapted for platform demonstration.
