Internet of Things – Architecture © 30
te Methodolgy followed in order to derive the ARM and Finally Appendix E gives
requirements related to the ―Towards a Concrete Architecture‖ Chapter 5.3.
1.3 Project-internal inputs
This document draws heavily on the following public IoT-A deliverables and internal
reports. D1.5 mainly elaborated on D1.4 and feedback collected during the working
sessions held with external experts (e.g. at Bosch Research) and IERC cluster
members being involved in the Architecture activities taking place in IERC AC#1.
Other deliverables are mentioned for the sake of completeness. They were mainly
used for elaborating D1.2 and IR1.4 though:
D6.1, which contains a summary of the IoT-A requirements-engineering
process and a first list of requirements inferred from stakeholder aspirations
provided during the first IoT-A stakeholder workshop in Paris in October 2010
[Pastor 2011] This requirement list was analysed and views and
perspectives were assigned to all requirements. The list of Unified
Requirements can be found in [IoT-A UNIs];
D1.1, which contains a summary of the state of the art of IoT-related
architectures, service interfaces, communication layers, resolution
infrastructures, and hardware [Bui 2011]. Each of the aforementioned
topics is divided into input gathered from standardisation, commercial
applications, and EU and other research projects. This document was used
for the inference of technical requirements pertaining to the IoT architectural
reference model;
D1.4: The previous version (v2) of the ARM released in M26. Following its
release, a third round of feedback collection was initiated with external and
IERC experts;
IR2.1, IR3.1, IR4.1: which contain the detailed feedback from those work
package w.r.t. the first IoT Reference Architecture document D1.2.
Deliverables summarizing the results of the different Stakeholder workshops:
o 6.3: Final requirement list;
o 6.4: Final Validation report
Furthermore, as already mentioned, IoT-A provides a web page on which all the
IoT terminology that is used in this deliverable (and will be used in forthcoming
IoT-A deliverables) is listed [IoT-A Project]. A current snapshot can be
found in Appendix A.