Collaborative Open Market to Place Objects at your Service

D1.2.1 Initial COMPOSE architecture document


The COMPOSE project aims to perform research leading to the development of an IoT platform that will easily enable relevant stakeholders to be engaged. Stakeholders include (i) developers, who wish to develop services and applications based on real-world smart objects (ii) Smart objects providers and owners who wish their smart objects to be exposed and available to developers, and (iii) end-users who wish to make use of existing services and applications. The goal is to create such a platform that will automatically take the burden off the identified stakeholders and enable each one to concentrate on their areas of expertise while leaving all systems related aspects as well as productivity related aspects for the COMPOSE platform to handle. The main aim of this document is to explain in detail the architecture of the proposed platform including main aspects driving to this architecture and the manner in which the proposed architecture will enable achieving the ambitious goals set out at the beginning of this journey. This document was thought of and written with the requirements document (D1.1.1 "COMPOSE requirements") in mind, and the forming use cases as a constant validation and reference point. This deliverable represents the first complete version of the architecture document, but is not seen as the final product, rather it is the first step in an iterative process that will be further refined as we advance with the design, implementation, and validation of different aspects of the project. The final COMPOSE design document is due in M24, a year after this document. We took such an approach due to the complexity and multi-dimensionality of the proposed platform, thus, this document serves as a starting point from which all individual tasks in the technical WPs can start from, but we leave room for improvements and for getting things right as we gain actual experience in the development parlours. In addition, possible changes in the requirements document will have to be reflected in future versions of this design document. In this document we start from a high level description of the architecture and then delve into more detailed explanation of the different components, and the interactions thereof. In addition the main ideas and interactions are demonstrated through the introduction of the platform as viewed by the main stakeholders, as well as by mapping the intended use-cases to the proposed architecture.

Document Type: 
Deliverables