D2.5 – COGITO System Architecture v2
Creators: name: Giannakis, Giorgos
name: Papafragkakis, Apostolos
name: Vassiliadis, Michalis
name: Kakarantzas, Pavlos
name: Malavazos, Christos
name: Rovas, Dimitrios
name: Lilis, Georgios
name: Katsigarakis, Kyriakos
name: Teizer, Jochen
name: Esterle, Lukas
name: Chronopoulos, Christos
name: Bosché, Frédéric
name: Bueno Esposito, Martín
name: Robertson, Gail
name: Wilson, Amy
name: Kaheh, Zohreh
name: Tsakiris, Thanos
name: Gounaridou, Apostolia
name: Karkanis, Vasilios
name: Chatzakis, Michael
name: García-Castro, Raúl
name: González-Gerpe, Salvador
name: Bernardos, Socorro
name: Woitsch, Robert
name: Falcioni, Damiano
name: Andriopoulos, Panos
name: Zografou, Chara
name: Moraitis, Panagiotis
name: Triantafillou, Yannis
name: Belej, Bohuš
name: Straka, Martin
name: Baňas, Vladislav
name: Fedor, Jozef
name: Lofaj, Stanislav
Publisher: name: Zenodo
Year: 2022

description: This deliverable constitutes the outcome of the work carried out to design and deliver the final version of the COGITO ecosystem architecture. The present documentation of the COGITO system architecture is oriented towards (1) the definition of the Conceptual Architecture, (2) the development of the Use Cases  Sequence Diagrams, (3) the elicitation of each component’s Requirements and Specifications, and (4) the internal design of individual components. 

The Conceptual Architecture constitutes a high-level illustration of the COGITO solution with the various components involved, as have been reviewed and refined in the deliverable “D2.1 – Stakeholder requirements for the COGITO system” [1]. It also provides a high-level description of the components with their main functionalities that complements the conceptual architecture design. UML sequence diagrams have been developed for each COGITO Use Cases (UCs) to convey the high-level information about the relationships among the different components. We gave special attention to identifying and defining the relationships of each component with the Digital Twin Platform – the core interoperability component. A high-level sketch of dependencies among different parts of the COGITO system (e.g., individual components interfaces, etc.) has also been delivered, including information about the functional and non-functional requirements, the constraints of the different elements in terms of software and hardware resources, compatibility with standards, etc. UML component diagrams have also been developed providing additional information about each COGITO component's sub-components. Those UML component diagrams are further detailed in the corresponding demonstrator type deliverables.

The first version of the COGITO system architecture was released in M9, and it has been documented in the deliverable “D2.4 – COGITO system architecture v1”, providing a solid basis for the individual components’ prototyping. With the COGITO components prototypes and the COGITO data models & ontologies development being progressing, the first version of the overall architecture has undergone updates, based on the feedback received from the technical developers of the COGITO components during the technical workshops that were organised within the M10-M18 period. For the sake of completeness, the outcomes of D2.4 are replicated, accommodating the latest updates to the Use Cases Sequence Diagrams, the Components requirements and specifications tables, and the internal design of individual components.