Abstract Architectures for Smart Office Clause Samples

Abstract Architectures for Smart Office. (Scenario 4)‌ The abstract architecture for the Scenario 4 is divided according to the two identified test groups: The first abstract architecture shown in Figure 7 represents the communication dependencies that need to be tested with respect to configuration and discovery of devices. The other figure (Figure 8) shows the execution-time messages for this scenario and identifies what has to be tested to validate the scenario. The figures serve as a basic description of the architecture that will be tested. The test cases will refer to this figure as needed. The components that are to be tested in the respective test case are identified in the test purpose. EUT IoT6 Gateway 2. Local CMS Global Resource Directory Control-Monitoring System Smart Board Resource Directory Server 1., 2. mDNS or CoAP RD EUT 1. IoT6 Gateway Smart Office App Local CMS Legacy Device Controller Control-Monitoring System Smart Board Legacy Device 1. IoT6 CoAP 12/JSON/oBIX 2. Legacy Protocol 3. Smart Office App API 5 Base Standards: Refined use case scenarios‌ According to the ETSI guideline that is followed in this deliverable, the starting point for the creation of a test specification is the follow up to base standards that clearly identify the requirements for the system to be tested. In this chapter, therefore, a selection of the use-case scenarios that have already been defined in deliverable D1.1 is refined so that they can be used as basis for the test process that will be specified. The selection was carried out in a way that the chosen use cases can be used to generate all necessary test cases for the IoT6 architecture. Throughout the following sections, the IoT6 project partners are addressed with the following abbreviations: