General design principles Sample Clauses

General design principles. In [1] we defined a set of use cases and requirements specific for the domains of e-health, energy management, domotics and community services. From these requirements we derived a set of general design principles which are briefly summarized hereby:  Loosely-coupled integrated control using information brokering; this means that failure of one of the providing or consuming sub-services, does not result in failure of all functionality.  Distributed connection management for federated gateways; in this case the gateway aids in setting up connections between devices, but is not required for further communication. Such mechanism ensures that when the gateway fails, at least parts of the home system continue to operate.  Security and privacy; this includes protecting the user against attacks on the home network, preventing others from getting access to the user’s personal data, and also prevents the user from tampering with information services.  Graceful degradation of services; systems and services that are interconnected must be able to maintain an acceptable level of basic operation if the network fails. That is, if coordinating or governing super-systems are no longer available, the system should be able to run autonomously.  Support for multi-vendor systems, multiple service provider, multiple gateways; consumers will use multiple services from multiple service providers, even though new services could be installed on a gateway the architecture must be able to support multiple gateways. These general principles are used in the definition of the Internal Federation Architecture. They will provide guidance for making architectural choices. In the next chapter we describe the Internal Federation Architecture from a networking perspective and define the required components. In Chapter 4 we will evaluate to what extent the architectural choices fulfil the generic requirements and support the use cases.