Actions and inputs Sample Clauses

Actions and inputs. ‌ In the previous section we discussed how reference architectures relate to architectures and real systems. In order to derive such a reference architecture and the reference model upon which the reference architecture builds, one needs to understand better how they relate to each other and to external input. A high-level taxonomy of how we understand the reference architecture process is depicted in Figure 5. Such a taxonomy already provides us with a high-level perspective of actions and inputs needed for developing an ARM for IoT. As discussed earlier, the IoT Reference Model provides guidance for the description of the IoT Reference Architecture. The Best Practice guides the derivation of IoT-A-compliant domain-specific concrete architectures from the reference architecture. Essential inputs for the definition of the IoT Reference Model are stakeholder concerns, business scenarios, and existing architectures. It is important to create a common understanding of the IoT domain from the different inputs. This is mainly a modelling exercise, during which experts have to work together and extract the main concepts and their relations of the IoT domain from available knowledge. Furthermore, business scenarios, existing architectures, and stakeholder concerns can be transformed into application-specific requirements. When extrapolated, these requirements lead to a set of unified requirements. Unified requirements in turn steer the definition of the IoT Reference Architecture. Within the ARM, the IoT Reference Model guides the definition of the IoT Reference Architecture, creating dependencies between the Reference Architecture and the Reference Model; once a change is proposed in the Reference Model a clear chain of dependencies can be followed and lead to subsequent changes within the Reference Architecture. By so doing, an overall consistency of the IoT-A ARM is maintained. IoT Reference Model understand guides extrapolate IoT Reference Architecture Unified Requirements steer Business Scenarios, Existing Architectures & Stakeholders define Application- Specific Requirements define guides with Best Practices Compliant Domain-Specific Architectures Figure 5: High-level taxonomy of the IoT-Reference-Model and IoT-Reference-Architecture dependencies and model influences. As one can see, this high-level taxonomy already identifies high-level actions for the derivation of the ARM and for domain-specific architectures (“understand”, “define”, etc.). However this ...