WP4. System architecture & Integration

WP4 focuses on the integration of the back-end modules developed in WP1-3, enabling the development of interactive applications in WP5. The main objective of WP is to unify the developed technologies under the eTryOn middleware and provide access through a set of back-end and front-end APIs.

Description of work

T4.1 – System architecture and integration protocol design (M1-M8)

The purpose of this activity is to provide direction and specifications for consortium partners who will develop software components through the R&D and pilot phases of the project. It consists of defining the components, including their functional and non-functional requirements and the interfaces between them. These will be described as a series of related diagrams in the C4 model, and interfaces using the Swagger specification for APIs. The development of these specifications will involve a high level of collaboration between consortium partners to assess point-to-point validity. Integration validity will be assessed by describing how the components will collaborate for each of the pilot use cases.

T4.2 – eTryOn middleware and component integration (M9-M18)

This covers the development and deployment of server-targeted components to fulfil the specifications described in D4.1. These components will be developed to run in the AWS platform as serverless components (using AWS Lambda) for preference, or containerised services if this is not possible. Software development will use an agile methodology that includes regular, timeboxed releases, giving us a regular measure of progress, and we will use vertical slice development to uncover complexities early, and spike investigations to further reduce risk.

T4.3 – APIs for back-end and front-end applications (M9-M18)

This covers both the software development of service components that enable access to the business logic components developed in T4.2 and also the hosting and support of the assembled services for the rest of the consortium in R&D and the pilots. The software development parts will run in the same way as described in T4.2, with the addition of configurations for regional distribution of the services, load balancing, autoscaling and caching. We will monitor the performance of the services and components, and target and resolve server and network latency issues as they arise.